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.
My base image fits image files size is 5440x3648 but after running integration the image size(s) change - by a few pixels
eg. 5440 x 3648 Ha
5442 x 3652 OIII
5446 x 3652 SII this means that when I try to final process the files in Star Tools it recognises they are changed so can't open as a Layered composite - to work on.. Is there a reason / or an option to prevent the integrated files being changed in this way / a fix ..
regards David
That is certainly a bit strange, I don't think it should do that. You processed them entirely in APP, not touched by anything else?
yes straight fit files from the the camera (AA 183M).
just double checked the original dta fit files are all 5440 x 3648
which is the resolution size for that camera..
David
Also for this issue I will have to tag our programmer, @bula-admin . 🙂 Never heard the issue before though.
Hi David and Vincent @prioryart @vincent-mod
This is not strange, this is due to the full composition mode in 6) Integrate.
Most applications, by default use the reference composition mode.
In 6) integrate, the full composition mode will have the effect that all integrations will contain all pixels (therefore it's called full ) of all the frames in the integration. So, unless all frames have the exact same composition on a pixel basis, integrations will be larger than the reference frame.
On the other hand, reference composition mode, will only integrate to the field of view of the reference frame which will result in integrations that have the exact same size as the reference frame. Which David is expecting here.
If you are fine with losing data at the borders of the field of view and simply have the same dimensions as the reference frame, you can use the reference composition mode.
But....., this is really not recommended.
APP has a multi-channel workflow to ensure that all data (all pixels) is used, also at the borders, and it will give you several integrations per channel/filter that are registered to each other and that will have the same image dimensions.
Please check this tutorial:
It’s using broadband filters, but the principle is the same. This is the best and most automated workflow for your cause 😉
Please let us know if you need more assistance.
Kind regards,
Mabula
