Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
Based on what this article describes (the theoretical part seems sound),
https://siril.org/tutorials/synthetic-biases/
could the option to add a value (in ADU) instead of bias (or masterbias) to avoid adding noise to the image be included in APP?
Thanks for your attention.
Hi @anofeles,
The method as offered and discussed can be used for sure.
But... a perfectly flat bias or darkflat to calibrate flat frames (or lights) by using only an offset instead of real sensor data is something which I would only contemplate if it were impossible to create proper bias, darks or darkflats. And this is not a very difficult task I think, so why would you want to go down that route?
I would advice to simply shoot enough bias/dark/darkflats and you will get proper data calibration on pixel AND larger than 1 pixel scale (there are definite sensor noise patterns in clusters on these new CMOS sensors). The static offset simply can't offer that so it will be less good, especially on sensors that are getting of age where even the bias signal can be quite different across the whole sensor. You would be surprised what bias signal an old cmos or ccd camera can give when compared to the signal that the sensor gave when it was brand new!
In my opinion, the static offset method is just a lazy person's way to accomplish something with less precision and definitely more error-prone when compared to proper data calibration where the current state of the camera is always included, so it is a bit difficult to advice this to users even. I would not.
But..., we will try to add it as an option though at some point. It is on our ToDo list.
Mabula
Â
Â
Thanks for taking this into account.
Yes, obviously, biasing is not very time consuming (especially compared to darks or flats). It's not because of the time that can be invested in their creation but because of the noise they can introduce in the image. It would only be within the reach of the most modern CMOS sensors, of course, but it would be a way to try to avoid it.
Taken from siril's website:
"Taking a bias image must be done at the fastest possible speed, to avoid adding signal and thermal noise that would interfere with the processing. However, a bias will contain, in addition to its offset level, a certain level of noise. This is why we advise you to take as many biases as possible in order to minimize the noise in the final master. Remember that when you subtract two images, their respective noise is added. Therefore, using 20 biases introduces more noise into the final image than using 200 biases".
As said, thanks, Mabula, for taking it into consideration.
Best regards...
Â
