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.
Hey all, I have a rather gnarly project that is giving weird results. Due to [long story, details elided], I had to work on a target that was pretty low to the horizon and had the Moon nearby for a couple nights besides. I was getting frames as low as 15° altitude, and the gradients were pretty savage on the two Moon nights. To add to the challenge, the desired FOV was a bit bigger than my rig's, and I wound up with frames oriented every which way.
APP did an absolutely superb job making a silk-purse image out of my sow's-ear data, with one little exception: In the center of the image, as nearly as I can tell, the red, green, blue, and luminance integrations do not coincide. What's weird is that that's the only place in the image where that's true. It's also about the only part of the image covered by every single frame in the integration. This shows the effect after LRGB combination (it's no better with just RGB). You can tell that the effect is almost gone by the edges of this highly zoomed-in crop. The settings for registration and integration are also shown, along with a before-and-after-LPC pair on the L channel just for "Wow, APP does a great job" bragging. (The seam at lower left wouldn't appear in the final crop so I didn't bother correcting it any more.)
Any ideas? Do each session's panels separately, run LPC on each, then register and integrate those? Turn off "same camera and optics"?
Thanks for your help!
LPC-corrected full integration, pre-correction integration
Zoomed-in crop showing the problem, integration settings, registration settings
I tried it again on my PC (first try was on my Intel Mac), turning off "same camera and optics". Not sure which difference made the difference, but I got integrations that registered perfectly for RGB combination. Hmm. Still interested in hearing why that might be the case.
Rick
I'm assuming you integrated each panel separately and then combined them into a mosaic. If that is not the case then what I am about to say will not apply.
My understanding is that when combining panels into a mosaic you should always disable 'same camera and optics'. If you don't I think the projective model is applied twice leading to geometry errors that can affect registration.
I hope I've got this right, but I think it can explain your results.
JC
