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.
At times I use 2 different scopes and cameras on the same target. I saw mention of reference crop but I need clarification. Â
Is it possible at any point prior to Integration to crop the images to the desired final size (specifically to the frame size from the camera/scope with the smaller field of view? Â
Thanks as always.
Â
Andy
@andynowlen Andy,
There are three possible final frame sizes possible: full, reference and crop. When you choose reference, the size of the reference frame will be used for the final crop but it will also match the field of view of the reference frame. If you apply dithering then it is likely that the area of the reference frame will be different than the final area that all images of the smaller camera contribute to. This means that areas of the sky will be included where not all images contribute to.
Why would you want the integration result to be cropped for you?
I notice that in the final "all session" stack the smaller field of view is always noticeable. Whether it is darker or lighter. Â
Usually, I have to then crop to the smallest field of view - which I knew I would have to do at any rate. Â
As a test, I tried a project with three different fields of view. APP dimensions the stack according to the widest field of view. Then if I crop to the narrowest field of view the cropped image is very small. Â
I.E. final three scope stack dimensions = 5100x3600 for instance. Dimensions are fictitious for illustration only
Cropped to the smallest field of view = 2300 x 1700 for instance. Dimensions are fictitious for illustration only
Normally my smallest field of view is 3,000 x 3,000. (Asi533MCpro). So, it seems some resolution and detail might be lost if I am always cropping to the smallest field of view in the end. But I am a total amateur.
This led me to ask the original question.
As always, Thanks much!
Andy
Â
@andynowlen Thanks for the explanation. Have you tried integrating the data of the two telescopes in two separate sessions or completely separately, removing light pollution from them and then integrating them? To do the latter, load them as lights (don't load calibration data), go to tab 6 and click integrate. That may take care of the difference in background brightness between the two of them.
