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 trying to combine data from an Atik Horizon 2 colour camera and a ZWO ASI1600 mono.
These two cameras use the same generic chip and both are using a Samyang 135 F2 lens.
If I process the RGB and Mono data separately APP works ok but when I try to do both data sets together APP gets about 18% the way through Normalising and then fails.
Screen shots attached of error message. !6 Gb of ram is used by APP. Help!
Â
I see the error mentioning an overlap issue, does the data share at least say 20% overlap? Shouldn't cause an error like this I think, but just to confirm. Can you show a sub from one and from the other as well? And how did you configure APP itself?
@vincent-mod
The individual Fits files exceed the 30mb upload but I have attached two Jpgs from another data set which have been processed using APP as RGB and LUM separately which will give an indication of the alinement's
.These data sets also produce the same error message when processing together
For APP config the only setting change was for the RGB raw files to GRBG.
Â
Here is a list of settings used
Raw/Fits GRGB
Load Full set of calibration frames. RGB data to RGB session 1. Luminance data to Luminance
Calibrate no change used defaults
Analyse stars no change used defaults
Register No change used defaults
APP ran through all the above without issues
Normalise Have tried all combinations of Mode/Method/Scale...error message
So are you processing mono and RGB at the same time? That is not, yet, possible like that. If you want to do that it's best to first save the split frames of the RGB (saving them as mono R, G and B) and then load those in to be registered together with the mono data. I would do that with the integrated RGB and the integrated mono data.
@vincent-mod
Thanks for the advice. Will give that a go this afternoon. I still load both the RGB and luminance data files and calibration as before but when it comes to Normalise I untick the luminance mono data and normalise the RGB per channel, then untick those and tick the Lum data and normalise those. Then tick all to integrate.
Have I understood what to do correctly?
Â
Not really. 🙂 You do need to normalize them together as well. You first load in your RGB data, then go to tab 2 and calibrate, then all the way down on tab 2 you can select "split channels" and then save them. You'll then have calibrated R, G and B frames. These you can load in again as mono data and then you add the mono luminance data and proceed with integrating everything. This will result in integrated R, G, B and L data frames which you can combine in the RGBCombine tool.
Followed your reply and success!
I built a dual imaging rig with two Samyang 135 F2 lenses and am impressed with the results. Many thanks for getting back to me.
That's awesome, I always love when giving advice works out. 🙂 Very nice result! And clever to have a dual system, make use of the spare nights we have.
