Share:
Notifications
Clear all

2026-10-09 APP 2.0.0-beta48 has been released !

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.

[Solved] MEMORY TO FILE MAPPER: still trying to remove mapped file

4 Posts
2 Users
0 Reactions
1,403 Views
(@lilacwatcher)
Brown Dwarf
Joined: 2 years ago
Posts: 3
Topic starter  

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.



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 10 years ago
Posts: 5468
 

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

 



   
ReplyQuote
(@lilacwatcher)
Brown Dwarf
Joined: 2 years ago
Posts: 3
Topic starter  

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.

 



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 10 years ago
Posts: 5468
 

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



   
ReplyQuote
Share: