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 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.
Â
@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.
@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.
Â
Â
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.Â
@wvreeven Yep, processing the "panels" separately worked well...now to expand the mosaic!
