This is mainly a bug fix release for the reported bugs in beta47. In addition it has a significant User Interface performance improvement noticable when you need to process 1000s of images in APP.
2026-10-03 APP 2.0.0-beta47 has been released !
This is a very big release... many code optimizations/rewrites, many parts of APP are much faster and more precise, especially star analysis and registration are much faster ! Big mosaics will go much faster 🙂
And we introduce a new preview filter, which includes the new Adaptive Deep Sky Stretch and a General Levels Stretch, this has been long over due. The old preview filter (the panel on the right side to stretch and preview your data) has not been updated for a couple of years and it is a critical part of any APP session.
Adaptive Deep Sky Stretch or ADSS is a much more intuitive stretch algorithm. It is also color preserving (which is a great new addition in itself ! ) which means that the highlights are no longer bleached, color is maintained from the linear data while stretching. You can simply stretch your data using the sky background level and signal width sliders which work much easier and more intuitive. You no longer need to fiddle with the old complicated sliders with zoom buttons. All the zoom buttons for the sliders are made redundant. And you can enter slider values in the slider value fields yourself. I will make a youtube video in the coming days to explain and fully introduce ADSS. Once the video is ready, it will be highlighted on the forum.
RGB Combine upgrade !. The RGB Combine Tool has been rewritten mostly. The tool is faster and easier to use and most importantly, the Luminance slider to inject a luminance channel or channels into the RGB composite is now working correctly. It no longer bleaches the RGB colors. Combined with the new ADSS preview, you will get much better and easier great composites with great color! I will also explain this in a new youtube video.
Windows "Encountered error in module FileDetailListUpdater"
How are you loading these frames? Are they on an external drive?
I have 2 other customers with the same issue and one of them has confirmed now that he is loading the data from an external drive and his raws on that drive are now corrupt... so his drive is failing.
Feel free to send me a raw so I can test to make sure.
Hello. Sorry for the late response. I am using M2 disk on pcie 3.0 x4 bus. Until now, there were no problems with reading or working on these files located on this disk. The previous version of the program is free of this error because I checked. After copying to the 3Tb internal disk, the program loads them correctly from this location. The M2 disk is error free and in excellent condition.I just uploaded the RAW files to the specified server.
EDIT : after copying the files to the internal 3 TB disk, the problem occurs at the moment, I do not understand why now it does not work since a few minutes ago I could. Disk status is excellent.
This post was modified 7 years ago 2 times by Grzegorz Nagy
Hello. Sorry for the late response. I am using M2 disk on pcie 3.0 x4 bus. Until now, there were no problems with reading or working on these files located on this disk. The previous version of the program is free of this error because I checked. After copying to the 3Tb internal disk, the program loads them correctly from this location. The M2 disk is error free and in excellent condition.I just uploaded the RAW files to the specified server.
EDIT : after copying the files to the internal 3 TB disk, the problem occurs at the moment, I do not understand why now it does not work since a few minutes ago I could. Disk status is excellent.
Hallo Mabula,
I have a problem with loading Olympus ORF raw files from an Olympus E-3 camera into APP on a Windows 10 PC. Error message below. (APP 1.077)
I tried it on a Linux Mint box with APP 1.077 where I had no problems.
PC: Windows 10, 32GB, Intel Dual Hexacore, Nvidia graphics card.
In APP 1.077, loading CR2 & NEF frames is using LibRaw. APP 1.076 and before were using my own raw conversion code. So there is a difference there.
LibRaw code was not able to handle filepaths with non-standard characters like umlaut or chinese characters... My own code was able to process that. I had to fix the filepaths so LibRaw can now understand them correctly, so in APP 1.078 it should all work again.
