Ableton Forum

In pro-tools there's a way to disable a track which mutes it and basically makes it completely inactive so it doesn't use any CPU. namely i'd want to use this on MIDI tracks so that I could bounce the midi and effects to an audio track to reduce CPU load and disable the MIDI track afterwards.

i don't want to freeze the track because i want to completely mess with the samples after i've bounced them, although I tried variations of this this weekend. the result was a slow tracking session, frustration and little headway.

i just want to turn a track off and yet have it there in case i need to return to the source. any suggestions?

Can't you just record the output of the MIDI track as an audio track, and then bypass the device on the MIDI track? You could also set the MIDI output to none.

Maybe I'm missing something, but couldn't you just not launch that track, or deactivate the clips in that track?

hambone1 wrote:Maybe I'm missing something, but couldn't you just not launch that track?

I think he wants to hear the sound, just not take the CPU hit.

Some synths might use CPU when "idling" perhaps?

Just turn the VST off with the yellow button in the top left corner.

fluid wrote:Can't you just record the output of the MIDI track as an audio track, and then bypass the device on the MIDI track? You could also set the MIDI output to none.

if i bounce to another track, i can hear the sound, so to speak. say for instance a given track is using an operator with some plugs and its using some crazy 35-40% of my CPU. i will route the audio to another track and record it and then i disable the devices on the track. it still seems to have some cpu effect. it would be handy if there was a way to just say "ignore this track, live". that way, if i want to change some of the midi notes, plugs or settings later, i just reactivate the track and re-bounce as needed.

the issue is that some synths and plugs use CPU whether you can hear it or not. maybe its having sends on the track or something. bypassing the device on the midi track still seems to use CPU resources as well.

i'll play around and see if i can figure out what's doing it. it seems logical to me that, if i disable ALL plugs and synths as michael described, it should solve my problem. i'm just pretty sure i tried that already. maybe not. i *am* a dunce, after all...

helixx wrote:

fluid wrote:Can't you just record the output of the MIDI track as an audio track, and then bypass the device on the MIDI track? You could also set the MIDI output to none.

if i bounce to another track, i can hear the sound, so to speak. say for instance a given track is using an operator with some plugs and its using some crazy 35-40% of my CPU. i will route the audio to another track and record it and then i disable the devices on the track. it still seems to have some cpu effect. it would be handy if there was a way to just say "ignore this track, live". that way, if i want to change some of the midi notes, plugs or settings later, i just reactivate the track and re-bounce as needed.

the issue is that some synths and plugs use CPU whether you can hear it or not. maybe its having sends on the track or something. bypassing the device on the midi track still seems to use CPU resources as well.

i'll play around and see if i can figure out what's doing it. it seems logical to me that, if i disable ALL plugs and synths as michael described, it should solve my problem. i'm just pretty sure i tried that already. maybe not. i *am* a dunce, after all...

Have you tried disabling the output of the MIDI track as well? How about deactivating the MIDI clips?

Not sure about any of these, just trying to give you some ideas....

i'll try all of these tonight. i appreciate the suggestions, folks!

An efficient, tidy way to do what I think you want to do is:

1.to bounce the parts (or render them) to audio, for use in your set (beware - using complex warp mode chews a lot of cpu - try beats/tones)

2.drag the original (midi) clip/s to the browser (making a Live Clip, which stores all your instrument settings and FX chains and can be easily dropped back into any set from the browser)

3.delete the original midi channel altogether (saves screen real estate on my laptop, clears the vst's and frees their cpu use)

hope that helps.

the live clips is the most sensible non-realtime workaround, but I have been requesting disable tracks feature for a while now for this reason

with live devices you can turn it all off at once by alt+clicking the on switch, but this doesnt help if you are using non live vstis + FX

I think particularly for a live app this is important

forge wrote:the live clips is the most sensible non-realtime workaround, but I have been requesting disable tracks feature for a while now for this reason

with live devices you can turn it all off at once by alt+clicking the on switch, but this doesnt help if you are using non live vstis + FX

I think particularly for a live app this is important

i did request this feature as well, hopefully the next upgrade will include it ,
there always the way of assigning the on switches to a single controler .
i think the midi translator that kid beyond uses can do that .

spiderprod wrote:

forge wrote:the live clips is the most sensible non-realtime workaround, but I have been requesting disable tracks feature for a while now for this reason

with live devices you can turn it all off at once by alt+clicking the on switch, but this doesnt help if you are using non live vstis + FX

I think particularly for a live app this is important

i did request this feature as well, hopefully the next upgrade will include it ,
there always the way of assigning the on switches to a single controler .
i think the midi translator that kid beyond uses can do that .

doesnt help the cpu issue though, which is the point

when you freeze a track it makes a new file, i can't remember where, not at my computer, but maybe you could use that, maybe i don't understand the issue though?

here's a workaround..

..i feel you on the disable track thing being a past PT user


"save as"

delete the track..

if you have live 5 and want to re-tweek the track you can import it right back in...

if you have pre 5 live you'll have to open the old set and ..........