I was always under the impression that deactivating a track deactivate all devices in that track and in turn save's cpu power. I have been noticing lately while working with Diva (CPU intensive patches), that this does not seem to be the case.
While it does reduce the cpu load a little, it seems that its still doing most of the work in the background and the CPU is only truly relieved by deactivating the device itself(within the chain).
I was wondering if this is just how live was designed, or is this a bug?
Cheers,
Dan
Deactivated tracks still use CPU
Re: Deactivated tracks still use CPU
Track Activator just mute tracks.
You can see the Track's meters keep showing activity (though grayed instead of green) even with the Track deactivated.
Even with playback stopped, if you have a MIDI Track deactivated but still armed, you can play MIDI notes, you will see it still plays the instrument.
You can see the Track's meters keep showing activity (though grayed instead of green) even with the Track deactivated.
Even with playback stopped, if you have a MIDI Track deactivated but still armed, you can play MIDI notes, you will see it still plays the instrument.
♥♥♥
Re: Deactivated tracks still use CPU
Hmm... Is that for sure? It seems somewhat counter productive if so.
Obviously having a mute button is a necessity, but why call it "disable track" if its actually just muting it. If this is the case there really should be a true "disable track" feature implemented. They don't serve the same purpose..
Obviously having a mute button is a necessity, but why call it "disable track" if its actually just muting it. If this is the case there really should be a true "disable track" feature implemented. They don't serve the same purpose..