I throw my two cents about this topic.
- I am a little reserved about advertising of a "buying" product other than PI team.
Warhen, I'm glad for you if you write a book but the best is to avoid many advertising here. Your book is not finished. OK. Go back when it will be ready and ask PI team if you can do advertising here.
I have bought your video but as many books on astrophotography software it stays at the 1rst level of the possibilities of the functions. Many of them use standard settings where the most interesting is to go deeper in the choices of theses settings. It is a choice. No problem. But useless for PI users who want to go deeper in the full settings range of every important process.
For example, when doing StarAlignment with special distortion correction on large CCD and very special optics (Riccardi Honders for example), we have spent hours and hours to find the right settings to make a real correction. Some settings are far from the standard ones. New splines distortion image solver script is now a better result for this. We cannot write a book for this. But we are several users in France to use now this method. We will do a special event in November for Hi level PI users of AIP (our association)
I will not buy your book because PI moves constantly and some very usefull process are changing every year.
A good book is not to describe at a time (2015-2016) every process but the way to abord an image for processing. In 2017 or 2018, your book will be useless if you describe all function like your video. But I understand PI users need documentation. If a book can do the job, why not.
A good book on PI should explain the philosophy of PI. From pre-processing to final processing. For example doing a good chapter on all denoising possibilities, when, where, how... and explain the philosophy of denoising.
In my association, AIP, we are doing Pixinsight training. It is free. When I am doing the training I try to explain why I will do this process or this other one. Why this choice. And question are coming.
- Another thing, it is not because you will claim PI documentation is missing, useless or so, the things will be better. It takes a long time to do a good reference documentation. Juan tries to do the best documentation for each processes. I prefere he uses his time to do new stuff, process, scripts, bug correction for PI than spend his time to do a huge documentation. Every setting in all process have a small information (when mouse over) and it is a good start.
The best in this forum is users can share some settings, even simple, with examples. It is a good starting point. It is how I learned PI, and how I wrote my website (for french users first, as there are many PI website user in english)
So, in respect to the work of PI team (Juan, Carlos...), I ask you to avoid critics on PI documentation. One day it will come and we will not need a book for that !
Regards
