Feature tracking bug when switching from 8-bit to 16-bit
Posted: Fri May 10, 2024 4:50 pm
Hey!
When using Feature Tracking by moving the camera ROI based on the center of mass, and having "Highlight Features / Center of Mass" enabled, everything works fine with the default settings when shooting in MONO8 colour space. However, when I switch to MONO16, Feature Tracking stops showing a small cross for the center of mass and the tracking goes way off. I am able to get it consistently back to working condition by changing Background Level from the default value of 10% to 0% in the Feature Tracking window. Then it seems to find the center of mass again.
This leads me to suspect there is something wrong with the background level determination. Perhaps it is using 8-bit numbers when operating on 16-bit data, or vice versa.
I am imaging with a 50mm Lunt H-alpha telescope and Player One Neptune-M camera, and using Windows 10 Pro, and Sharpcap 4.12151 64-bit.
When using Feature Tracking by moving the camera ROI based on the center of mass, and having "Highlight Features / Center of Mass" enabled, everything works fine with the default settings when shooting in MONO8 colour space. However, when I switch to MONO16, Feature Tracking stops showing a small cross for the center of mass and the tracking goes way off. I am able to get it consistently back to working condition by changing Background Level from the default value of 10% to 0% in the Feature Tracking window. Then it seems to find the center of mass again.
This leads me to suspect there is something wrong with the background level determination. Perhaps it is using 8-bit numbers when operating on 16-bit data, or vice versa.
I am imaging with a 50mm Lunt H-alpha telescope and Player One Neptune-M camera, and using Windows 10 Pro, and Sharpcap 4.12151 64-bit.