Ok great thank you for testing. I expect memory usage to be higher than other synths considering all that’s going on with it,especially if I have 8 multi samplers or granular samplers loaded but I’m getting excessive memory use from the single saw init patch.Have you tried to pay with the settings of how your plugin is loaded in Bitwig? Can change a lot memory usage.
I'll try it later and tell you if I have the same problem. I have 16gb and never noticed anything despite having 8-10 instances.
I am not under sequoia yet though...
I have. I usually have it set in the middle “by vendor “. Switching to “together improved it slightly. The” host with Bitwig” setting is better still which is to be expected but still too much. Its possible that Avenger 2 just uses to much RAM for my computer though I don’t remember having this problem before but most of my use was of Avenger 1 in Fl Studio. I’m pretty amazed at what I can do with the m1 and only 8 gigs but it might be time to upgrade.
Hello again...
So I did check and...
You are definitely into something. I have 16gb. My memory usage is 9.3GB in the song without Avenger 2. When I load avenger 2 in the song. It becomes 12.8 (3.5gb additional!) for 6 instances.
The 6 instances are heavy but indeed the memory consumption seems to be quite high...
The memory consumption is NOT evolving though, so it doesn't seems to be a data leak....
Starting a project from scratch. I added a simple melody as only track.
8.38gb as memory usage with Bitwig only.
8.50gb with polysynth playing the melody (Bitwig synth).
8.79gb with spire.
9.18gb with Falcon 2 (first preset of the preset tour default bank pack)
Back to Bitwig only: 8.69gb.
11.13 with Avenger 2 (first bass preset of the factory sound bank).
Difficult to interpret these results as there are many many factors (it can be only smart memory reservation) but it seems indeed Avenger is very heavy on memory...
I will report the problem to the support (and so should you).
Statistics: Posted by ChanceB — Sat Oct 05, 2024 6:46 am