What calibration fi...
 
Share:
Notifications
Clear all

2026-10-09 APP 2.0.0-beta48 has been released !

This is mainly a bug fix release for the reported bugs in beta47. In addition it has a significant User Interface performance improvement noticable when you need to process 1000s of images in APP.

2026-10-03 APP 2.0.0-beta47 has been released !

This is a very big release... many code optimizations/rewrites, many parts of APP are much faster and more precise, especially star analysis and registration are much faster ! Big mosaics will go much faster 🙂

And we introduce a new preview filter, which includes the new Adaptive Deep Sky Stretch and a General Levels Stretch, this has been long over due. The old preview filter (the panel on the right side to stretch and preview your data) has not been updated for a couple of years and it is a critical part of any APP session.

Adaptive Deep Sky Stretch or ADSS is a much more intuitive stretch algorithm. It is also color preserving (which is a great new addition in itself ! ) which means that the highlights are no longer bleached, color is maintained from the linear data while stretching. You can simply stretch your data using the sky background level and signal width sliders which work much easier and more intuitive. You no longer need to fiddle with the old complicated sliders with zoom buttons. All the zoom buttons for the sliders are made redundant. And you can enter slider values in the slider value fields yourself. I will make a youtube video in the coming days to explain and fully introduce ADSS. Once the video is ready, it will be highlighted on the forum.

RGB Combine upgrade !. The RGB Combine Tool has been rewritten mostly. The tool is faster and easier to use and most importantly, the Luminance slider to inject a luminance channel or channels into the RGB composite is now working correctly. It no longer bleaches the RGB colors. Combined with the new ADSS preview, you will get much better and easier great composites with great color! I will also explain this in a new youtube video.

What calibration files do we actually need….

9 Posts
4 Users
1 Reactions
3,341 Views
(@takfsq85)
Main Sequence Star
Joined: 5 years ago
Posts: 33
Topic starter  

Hello,

I have one of the new QHY268c CMOS imx571 based cameras, and am reading more and more that Darks and dark flats are just not needed with these cameras, and all you need is Lights, flats and bias, is this correct, as the sensors are so clean that darks and dark flats are just not needed, now what about hot and cold pixels, well won’t they be sorted in dithering and or rejection during the stacking…??

I realise different cameras require different calibration, but my concern is am I wasting time on a dark library if not needed…..with my camera….

Or am I hearing incorrect information..?

cheers 👍🏼



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

Some sensors do behave very nicely. But hot pixel detection I think would still be necessary (though I don't know the details of this sensor in particular) and while dithering solves that to some extent, it won't be 100%. I would still make a dark library and just test it out, they can be used for quite a while and don't take too much time when the skies are clouded anyway. ;)\

Another option would be: Create a nice Bad Pixel Map from a proper long dark and use that instead of the darks in most cases. That might be a good thing to try as well, create a long dark without any cooling to get it noisy, make a BPM out of that and us the BPM instead of the darks for all your exposures. Of course, this only work well when there is no amp-glow whatsoever.

If you use flats, they do need calibration from the bias signal, so for the flats I would still use dark-flats.



   
ReplyQuote
(@takfsq85)
Main Sequence Star
Joined: 5 years ago
Posts: 33
Topic starter  

Dont the hot and cold pixels get rejected in calibration anyway, aren’t they sorted there…??

Amp glow is a thing of the past with this 16 bit sensors, it’s been eliminated 



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

They are sorted in calibration yes, by the use of darks or a Bad Pixel Map.



   
ReplyQuote
(@sparna)
Molecular Cloud
Joined: 6 years ago
Posts: 4
 
Posted by: @vincent-mod

Some sensors do behave very nicely. But hot pixel detection I think would still be necessary (though I don't know the details of this sensor in particular) and while dithering solves that to some extent, it won't be 100%. I would still make a dark library and just test it out, they can be used for quite a while and don't take too much time when the skies are clouded anyway. ;)\

Another option would be: Create a nice Bad Pixel Map from a proper long dark and use that instead of the darks in most cases. That might be a good thing to try as well, create a long dark without any cooling to get it noisy, make a BPM out of that and us the BPM instead of the darks for all your exposures. Of course, this only work well when there is no amp-glow whatsoever.

If you use flats, they do need calibration from the bias signal, so for the flats I would still use dark-flats.

This is good advice - I use a QHY268 and have done extensive tests with darks, and across visual comparisons and statistical noise comparisons in different programs couldn't see any meaningful difference. I have a TON of hot pixels however (when I am shooting with a duoband filter at least), and making a solid BPM via this method works very well to remove them. Vital part of the process IMO - especially since I have backed off a little on the frequency of my dithers, due to my mount taking a while to recover and the super low amount of fixed pattern noise on this sensor.

 



   
ReplyQuote
(@astrokrause)
Hydrogen Atom
Joined: 4 years ago
Posts: 2
 

Hi Vincent,

I’m relatively new with APP and astrophotography in general, but had a question regarding creating BPM’s for IMX571 cameras suggested in this forum. I own an OSC RisingCam IMX571 and want to ensure I calibrate most effectively, efficiently, and consistently. You mentioned creating a BPM from a long, noisy dark. Could this be created from just one dark? And can it be created on its own (no lights, flats, etc…)? And when created, can I just use the BPM along with flats and dark flats only, for future use?

Thanks,

David



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

This can be done with a single dark yes and it can be created on its own, just load the dark (or a few darks) and let it create the masters (leave the BPM creation checked of course). This BPM can be used with any processing it never destroys data basically. If your sensor doesn't have amp-glow, you may even see if it's enough to only use the BPM without darks. A BPM can typically be used for a year or even longer, but of course your sensor characteristics will change, so do check from time to time if it still performs well. You can easily do this by zooming into hot pixels of 1 light, add the BPM and then switch to "l-calibrated" on top of the preview window. APP will then calibrate a single light and show you what happens with your calibration data added, before you'd have to wait for an entire integration.



   
ReplyQuote
(@astrokrause)
Hydrogen Atom
Joined: 4 years ago
Posts: 2
 

Thank you! One point of clarification, could the BPM substitute for both bias as well as darks in this case?


This post was modified 4 years ago by David Krause

   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

No, a BPM is there purely for hot and cold (you need flats for that, though modern sensors almost don't have those anymore) pixels. Bias or darkflats are required for proper flat calibration.



   
ReplyQuote
Share: