Ive set the preference to fits. yet for some reason, it keeps sneaking png format in there, often when sharpcap crashes for some reason.
this is utterly enraging, because i cant use PNG format, and though yes i can convert it, the resulting images are slightly off the rest of my sequence and the entire nights observing is lost if i dont catch it.
I can see no reason at all to use a png format, let alone have it default to it. can we PLEASE remove this format entirely? it taking a reasonably decent application and making it untrustworthy.
thanks
Phoenix
sharpcap keeps reverting to PNG format
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
-
admin
- Site Admin
- Posts: 17524
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: sharpcap keeps reverting to PNG format
Hi,
the PNG format is definitely needed, since it provides a good option for those wanting to save in a way that is immediately viewable in a normal image viewing application. The other options have issues (JPG has lossy compression, TIFF either has no compression or compression that is not always compatible with some viewing applications).
The file format that you get from saving in most cases is determined as follows:
* If the 'Output Format' is set to non-auto then the format set in the 'Output Format' control is used
* If the 'Output Format' is set to auto, then it will change between the 'Preferred Video Format' and 'Preferred Still Format' as defined in the settings (video format for short exposures, still format for longer exposures)
In a few places (creating dark/flat frames mostly), the 'Preferred Still Format' can override the selected output format if the selected output format is unsuitable (ie lossy compression or cannot handle more than 8 bits of bit depth).
There are a small number of places where PNG files are deliberately created regardless of your settings - these are places where the primary use of the saved file is likely to be to immediately view or share rather than perform further processing. I am guessing you may be encountering one of these places... The places where this happens include:
* Live Stacking, when saving 'with adjustments' or 'exactly as seen'. Both of these are stretched/processed/enhanced images that are generally suitable for immediate viewing. Saving as 16 or 32 bit stack will give FITS data without stretching/processing applied
* Using the 'Save image exactly as shown' button in the mini histogram stretch area - again saving a processed image for viewing
* Planetary live stacking saves - again, saving processed images
Now, you mention crashing triggering PNG files - this could happen if you are live stacking when SharpCap crashes, as SharpCap will try to 'Emergency Save' your live stack before closing in this situation. Since SharpCap cannot be sure what format you really wanted at that point it will emergency save as:
* 16 bit stack without processing, which should go to the preferred output format - ie FITS if selected
* 32 bit stack without processing, again to preferred output format (only if the option to auto save includes 32 bits in the live stack settings tab)
* An 'As seen' version, which will be PNG
So, maybe you have had a crash while live stacking and are getting a saved PNG at that point, but there should also be a 16 bit FITS copy of the stacked data saved too (it's saved before the PNG in the emergency save).
So, the above covers how things are supposed to work - maybe you can fit that in with what you have encountered and understand where your PNG files have come from and why. If it still doesn't make sense, or you think it's not behaving as described above, then let me know as there may be an issue that I am currently unaware of.
thanks,
Robin
the PNG format is definitely needed, since it provides a good option for those wanting to save in a way that is immediately viewable in a normal image viewing application. The other options have issues (JPG has lossy compression, TIFF either has no compression or compression that is not always compatible with some viewing applications).
The file format that you get from saving in most cases is determined as follows:
* If the 'Output Format' is set to non-auto then the format set in the 'Output Format' control is used
* If the 'Output Format' is set to auto, then it will change between the 'Preferred Video Format' and 'Preferred Still Format' as defined in the settings (video format for short exposures, still format for longer exposures)
In a few places (creating dark/flat frames mostly), the 'Preferred Still Format' can override the selected output format if the selected output format is unsuitable (ie lossy compression or cannot handle more than 8 bits of bit depth).
There are a small number of places where PNG files are deliberately created regardless of your settings - these are places where the primary use of the saved file is likely to be to immediately view or share rather than perform further processing. I am guessing you may be encountering one of these places... The places where this happens include:
* Live Stacking, when saving 'with adjustments' or 'exactly as seen'. Both of these are stretched/processed/enhanced images that are generally suitable for immediate viewing. Saving as 16 or 32 bit stack will give FITS data without stretching/processing applied
* Using the 'Save image exactly as shown' button in the mini histogram stretch area - again saving a processed image for viewing
* Planetary live stacking saves - again, saving processed images
Now, you mention crashing triggering PNG files - this could happen if you are live stacking when SharpCap crashes, as SharpCap will try to 'Emergency Save' your live stack before closing in this situation. Since SharpCap cannot be sure what format you really wanted at that point it will emergency save as:
* 16 bit stack without processing, which should go to the preferred output format - ie FITS if selected
* 32 bit stack without processing, again to preferred output format (only if the option to auto save includes 32 bits in the live stack settings tab)
* An 'As seen' version, which will be PNG
So, maybe you have had a crash while live stacking and are getting a saved PNG at that point, but there should also be a 16 bit FITS copy of the stacked data saved too (it's saved before the PNG in the emergency save).
So, the above covers how things are supposed to work - maybe you can fit that in with what you have encountered and understand where your PNG files have come from and why. If it still doesn't make sense, or you think it's not behaving as described above, then let me know as there may be an issue that I am currently unaware of.
thanks,
Robin