The clip is just what I needed to review the practical aspects of GHS as I start to use it. GHS is an amazing tool, David and Mike, and I love what it's brought to the table. Thanks for this clip, Molly...I'll likely come back to it often.
We generally get what we need with HT followed by HDRMT/CCHDRMT when appropriate, or MaskedStretch, but this is very interesting and will compare again with the newer process, which replaces the script. Thanks Mike and TAIC. FYI, it's ARC-sinh rather than ARCH-sinh.
I tried to follow the same steps on M33, but when I try recover the colours with Col button, it messes with star colour. Any suggestion on how to avoid that ? Thanks
A couple of questions: The built-in GHS in PixInsight does not have all the same features in it's dialog box as is shown in this video. Close, but not exact. Is the buil-in version the same/have the same capabilities/version as the stand alone script? I've read that once the built-in version is in PixInsight, it will no longer load/run the external scripted version. Is this correct? Using the script version rather than the PI process raises another issue (for me). In the zoom feature, 200 barely makes the data evident on the left hand side. (It is 412 frames of M42, exposures used to build and HDR image (30 sec, 60 sec, and 180sec for each narrowband filter). Another issue is with the "create new image" function. It appears to be creating a backup copy of the original with the new image name, while stretching the original.
Some people have been confused, now that GHS is available in process form, thinking it is now native/built-in to PixInsight. It is not, the process version still needs to be downloaded from the ghsastro repository just like the script does. There is, so far as we know, no proposal to incorporate a GHS process into the standard PixInsight distribution - at least, the PI team have not approached us about this. From our point of view we remain committed to supporting both the process and the script version for the foreseeable future - ie what you have read is not true as things currently stand! As regards the different look between the script and the process interfaces, the process version integrates with the PixInsight standard environment, including the real-time preview and readout functionality. This means less needs to be included within the process interface itself. This is the main reason why the process interface looks like it has less options. I hope this helps. CS, Mike
![All About Dithering [TAIC Short]](http://i.ytimg.com/vi/7UAp4uzSnj0/mqdefault.jpg)
![All About Dithering [TAIC Short]](/img/tr.png)
I very much appreciate these clips. They are a nice addition to the channel.
The clip is just what I needed to review the practical aspects of GHS as I start to use it. GHS is an amazing tool, David and Mike, and I love what it's brought to the table. Thanks for this clip, Molly...I'll likely come back to it often.
This is an absolute game changer, especially for targets that have extremely bright and also faint sections like orion
Amazing straightforward and clear presentation Mike!
Thank you ! Looking forward to applying
Thanks for the clear presentation!
Wow! That's impressive! Nice work!
Excellent work!
This is a great presentation ! Thanks !
Thanks for the tips.
Increíble tool ! Thanks by the clip !!
We generally get what we need with HT followed by HDRMT/CCHDRMT when appropriate, or MaskedStretch, but this is very interesting and will compare again with the newer process, which replaces the script. Thanks Mike and TAIC. FYI, it's ARC-sinh rather than ARCH-sinh.
Thanks for the very helpful video! Question: filtered subs are you starting with for the M51 image? LRGB or something else? Thanks!
I tried to follow the same steps on M33, but when I try recover the colours with Col button, it messes with star colour.
Any suggestion on how to avoid that ?
Thanks
A couple of questions: The built-in GHS in PixInsight does not have all the same features in it's dialog box as is shown in this video. Close, but not exact. Is the buil-in version the same/have the same capabilities/version as the stand alone script?
I've read that once the built-in version is in PixInsight, it will no longer load/run the external scripted version. Is this correct?
Using the script version rather than the PI process raises another issue (for me). In the zoom feature, 200 barely makes the data evident on the left hand side. (It is 412 frames of M42, exposures used to build and HDR image (30 sec, 60 sec, and 180sec for each narrowband filter).
Another issue is with the "create new image" function. It appears to be creating a backup copy of the original with the new image name, while stretching the original.
Some people have been confused, now that GHS is available in process form, thinking it is now native/built-in to PixInsight. It is not, the process version still needs to be downloaded from the ghsastro repository just like the script does. There is, so far as we know, no proposal to incorporate a GHS process into the standard PixInsight distribution - at least, the PI team have not approached us about this. From our point of view we remain committed to supporting both the process and the script version for the foreseeable future - ie what you have read is not true as things currently stand!
As regards the different look between the script and the process interfaces, the process version integrates with the PixInsight standard environment, including the real-time preview and readout functionality. This means less needs to be included within the process interface itself. This is the main reason why the process interface looks like it has less options.
I hope this helps.
CS, Mike