Saving MIDI track before bouncing to audio
Saving MIDI track before bouncing to audio
What's the best way if there is any to save progress that you made from a MIDI track before bouncing it to audio?
-
- Posts: 3761
- Joined: Wed Oct 26, 2011 3:36 pm
- Location: Northwest Nowhere
Re: Saving MIDI track before bouncing to audio
make a folder then drag the midi clip to that folder out through the Live browser
-
- Posts: 105
- Joined: Thu May 17, 2012 9:36 am
- Contact:
Re: Saving MIDI track before bouncing to audio
I just right click and deactivate midi clips, So I can activate them later if I need to.
-
- Posts: 261
- Joined: Thu Mar 04, 2010 10:18 pm
- Location: Warsaw, PL
- Contact:
Re: Saving MIDI track before bouncing to audio
written somewhere else that idea: if You use the vsts (i.e. it's not a external instrument case).
If You want to have both: the midi track, and its render:
freeze the track, flatten, drag 'n' drop the rendered audio outside the Live. Double undo (ctrl/cmd-Z). Import the audio file from the current location (usually the first spot is the desktop) to a new audio track.
If You want to have both: the midi track, and its render:
freeze the track, flatten, drag 'n' drop the rendered audio outside the Live. Double undo (ctrl/cmd-Z). Import the audio file from the current location (usually the first spot is the desktop) to a new audio track.
MBP/ M-Audio FW 410/ OSX 8/AL 9 Suite/ UC33e + Drehbank
Re: Saving MIDI track before bouncing to audio
I find both of these easier than dragging stuff in and out but depends on what you're used to I guess:
Duplicate the track (ctrl or cmd-D), render one of the tracks, mute the other (keep all the muted MIDI tracks in a group out of the way if you find it getting too complicated).
If I'm doing this to several tracks (e.g. rendering a bunch of cpu intensive VSTs to create a performance version) I'll just do a save as and make a second version of the original, then do the renders. If you do this all the individual MIDI tracks will always be recoverable via the broswer in either version.
Duplicate the track (ctrl or cmd-D), render one of the tracks, mute the other (keep all the muted MIDI tracks in a group out of the way if you find it getting too complicated).
If I'm doing this to several tracks (e.g. rendering a bunch of cpu intensive VSTs to create a performance version) I'll just do a save as and make a second version of the original, then do the renders. If you do this all the individual MIDI tracks will always be recoverable via the broswer in either version.