APP 2.0 cant set me...
 
Share:
Notifications
Clear all

Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.

It did take a long time to have the work finished on this and it  will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...

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.

 

APP 2.0 cant set memory limit

5 Posts
2 Users
4 Reactions
2,380 Views
(@curtis2010)
Brown Dwarf
Joined: 5 years ago
Posts: 4
Topic starter  

I recently installed APP 2.0 and I am unable to set the memory limit. When I click the CFG button no options show to set memory limit.  I have rebooted the system and still get the same behavior. I have checked for hidden windows and there are none. 

Screen shot attached.

Clipboard01

 



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

@curtis2010 This is new in the APP 2.0.0 beta versions. APP sets the memory it uses to the available system memory minus 4 Gb. No need to set the memory limit anymore. If you run out of memory then you need to process in batches of smaller numbers of lights. Or make sure your computer has more memory but that's far more expensive of course.



   
Curtis2010 reacted
ReplyQuote
(@curtis2010)
Brown Dwarf
Joined: 5 years ago
Posts: 4
Topic starter  

@wvreeven Yes, I was processing a mosaic when APP ran out of memory. Instead I processed each frame separately.

In the process of building a new machine with 64GB of DDRM5 RAM...with room to expand to 128GB.

 

 


This post was modified 3 years ago by Curtis2010

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

Instead I processed each frame separately.

In the context of mosaics I think the term "panel" generally is used and "frame" refers to a single light or sub. I could be wrong of course 🙂

Yes, processing the panels separately and then combining them is a great way of avoiding memory issues and speeding up processing. 



   
Curtis2010 reacted
ReplyQuote
(@curtis2010)
Brown Dwarf
Joined: 5 years ago
Posts: 4
Topic starter  

@wvreeven Yep, processing the "panels" separately worked well...now to expand the mosaic!



   
ReplyQuote
Share: