Bitwig

Trancit · Post by **Trancit** » Fri Dec 14, 2018 12:36 pm

That´s a bummer for me tbh...
Sure it´s nice to be able easily reactivate the track on the fly... but this means, if you run out of RAM there is no other way than deleting plugins...

In Studio One and Reaper deactivating/setting offline frees up the RAM as well...

Is this intended to be in Bitwig? Anyone knows??

Butwug · Post by **Butwug** » Sun Dec 16, 2018 12:18 am

It does for me. I make drum kits from raw 909 samples and process them all at once. I bounce to another drum rack and disable and hide the original kit with all the compressors, filters, etc.. Once it’s disabled cpu usage drops.

*edit* just realized you said ram, not cpu.

newtobitwig · Post by **newtobitwig** » Sun Dec 16, 2018 9:34 am

Maybe that's a thing to consider for the Devs.Hit them up on their email about this.

It might get even worse for someone using big kontakt libraries.A solution might be to bounce the audio first before adding any effects.Once the audio is bounced,deleting the instrument and then adding FX to the audio will free up much RAM and CPU.

Trancit · Post by **Trancit** » Sun Dec 16, 2018 9:53 am

newtobitwig wrote: ↑Sun Dec 16, 2018 9:34 am It might get even worse for someone using big kontakt libraries....

Avenger takes up to 900MB for every single instance... 10 instances of Avenger take up easily up to 9 gigs of RAM...
Then comes Omnisphere, Eazy/Superior Drummer, as mentinoned Kontakt...

Many many instruments eating RAM for breakfast... I would like to see some easy way of unloading instruments from RAM after bouncing without having to delete them...

These are all the little things, where traditionel DAWs shine and DAWs like Bitwig, Ableton, FL Studio fail... sadly...

Hanz Meyzer · Post by **Hanz Meyzer** » Sun Dec 16, 2018 4:56 pm

Avenger is poorly optimized. No plugin should take 900MB of RAM. But I get your suggestion, kind of "parking" functionality, where only the settings and names are kept, offloading from ram/cpu/PDC. I miss such thing, too, even for single plugins.

pdxindy · Post by **pdxindy** » Sun Dec 16, 2018 5:17 pm

Trancit wrote: ↑Sun Dec 16, 2018 9:53 am These are all the little things, where traditionel DAWs shine and DAWs like Bitwig, Ableton, FL Studio fail... sadly...

Bitwig and Live are both designed to dynamically enable/disable on the fly. But there still should be some way to do what you are asking.

Trancit · Post by **Trancit** » Sun Dec 16, 2018 5:32 pm

pdxindy wrote: ↑Sun Dec 16, 2018 5:17 pm Bitwig and Live are both designed to dynamically enable/disable on the fly...

I get what you mean, but for my understanding, deactivated tracks is not part of that or at least should not be...

For quick enable "parked" plugins, there are i.e. mute functions or instrument/fx selector...

Deactivating for me means: I have a track I don´t want to delete for being able to recall earlier state of work respectively as a backup, but up to then it shall not bother me at all... no CPU, no RAM as if it wasn´t there...

ckam03 · Post by **ckam03** » Sun Dec 16, 2018 6:51 pm

Holy crap, you're right. There's only 17 tracks in this project right now and I'm using 12 gigs of RAM. All Omni and a few Kontakt.

ckam03 · Post by **ckam03** » Sun Dec 16, 2018 7:21 pm

Deactivating the tracks seems to work for me? I deactivated 5 tracks and it dropped 3 gigs of RAM.

Trancit · Post by **Trancit** » Sun Dec 16, 2018 10:27 pm

For me it does not...

Having loaded for a simple test 4 tracks with each an instance of Avenger ...: 2,7 gig of ram
I disabled 3 of the tracks...: 2,7 gig of ram

Did the same in Studio One: Ram usage dropped from 2.4 gig to 800MB...

Perhaps you´ve got automatic purge in Kontakt activated and the disabling of the Kontakt instances forced the plugin to unload all the samples...
Try with Omnisphere only...

Butwug · Post by **Butwug** » Mon Dec 17, 2018 5:45 am

Trancit wrote: ↑Sun Dec 16, 2018 9:53 am
newtobitwig wrote: ↑Sun Dec 16, 2018 9:34 am It might get even worse for someone using big kontakt libraries....
Avenger takes up to 900MB for every single instance... 10 instances of Avenger take up easily up to 9 gigs of RAM...
Then comes Omnisphere, Eazy/Superior Drummer, as mentinoned Kontakt...

Holy

. Why does it take up so much? I can have quite a few instances of Zebra2 open it doesnt take that much up at all. Is this due to these synths working off of samples and Zebra2 synthesizing from scratch? I messed with ANA2 and Pigment demos and noticed they took up a ton of space as well; Zebra2 is tiny. Thought it was cuz it’s an old vst but Hive was also good on resources.

Trancit · Post by **Trancit** » Mon Dec 17, 2018 8:47 am

As are Sylenth1, Spire and many many others... but some take up really a lot of space...

pboy · Post by **pboy** » Mon Dec 17, 2018 12:42 pm

If using the KOntakt sampler, you can temporarily drop the samples from inside the plug-in's UGI. And reconnect Kontakt with used samples later, if needed. This has saved me quite a few times.

Trancit · Post by **Trancit** » Mon Dec 17, 2018 2:16 pm

pboy wrote: ↑Mon Dec 17, 2018 12:42 pm If using the KOntakt sampler, you can temporarily drop the samples from inside the plug-in's UGI. And reconnect Kontakt with used samples later, if needed. This has saved me quite a few times.

My main problem is more Avenger as I use it a lot and as said ~900MB every instance...

JHernandez · Post by **JHernandez** » Mon Dec 17, 2018 3:44 pm

I just tried with Omnisphere and you're right. The thing is, how would they go about unloading the ram, in other words the samples in the case of Omnisphere, without it taking all the time to load them back up? I'm no expert, but from where I'm sitting that sounds like a magical task. If it isn't, again, I'm no expert.

Bitwig

KVR Audio

Deactivating tracks doesn´t unload from RAM????