June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
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.
Tutorials & Workflows
2
Posts
2
Users
0
Reactions
1,616
Views
Topic starter
April 30, 2024 15:43
Hi all,
It seems that the reading mode is not taken into account when creating masters.
This field exists in the FITS headers but is not written in the created masters.
In the figure below, READOUTM can be "Low Conversation Gain" or "High Conversation gain". And APP does not differentiate between the 2 types of data.
How to deal with that?
This topic was modified 2 years ago 3 times by Francis Moreau
May 22, 2024 22:32
I would write it to the file name for now, that is what I am doing. Or, settle on one mode. I have a OGMA AP26MC which is a IMX571 sensor. I did the full sensor analysis and found the differences slight enough that I just use HCG all the time, with the Extended full well depth setting.Â
