May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
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.
Having some weird issues when trying to adjust individual channels of color with this tool. see attached screen shot. it does it with any INDIVIDUAL COLOR channel. however if i use ALL then it works fine. also happens with the previous APP version as well. Â
i'm using my osc asi294mc pro. it must have something to do with this? i've only been using this camera a few times as its new. in tab (0) i have chosen RGGB for pattern and airy disc prior to loading files. any advice? thanks!
Hi @cheastside,
I am not quite sure what is happening. You mean that if you want to adjust red pixels, so selecting red to adjust, then the image becomes that white all of a sudden?
Perhaps you can send me the data so I can test what is happening?
Mabula
yes, that's correct. selecting and editing single color channel then hit calculate produces what's shown in the screen grab. my fit file is much larger than 30mb so here's a link
https://drive.google.com/drive/folders/1vSxaVTXOU1QbhyHq0AlL2MFiEQ4fS72Q?usp=sharing
Hi Cory,
Thank you very much for sharing your issue and uploading your data.
I see the same problem, your data somehow triggers a serious problem in the HSL Selective Color tool. Each pixel that is manipulated ends up with a null value... I will investigate tomorrow to find the cause and hopefully fix it quickly.
I have one additional question for now: what capture software are you using?
Mabula
Hi Cory @cheastside,
I have found the problem and I have fixed it. The bright M31 core upset the tool... it clearly was not a data nor data capture issue 😉
It will work properly in 1.083 stable !
Mabula
