I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
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.
