UPDATE FROM MABULA
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.
I have twice had APP fail to complete its integration workflow, and instead repeatedly give me the message 'MEMORY TO FILE MAPPER: still trying to remove mapped file'.Â
On the most recent occasion, with 1590 lights, reduced to 1210 because some didn't Register, about 80megapixels. There should have been no filespace problem: APP said that it required about 1.6Tb to integrate, using a drive with over 3Tb available.
Any advice would be welcome.
Hi Stephen @lilacwatcher,
Thank you very much for posting your issue.
APP should not have this issue on a regular internal diskdrive. Is the drive internal and always mounted?
If it is an external drive, then I suspect your issue can occur if the Operating System or other software on your computer tries to unmount the drive for some reason, then APP can no longer remove the temporary file I think causing the warning message.
Can you tell me what kind of harddisk that you are using and if it is a permanently mounted drive or perhaps and external drive that you connect on occasion?
I have opened an issue on our list to investigate this further and fix this issue.
Mabula
Â
Merci beaucoup d'avoir repondu si rapidement.
My SSD has been connected to my Windows 11 laptop through a Thunderbolt docking station. Prompted by your suggestion that the problem lay with the connection to my drive, I instead connected the SSD directly to my laptop, i.e. not through the Thunderbolt. This time, the processing proceeded smoothly, with no problems: 1590 lights were successfully stacked, and I am very pleased with the result.
Thank you for taking time to help me with this issue.
Â
Hi Stephen @lilacwatcher,
That is really great, thank you very much for the feedback ! I am happy to read that all is okay now.
If an external drive disconnects unexpectedly, the integration will break down/can't finish and APP can not remove that temporary file. I have added an extra warning now in the console panel that states: MEMORY TO FILE MAPPER: !!! maybe the harddisk was disconnected or unmounted unexpectedly?
That will hopefully indicate to other APP users what happened and what caused the issue.
Mabula
