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.
Hi Mabula,
with rev. 2.0.0.39 I can select f.e. Multi-NB extract H-a + Oiii. In the documentation is noted that automatically 4 files are generated in Register 6. But I get only on file and this is the classical Multiband Color.
Also if i choose f.e. Multi-NB extract Oiii I get also a classical Multiband Color with no separated Oiii Mono image.
Whats wrong ?
Thank you
Werner
here an example. Both files are made with a OSC (QHY268C) and the Optolong L-Ultimate (Ha+Oiii)
Selected Multinarrowband extract in Tab 0
Two Multinarrowband files loaded
after ingetration in Tab 6 I get only one file ... here TEST.fits (NOT 4 files). Test.fits is a multicolor file, no Monofiles !
Are you trying to do the operation using already stacked and debayered FITS?
Try on the raw fits files and see if the issue persists.
/Stefan
Hi Sefan,
yes, normaly my workflow is that I extract NB-Channels if I´m starting postprocessing and if I´m ready with all sessions. I have tried with unstacked raw files and this works.
Seems to be a bug that stacked files can not be extracted.
CS
Werner
I dont think it is a bug though. The difference between stacked and raw fits is that the stacked is already debayered.
Split chanels in the stacked files and stack B and G channels to make a master Oiii.
until 2.0.0.38 it has worked so far because this was my workflow for years.
I agree with @digitaliz-se. You seem to be trying to combine already extracted NB files. The multi-band extract feature is for extracting NB portions of OSC files. Your HO1 and HO2 are presumably already NB files and are ready for combining in the RGB combine tool.
The files beginning with HOxxxx are stacked OSC files made with a dual-narrowband filter, so they are RGB. In the past until 2.0.0.38 it was possible to extract different narrowband from stacked files like "extract Oiii" etc. As a result I got a mono file with f.e. Oiii or Ha.
If this is not a bug in 2.0.0.39 than I have to change my workflow in the future. But how I said ... in older versions it has worked.
Hi Werner @wstumpferlgmx-de,
Thank you very much for sharing your issue. And thanks everyone for your suggestions as well.
All the Bayer/X-Trans algorithms in 0) COLOR SETTINGS (or the old RAW/FITS menu) will only affect data that needs to be demosaiced/debayered.
All stacks/integrations will always be already debayered/demosaiced and so the algorihms in 0) Color Settings will do nothing. I can not see how older APP version would do so either.
I also see from the filenames in your screenshot that the files are run through GraXpert? The output is very likely only 3-channel RGB data instead of 1 channel CFA data that needs to be debayered.
Let me know if this makes sense and/or solves this.
Mabula
