What's new in SharpCap this week...
Posted: Mon Apr 11, 2022 1:59 pm
Hi folks,
I am going to try out the idea of writing a short post roughly once a week to outline what's new in SharpCap (with a bit more detail than the bullet points on the downloads page) as well as what is likely to be happening next.
This week is a bit of a bumper update with more bug fixes and small changes than usual - largely because there was no update last week.
Bugfixes
In the bugfixes side of things, there are still a number of fixes going in to address small (and perhaps not so small) issues with the new UI option (viewtopic.php?t=4875). New UI bugs fixed this time around include a possible crash when changing the Windows screen scaling with SharpCap running and a loss of control/tool area content after repeated unpin/repin of the control/tool panel. There may still be some font sizing issues when running on a high DPI display, and a possible issue with the image display area freezing. If you are affected by New UI related issues, please post in the New UI thread (link above) or as a separate bug report with as much info as possible.
Other bugfixes include fixing a missing taskbar icon for the 32 bit version, fixing a problem selecting live stacking from Python scritping and fixing a crash if you tried to 'Save exactly as seen' using the button in the mini histogram before the camera has captured a frame.
Gradient Removal
The main feature this time around is the addition of a gradient removal option to the background subtraction control. When enabled, this will try to detect any linear gradient in the background brightness of an image and remove it. This correction is applied to each frame coming from the camera before stacking or saving (just like flat correction, dark subtraction, etc). How accurate will the gradient removal be? Well, it depends on the type of image you are taking...
* Image is mostly background, with small areas of galaxy/nebulosity, or larger areas of faint stuff - the detection of background gradient should be excellent, removing 99% or possibly even more of the gradient
* Image has large areas of bright nebulosity or galaxy, but there are good sized background areas on all sides - should give good results, likely to reduce the gradient by at least 90%
* Image is all galaxy/nebulosity, or galaxy/nebulosity covers one side of the image but not the other - use with caution... In these circumstances the detected and removed 'gradient' might be actually part of the image that you want.
Small Features
I've had a couple of questions recently about whether it is reasonable to continue to use the polar alignment results to make further adjustments through an imaging session - basically people tried leaving SharpCap Polar Align running as they imaged to watch the results to see if they change. Unfortunately this doesn't work - as soon as you move the mount in RA, the results are ruined. I have now added code to detect rotation of the image once you get to the adjustment stage of the Polar Align process, and deliberately stop producing alignment updates if significant further rotation is detected - you will also get a message suggesting that you should restart alignment or undo the rotation.
Other small usability improvements include adding hotkeys to zoom the image (CTRL + to zoom in, CTRL - to zoom out), tweaks to the row noise reduction to reduce the chance of it over-correcting and some changes to ensure that the polar alignment guidance text is always drawn entirely within the camera image, rather than partly out of view in some cases.
Finally, another usability tweak to the Satellite Trail Removal feature is a new notification that appears when the satellite trail removal mode is set to 'Remove'. This notification will remind you to check the sensitivity/minimum trail length/width settings in test mode before using the 'Remove' mode. In some cases where people have just turned the option to 'Remove' without making adjustments, parts of the image are incorrectly detected as trails, basically messing up the image. This seems to be most common currently with globular cluster images.
Coming soon
The next things planned are:
* Improvements to satellite trail removal - trying to deal with non-continuous trails in them and those that vary greatly in brightness along their length, along with trying to reduce the chances of non-satellite parts of the image being incorrectly detected as trails
* Autofocus improvements - a number of small but significantly helpful tweaks to this to make it more usable, more reliable and easier to launch
cheers,
Robin
I am going to try out the idea of writing a short post roughly once a week to outline what's new in SharpCap (with a bit more detail than the bullet points on the downloads page) as well as what is likely to be happening next.
This week is a bit of a bumper update with more bug fixes and small changes than usual - largely because there was no update last week.
Bugfixes
In the bugfixes side of things, there are still a number of fixes going in to address small (and perhaps not so small) issues with the new UI option (viewtopic.php?t=4875). New UI bugs fixed this time around include a possible crash when changing the Windows screen scaling with SharpCap running and a loss of control/tool area content after repeated unpin/repin of the control/tool panel. There may still be some font sizing issues when running on a high DPI display, and a possible issue with the image display area freezing. If you are affected by New UI related issues, please post in the New UI thread (link above) or as a separate bug report with as much info as possible.
Other bugfixes include fixing a missing taskbar icon for the 32 bit version, fixing a problem selecting live stacking from Python scritping and fixing a crash if you tried to 'Save exactly as seen' using the button in the mini histogram before the camera has captured a frame.
Gradient Removal
The main feature this time around is the addition of a gradient removal option to the background subtraction control. When enabled, this will try to detect any linear gradient in the background brightness of an image and remove it. This correction is applied to each frame coming from the camera before stacking or saving (just like flat correction, dark subtraction, etc). How accurate will the gradient removal be? Well, it depends on the type of image you are taking...
* Image is mostly background, with small areas of galaxy/nebulosity, or larger areas of faint stuff - the detection of background gradient should be excellent, removing 99% or possibly even more of the gradient
* Image has large areas of bright nebulosity or galaxy, but there are good sized background areas on all sides - should give good results, likely to reduce the gradient by at least 90%
* Image is all galaxy/nebulosity, or galaxy/nebulosity covers one side of the image but not the other - use with caution... In these circumstances the detected and removed 'gradient' might be actually part of the image that you want.
Small Features
I've had a couple of questions recently about whether it is reasonable to continue to use the polar alignment results to make further adjustments through an imaging session - basically people tried leaving SharpCap Polar Align running as they imaged to watch the results to see if they change. Unfortunately this doesn't work - as soon as you move the mount in RA, the results are ruined. I have now added code to detect rotation of the image once you get to the adjustment stage of the Polar Align process, and deliberately stop producing alignment updates if significant further rotation is detected - you will also get a message suggesting that you should restart alignment or undo the rotation.
Other small usability improvements include adding hotkeys to zoom the image (CTRL + to zoom in, CTRL - to zoom out), tweaks to the row noise reduction to reduce the chance of it over-correcting and some changes to ensure that the polar alignment guidance text is always drawn entirely within the camera image, rather than partly out of view in some cases.
Finally, another usability tweak to the Satellite Trail Removal feature is a new notification that appears when the satellite trail removal mode is set to 'Remove'. This notification will remind you to check the sensitivity/minimum trail length/width settings in test mode before using the 'Remove' mode. In some cases where people have just turned the option to 'Remove' without making adjustments, parts of the image are incorrectly detected as trails, basically messing up the image. This seems to be most common currently with globular cluster images.
Coming soon
The next things planned are:
* Improvements to satellite trail removal - trying to deal with non-continuous trails in them and those that vary greatly in brightness along their length, along with trying to reduce the chances of non-satellite parts of the image being incorrectly detected as trails
* Autofocus improvements - a number of small but significantly helpful tweaks to this to make it more usable, more reliable and easier to launch
cheers,
Robin