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.
Hello There!
Can anyone explain it to me why is my Ha image is 3 pixels smaller than the rest of the images (SII and OIII)?
The subs are the same and I'm trying to make a Hubble palette image from my OSC data.
The 3 algorithms I used was "Ha-OIII extract Ha", "Ha-OIII extract OIII" and "Ha-OIII mono" and the one I made with the "Ha-OIII extract Ha" turned out to be 3 pixels shorter in the Y dimension than the rest and now I cannot combine it to RGB image, because it says the dimensions are not the same.
I'm using the 2.0.0-beta14 version of APP.
Edit: Same result with beta19.
Edit2:
When I crop the images in APP to match the dimensions then I get the following error message when I press the calculate button in the combine RGB menu:
When I close APP then open it up again and the only menu I'm using is the combine RGB then when I select az image to add, the channel assign window pops up 3 times at every image. There's clearly something I'm doing wrong or something is wrong. 🙂
Please, help!
Thank you!
Hi @rapid,
This problem occurs because you probably registered the stacks indepently from each other.
You need to register the "Ha-OIII extract Ha", "Ha-OIII extract OIII" and "Ha-OIII mono" results first. Then they will have the same dimensions. The difference in image dimensions are caused by the full composition mode in 6) integrate where it will create a field of view for the stack so no data is lost.
Even if the stacks had the same resolution, they would not be registered yet to each other as well.
So load the 3 stacks as lights, and register them in 4) Register, then save registered lights at the bottom in menu 4). Those saved registered lights are competely compatibel for a composite now 😉
If you add an image to RGB combine and the channel assing window pops up 3x, you are loading a color image which has 3 channels and you need to assign all 3 channels then.
Mabula
Thank you!
Now the combine RGB went flawlessly with the registered FITS.
Yes, it seems the cropped FITS was saved in RGB with APP, but the registered files are mono now.
I love your program! It's the most user friendly software out there with tremendous knowledge and functions packed inside.
Keep up the good work!
Hi @rapid,
The above issues will all be fixed in the next 2.0.0-beta25 release 😉
I will try to release it soon !
Mabula
Hi all,
Please try 2.0.0-beta25 which has been released with the fix for this issue.
https://www.astropixelprocessor.com/downloads/
Mabula
