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.
Just downloaded APP and got it working. Well, sort of working. Trying to load any images or calibrate anything is massively CPU intensive. Watching Sara's videos, where loading an image happened quite quickly, was what confirmed to me that something is wrong here. I just loaded up a series of 60 subs, at 60sec each, of M101. The subs are 16bit TIFs (output from RawTherapee). Loading a single sub in the image viewer takes about three minutes (yes, minutes). All four CPU cores are maxed out as a I do so, and all 4 GB of memory I've allowed APP to use get used. When I try to do calibration, APP quickly tops out all four CPU cores and all 4 GB, gets to 5%, and then pretty much just sits there maxing out my CPUs. It makes very slow progress -- something like 1% per 2 minutes. I don't want to wait that long just for calibration. This is not a crappy machine; the CPU is a 3770, I think, it has 16 GB of total system memory, and a 560 graphics card.
I'm using Linux Mint 17.3. I suspect it may either be the TIF files output by RawTherapee, or the version of Java (or rather, Java substitute) that I'm running, but I'd love to hear other theories. Mostly, I'd like to know how to fix this.
Hi Rachel,
Thank you for your feedback, you are describing completely abnormal behaviour indeed.
Which APP version are you using?
The java version that you installed on Mint can't have any influence because APP is installed with it's own Java runtime and should use that runtime.
The most probably cause of the issues that you describe are the TIF files from Raw Therapee. So I would need to have a look at the TIFs. So if you can provide me with one or two, I'll try to fix this.
A question from me, regarding using files from raw therapee: is there a certain reason why you bring your camera frames to raw therapee before starting processing of your data? Raw Therapee isn't astronomical capture software or is it?
Kind regards,
Mabula
Â
I'm using RawTherapee because it's the only program I have that converts Olympus ORF raw files into an APP-readable format. (I didn't realize APP wouldn't support ORF until I'd already downloaded it; I figured using TIFs was a good workaround.) Maybe I should just wait until APP directly supports ORF.
Each TIF is 70+ MB in size, so I don't have an easy way to upload one of the files.
Hi Rachel,
I understand, that makes perfect sense. Yes, more raw support for more camera brands will come.
Is wetransfer not an option to send me one of those tiffs? I guess I can try Raw therapy myself and create a TIFF from an ORF file I think.
Â
Â
Â
Â
