Layers Switch CPU Save
Im just curious if there are any limitations to the CPU Save. Like any modules it doesn’t work on or maybe Samples or something.
Im just curious if there are any limitations to the CPU Save. Like any modules it doesn’t work on or maybe Samples or something.
Comments
I haven't come across any yet and I've been using it almost exclusively with third party auv3's.
Push it as much as you can and if it goes over the edge don't say I didn't warn ya,....;)
Nah... just holla and we'll fix it. :)
When I start envisioning the possibilities I end up thinking “No way.. no way it can it all that…”
Try it and you will find out 😉
A reverb or delay effect will initially remain silent when you switch to it if CPU save is active.
Whether or not this is desired behavior is completely up to you.
Holy crap dude I just ran a test with 30 Layers each with 10 oscillators and the cpu was like “is that all you got?”
Yep. Drambo is very efficient, @giku cares a lot about performance!
Staggeringly awesome. Like on parr with the addition of Automation.
Does Fade in add to the amount of processing going on the same way Fade Out would?
The name Layers Switch is really inconspicuous for such a powerful device.
@Johnisfaster In my experience you can see the cpu rise a little during fades, which makes sense since both layers are playing simultaneously during the fade
I could see CPU rise with a long Fade Out but I didn’t see that with long Fade In which is what made me curious. Fade Out extends overlap between Layers but does Fade In also extend overlap or just fade during what was already gonna be overlap. Does that make sense?