lookatthisguy wrote:Sounds like you want to be printing stems. There are probably other methods as well, but the surest method I know of is to route the outputs of everything you want on a stem to a bus, make that bus the input of a new audio track, and then record to it. From there you just need to export the stems, and you have the added benefit of being able to proof them during recording or on playback before printing.
fuzzfilth wrote:It's not convoluted if you work from a template that has all the routing set up already. Being able to proofhear is really beneficial, you'd have to check and double check anyway before you deliver silence in a mission critical situation which will cost you likely this and certainly the following job.
That being said, if you're working towards stems, you will quite possibly have Summing Track Stacks of these stems already. Open the Track Stacks, so their tracks appear empty, then command-select these empty tracks, then File>Export>7 Tracks As Audiofiles and there you go.
fuzzfilth wrote:That being said, if you're working towards stems, you will quite possibly have Summing Track Stacks of these stems already. Open the Track Stacks, so their tracks appear empty, then command-select these empty tracks, then File>Export>7 Tracks As Audiofiles and there you go.
JonnyStrinati wrote:there really should be a more straightforward way.
fuzzfilth wrote:JonnyStrinati wrote:there really should be a more straightforward way.
If clicking on the stems and hitting Export isn't straightforward enough, then I don't know what is.
fuzzfilth wrote:No. You're trying to export Tracks, not Regions, so you need to select the Tracks you want to export.
fuzzfilth wrote:In any case, *exporting Tracks* as opposed to "Bounce Project" will give you each track like it is, at the output of that very track (you can specify if that track's fader and plugins should be included or not). You will not get any processing downstream (Sends to other FX, Bus processing, Master processing). This has been discussed many times on this board.
Again, if your workflow regularly involves stems (like writing for film, or for music libraries) you will set up your project template accordingly so you can benefit from track stacks or busses to actual recording tracks like discussed above, and you will make clever decisions which FX returns will get included where.
If you want to send your stuff to a mixer to get it mixed properly, then you will not want any of your presumably lesser quality (in terms of sound and choice) FX on there anyway unless it's your signature guitar sound or whatever.
If it's a one-off where MOMA wants your track split up as is so they can play the maracas from the balcony, then you will patiently Bounce each track or group of tracks in solo while basking in the glow of eternal fame.
fuzzfilth wrote:We're going in circles here. You asked how to export stems, now you have two valid and straightforward ways to do it. Then you ask about exporting single elements with all their processing, and this being a rare case requires special attention.
fuzzfilth wrote:Stems never include any downstream processing, individual-elements-with-all-their-processing however, do, so there's the fundamental difference. If you don't believe me, ask anyone else working with stems.
fuzzfilth wrote:One last thing before I give up, though I've tried to convey it already:
If you regularly create stems, you set up your mix so that each stem gets its own set of plugins and sends, the returns of which will also be routed into this very stem, and can be printed (or not) into that very stem. You avoid adding FX downstream as they will not be part of any particular stem.
Over and out, the ground is yours.