Large projects can use a lot of cpu. All devices use cpu.
When editing a channel of audio, it is a good idea to save cpu power by disabling effects.
It is a better idea to disable effects until you're ready to start rendering.
By now you have already tested how they will sound once enabled, but enabling them will cost you cpu, and you don't want to hear glitches while editing something else.
Some people have the luxury of using as many devices as they want, but at the cost of overheating their most likely liquid cooled cpu.
But most people aren't that fortunate, and obviously have resorted to use a free daw.
But to what extent is an effect disabled? Is it just an image on the desktop or is it using at least some cpu?
I don't think you can disable other devices in the same way as effects, but what if you could?
And obviously synths use more cpu than anything, even when they're not in use.
Maybe a feature can be added to completely disable a devices logic by right clicking on any device, to save cpu.
This is the best online daw that exists, and I'm sure it will soon be the best professionally.
Comments (2)
I thought about this as well. Once you make what you need and you're ready to move on ( add another Heisenberg for example ) you can somewhat disable the previous one, have it somehow gone but still playable.
I also agree with this, to save CPU load. I've found that disabling unneeded timeline tracks helps a lot to make heavy drafts easier to play without glitches. This was definitely the case in Flash and I think in Next too.