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.
Sometimes when I include my bias I get a completely black or completely white frame upon integration. Removing the bias and reintegrating renders and nice image. I think it happens mostly with hydrogen Alpha but RGB also but only sometimes. Have you any idea why this might happen?
@gregwrca, yes I do. It has to do with how data calibration works at the moment in APP. In APP 1.060 this shouldn't happen anymore 😉
Let me explain: in APP (versions lower than 1.060) if you load bias and dark frames of the same ISO/gain, then the darks will be subtracted by a masterbias created form the bias frames. If you calibrate lights then, you need to load both masterdark and masterbias for correct calibration.
But if you only create a masterdark by loading only darks (no bias/masterbias) then the bias signal and pedestal is not subtracted from the darks in creation of the masterdark.
In that case, if you later add a masterbias to the masterdark and try to calibrate your lights, you will be subtracting the bias signal and pedestal twice from your light frames. And that will explain the problem that you describe.
I understand this is a bit complicated and not very user friendly. So in APP 1.060 the new calibration engine should prevent problems like this 😉
Cheers,
Mabula
So skip bias for now? Will that work? Or should I load the master bias when I create my darks and flats Masters and leave it there for every step of the way
