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 have stacked four channels of data - LRGB - of M3. I used the multi-channel processing for RGB and L as a single event. The RGB files are all of the same dimensions while the L is smaller.
When attempting to register/normalize them all to combine in the RGB tool I get this error when attempting to load them as individual light frames. When I attempt to load them as 'processed' frames they show up in the bottom window, but do not index next to that field as being available for processing, and when I attempt to Normalize them the error message that there are no lights to process come up. But when I try to load them as individual light files this error box comes up and it fails.
Hi Eric @flywaldo,
Thank you for sharing this.
Is there a specific reason why the L was created in a single event? (should be possible off course)
When attempting to register/normalize them all to combine in the RGB tool I get this error when attempting to load them as individual light frames.
So you load the 4 integrations to register + normalize them as lights, right? What happens if you disable or enable the multi-channel mode and try loading them again? Is the error still there after a restart of APP? I will try to duplicate this problem. Can you duplicate the error yourself, or is it non-existent after a re-start? (All questions help me in finding the error).
When I attempt to load them as 'processed' frames they show up in the bottom window, but do not index next to that field as being available for processing,
That's normal behaviour, other/processed frames will not be considered for modules 2) to 6), Only light frames. I introduced this to differentiate.
and when I attempt to Normalize them the error message that there are no lights to process come up
So that then is also normal behaviour, since there are no lights loaded.
Â
Â
Kind regards,
Mabula
I just reprocessed all of the subdata in the multichannel setup so they are all the same size. That created four good files. However, when I attempt to load them into the Other/Processed instance they do show up in the bottom window, but not in the file index so when I attempt to normalize them all to prep for RGB integration the error of 'no lights available, so nothing to do' error bonks out the system.
I don't get the Java error after a restart. But am unable to have the processed images loaded into any useful section of the Load page.
If the Other/Processed images are not able to be registered/normalized, then how can I use the RBG integration tool as I did before?
Thank you,
Eric
Ok, I think this is an error on my part to understand the workflow in the new version. I loaded the integrated files into the RGB combine tool and it worked fine. So as long as I use the Multichannel combine process to integrate the subchannels I can just load the resulting files into the combine tool directly instead of registering/normalizing them again together before doing so.
I'll keep working through the new system. Like it a lot so far despite my self-imposed ignorance.
Thanks,
Eric
It seems to have worked!
Ok, I think this is an error on my part to understand the workflow in the new version. I loaded the integrated files into the RGB combine tool and it worked fine. So as long as I use the Multichannel combine process to integrate the subchannels I can just load the resulting files into the combine tool directly instead of registering/normalizing them again together before doing so.
I'll keep working through the new system. Like it a lot so far despite my self-imposed ignorance.
Thanks,
Eric
Hi Eric @flywaldo,
The new multi-channel processing feauture will ensure that all resulting channels are both normalized and registered directly ready to feed into the RGB combine tool 😉
The other workflow should still be possible off course, so I will test to see if I can duplicate the error that you got.
Kind regards,
Mabula
