Share:
Notifications
Clear all

June 24 2026 APP 2.0.0-beta46 has been released !

Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.

May 27 2026 APP 2.0.0-beta45 has been released !

Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.

Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options

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.

 

selecting RAM

5 Posts
3 Users
0 Reactions
1,773 Views
 J_DP
(@nateman_doo)
Red Giant
Joined: 4 years ago
Posts: 37
Topic starter  

The config button no longer has the ability to do anything.

APP cfg

No RAM, no CPU just the gong.  a stack crashed because it said there wasn't enough RAM allocated and I went to the config (2.0.0 Beta1) and no more config options.



   
ReplyQuote
(@turtlecat1000)
Red Giant
Joined: 5 years ago
Posts: 63
 

It’s in the release notes. Memory management is now dynamic.



   
ReplyQuote
 J_DP
(@nateman_doo)
Red Giant
Joined: 4 years ago
Posts: 37
Topic starter  

@turtlecat1000 That doesnt seem to be the case with me.  It said it ran out of ram at 28G, and specifically to allocate more ram (I have 32G)



   
ReplyQuote
(@turtlecat1000)
Red Giant
Joined: 5 years ago
Posts: 63
 

@nateman_doo It’s likely a bug with the message rather than the function. 



   
ReplyQuote
(@wvreeven)
Quasar
Joined: 8 years ago
Posts: 2134
 

@nateman_doo @turtlecat1000 This indeed is a bug with the message and Mabula already has fixed it for the upcoming next beta or APP 2.0.0.

In the mean time, how many files are you trying to process at once? Are they all the same type (e.g. RGB) or are you loading many files for different filters? Or do you perhaps try to create a mosaic with many subs? It looks like you may need to reduce the number of frames loaded at once and process your data in batches. If you answer my questions about the data then we can help you devise a good partitioning scheme.

 

Wouter



   
ReplyQuote
Share: