@@MarkPetrieMusic great question! Every individual stack (the bracketed ones) has a room verb (Berlin studio) and a tail verb (cinematic rooms) inside of it. Those are routed to the track stacks with the rest of the instruments. You could also send the FX to their own aux that lives on that bracketed layer, if you’re trying to keep wet things separate! So those tracks can still live in those stacks, but their outputs can be a different place entirely! Either way works great depending on your needs. Those then naturally get fed into the larger stem groupings as well.
Hey Blair, Great video. Lots of really good ideas here. Tons of benefits of your method vs what I’ve been doing, but what I’m not understanding is the primary reason for the Aux tracks (with the _underscore naming). I mean if you just export your [Bracketed] stacks, doing so will still give you both your groups as well as your individual track-stems. The only thing I can think of is if you have a massive session, using Aux tracks provides you the benefit of not having to name 100+ stems after the fact. So are the Aux tracks purely an administrative focus? maybe just for nomenclature and file management? Or is there something in the processing of the audio file that I’m missing?
@@MarlonGibbons good question! The aux tracks do not export anything that hasn’t been exported. Rather, they create sub groupings of exports. Think of it as exports of stem layers. The first layer of exports is the bracketed group - that’s every folder. It’s awesome for mixing, but too many stems to send to a film production or a license music house, so I send that to auxes in a specific order. Now those stems are bussed down to fewer tracks in a high/low config, level 2. This is generally perfect for most music libraries, but not for some films, so I do one more round of bussing, level 3. These are very broad groups. So basically what you have is a session that bounces 3 different styles of stems plus all individual tracks if needed. If you just do brackets, then you will have to bring those into another logic or pro tools session to combine them in order to bounce them down to smaller groups - because some productions will not need v1, v2, va, cello, and bass stems! lol - it’s too in depth.
Really awesome video Blair!! I’ve never thought of making stems like this so I’ll definitely give it a shot 😁
It’s SO much better! Haha. I hope you enjoy it!
This is the way. Been setting up my logic template like this and it works great
@@w1wang it honestly is so much better than any other option I’ve heard of!
Great video. How do you apply FX like reverb to each section with this template, to ensure they get printed?
@@MarkPetrieMusic great question! Every individual stack (the bracketed ones) has a room verb (Berlin studio) and a tail verb (cinematic rooms) inside of it. Those are routed to the track stacks with the rest of the instruments. You could also send the FX to their own aux that lives on that bracketed layer, if you’re trying to keep wet things separate! So those tracks can still live in those stacks, but their outputs can be a different place entirely! Either way works great depending on your needs.
Those then naturally get fed into the larger stem groupings as well.
Hey Blair, Great video. Lots of really good ideas here. Tons of benefits of your method vs what I’ve been doing, but what I’m not understanding is the primary reason for the Aux tracks (with the _underscore naming). I mean if you just export your [Bracketed] stacks, doing so will still give you both your groups as well as your individual track-stems. The only thing I can think of is if you have a massive session, using Aux tracks provides you the benefit of not having to name 100+ stems after the fact. So are the Aux tracks purely an administrative focus? maybe just for nomenclature and file management? Or is there something in the processing of the audio file that I’m missing?
@@MarlonGibbons good question! The aux tracks do not export anything that hasn’t been exported. Rather, they create sub groupings of exports. Think of it as exports of stem layers. The first layer of exports is the bracketed group - that’s every folder. It’s awesome for mixing, but too many stems to send to a film production or a license music house, so I send that to auxes in a specific order. Now those stems are bussed down to fewer tracks in a high/low config, level 2. This is generally perfect for most music libraries, but not for some films, so I do one more round of bussing, level 3. These are very broad groups.
So basically what you have is a session that bounces 3 different styles of stems plus all individual tracks if needed. If you just do brackets, then you will have to bring those into another logic or pro tools session to combine them in order to bounce them down to smaller groups - because some productions will not need v1, v2, va, cello, and bass stems! lol - it’s too in depth.
@ ahhh! Ok now I got it. Thanks. Great tip/video.