Hello everyone! I've been noticing that Bitwig doesn't completely unload plugins from RAM when I deactivate them, meaning that the amount of freed memory isn't what the plugin actually consumes. This causes the RAM usage to slowly build up when I'm working on a project with virtual instruments and eventually reaching dangerous levels like 98% usage out of the (sadly not upgradeable) 16gbs my laptop has, which is just one step from to the system freaking out or even crashing.
To avoid this I have to terminate the audio engine so Bitwig unloads everything and then I reactivate it, that way it actually frees up my RAM.
Has anyone else experienced this?
I'm on (Arch) Linux running the .deb version of Bitwig 5.2.5.
Edit: After more testing I think that the culprit in this situation is Ugritone's drum sampler, when it loads all the samples to RAM the usage goes up to 80%, but luckily it has an option to not do that and that way it comes down to 60%.![:D]( "Very Happy")
To avoid this I have to terminate the audio engine so Bitwig unloads everything and then I reactivate it, that way it actually frees up my RAM.
Has anyone else experienced this?
I'm on (Arch) Linux running the .deb version of Bitwig 5.2.5.
Edit: After more testing I think that the culprit in this situation is Ugritone's drum sampler, when it loads all the samples to RAM the usage goes up to 80%, but luckily it has an option to not do that and that way it comes down to 60%.
Statistics: Posted by IRVNG — Mon Nov 11, 2024 10:43 am — Replies 0 — Views 11