MAY 4 2026: APP 2.0.0-beta44 has been released !
New improved internal memory controls should now work on all computers
May 1 2026: APP 2.0.0-beta43 has been released !
Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
Apr 29 2026 APP 2.0.0-beta42 has been released !
New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...
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.
Hi everyone,
I searched the forum, but could not find an answer to this. Is there a description of the filename naming convention that APP uses to determine what kind of image is loaded? It seems the import is quite good in guessing what Image (Channel, Session, Filter, etc.) is used by the filename. But I could not find a documentation of that. It would really help to speed up things if I just name all files from a imaging session appropriate to this naming convention and load everything in one step and let APP decide what image is what.Â
Or even better if APP could be started with a reference to a config file that defines list of image files for darks, flats, bias, lights, etc. and if possible also the parameters for the processing. This could be also a different config file so you can have presets of different processing parameters.Â
With best regards,
Mario.
APP looks at the headers of the files, for fits files at least. And if they use the regular fits header format it will assign the data properly. Not all manufacturers provide enough information, which is why you sometimes have to click "force CFA" if APP loads the image assuming it's color while the data should be mono.
The config presets, APP will get a "watch this folder" feature, mainly developed for iTelescope, but I guess it'll also be in the regular release. That would allow you to put your data in there and APP processes the data automatically when new data arrives. And maybe something like you suggest can be part of that.
