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.
I am using a ZWO ASI533MC Pro OSC camera and a L-Enhance filter. my integrated subs are ending up green. On LOAD, I set the pattern as: supported, algorithm as: Ha-OIII color, ticked Force Bayer and ticked use camera color matrix.
I suspect I am making a stupid error but cannot find the problem.
Advice appreciated
Frank
Do you need the force debayer option? And do you mean somewhat green or solid green?
Ah yes that's green alright. It's normal for an OSC sensor to have more green signal, but this is quite a bit. Can you tell me more about the APP version you use and what your data workflow is, calibration files and such?
It is version 2.0.0-beta4 amd64. I get the same result with or without calibration files.
Funnily enough, I have subsequently discovered that besides showing me the 'green' image and staying that way when I save as a tiff, APP also saved a fits file, which when I open is OK, in full colour.
I then did another process, and the same happened, I am faced with a green image on my monitor and saves as green tiff, but a correct fits is saved.
Quite peculiar.
Further to my reply above, clear skies have allowed me to have another go. This time I took 120 subs of 60sec together with full set of calibration files, darks, flats, etc.
I processed the lights and all the subs. This time the integration produced a blue file, and saved the fits file as blue.
I then processed again but this time without any of the calibration files. The integration produced a green file on screen, which when I saved as a tiff was also green. However APP had also saved a fits file which when I converted to .png produced a coloured image as expected.
Up to the previous post, all was well with APP producing 'normal' images. It seems to me that the recent upgrade to APP is the culprit.
Is there a way to get back to the earlier APP in order to check this?
If I can't get this sorted I will have to consider moving to, maybe, Pixinsight, as at the moment it is all rubbish.
You mention you're on beta 4, can you download beta 22? There are quite a few bugs that we squashed in between.
Hi Vincent
Sorry to have been a while but I've been working my way through the versions. I have been installing different versions and doing a process, starting at 1.083. I worked my way up through the 2.0.0-betas and the green image appeared at 2.0.0-beta19 and subsequent ones. It seems that 2.0.0-beta18 works OK.
As I mentioned before, the system actually saves a file which opens OK with no green cast, but the image shown and which some forther processing can be done is the green cast one.
I hope this helps
Hi Frank @thedwo,
To me this seems to indicate a problem with the calibration data that you provide? since the image without calibration looks fine to me? It is a bit hard for me to understand what is happening here and what your workflow is. The problem that you describe is not known and I do not recognize what is happening, so maybe it will be best if I have a look at your data and analyse to understand what is going here?
Do you want me to have a look at your data? If so, please upload your data here and let me know how your workflow goes, so please share the settings that you use in 0) to 6) so I can understand any problems here:
https://upload.astropixelprocessor.com/
username: uploadData
password: uploadTestData
please make a folder with your name and issue like : Frank-GreenBlue-Integrations
and let me know once uploaded, thanks.
Mabula
Hi Mabula
Thanks for the contact.. I am uploading a folder entitled Test_Beta18-andBeta25, this has a smaller number of lights, 30 as opposed to 90 but all the calib files used previously. There are also folders giving results for the tests with Beta 18 and Beta 25 respectively. In each of these I saved a tiff file. This tiff is the file shown on the screen, when Integration completed.
I also created a file before I uploaded called Frank_Green-Integration, but that was premature so is empty and the system would not allow me to delete it.
As for the process, I set Section 0) Raw/Fits to Ha-OIII color. All other sections were set at default, to keep it simple.
You will see the tiff is Beta 18 is as expected, whereas the tiff in Beta 25 is green.
I hope this helps in the development of APP, and look forward to hearing further.
Frank
Hi Frank @thedwo,
Thank you very much for sharing your data.
I have tested it today and all is working as expected in beta25, I do not get a green integration with default settings (you can set defaults with the CFG button):
And if i save this as a TIFF with the save button below the histogram, all is fine as well:
But... if I look at the uncalibrated lights, they are very green indeed which can be normal for OSC data. So if you would turn of background neutralization in 5)Normalize, you will surely end up with a green integration and yes indeed, I turned it off and this what I get :
So, you must have disabled background neutralization at some point? Please be aware that these new APP sessions keep all those settings the same with an APP restart. You can always go back to the safe defaults, with the CFG button 😉
Mabula
Hi Mabula
Many thanks for the response and the solution to my problems. I now realise this was caused by my inadvertent clicking of the Background Neutralisation tab. I would like to apologise for causing you this extra work, when there is always much to do to in the development of this great software. I suppose it is rather ironic really. I was one of those asking for APP to remember our settings once it closes down. This time that came back to bite me 😉
Thanks again
Frank
Hi Frank @thedwo,
It is no problem ;-), I am glad that we have a clear explanation for your issue in this case !
Mabula


