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.
Hi,
Would it be possible to add a Canon Banding Reduction option ?
Thanks,
Bob
Do you see it remaining an issue in a stack? I think it should already be a signal in the bias or darks, might be mistaken.. Dithering will also reduce this.
Hi Vincent,
Yes, the banding is visible in the stack (see attached (extremely stretched) photos).
You are right to say it should be gone with darks.
However, since I use dithering and Bad Pixel Map, I found that I can process my photos with only Biases and Flats (as per option 1 in sticky post "Data calibration principles/rules") and achieve nearly the same result as with darks once the remaining banding is removed from the stack.
For this I use the process integrated in other processing softwares but it would be nice to have this function directly into APP.
edit: Maybe the banding reduction would be even more effective if applied on each sub, during calibration ?
Yes that would work better, but it’s not going to improve the data dramatically I think. It will reduce it of course, but I think you still get a better result in this case by using darks as well. That will be the actual data and not “guessed” by an algorithm.
In fact, it seems that this problem cannot be entirely solved with darks as the banding is not constant from one image to another.
There was a Yahoo group on this subject but those groups are now dead.
I did a test adding darks and here is the result.
Even though the problem has diminished, we can see that there are still bands.
I requested this feature because it is present in other programs and I thought it was a classic.
Unfortunately, this problem only affects Canon cameras (old ones ?) and only a few of them, I may be the only one who needs this feature.
