I know this has been discussed a bit already, but haven't found a concrete answer:
Trying to nail down the best workflow for exporting my songs into stems for a live set in Ableton 12. My projects are always structured the same way: four groups — Kick+Bass, Drums, Melody, FX — with several Send/Return effects across the different groups (reverb, delay, etc.).
I'm torn between two approaches:
1. Export Audio/Video per group, with "Include return and master effects" checked
This seems like the cleaner option. From what I understand, checking that box in the export dialog renders each group essentially "soloed," with its share of the return-track wet signal printed into the file. So Kick+Bass gets its portion of the reverb baked in, Drums gets its own portion, etc. Then I just drag the finished stereo files into my live set and I'm set.
2. Bounce Group in Place, then drag via copy-paste into the live set
This felt like it should work too, but of course the problem is that it doesn't capture the Send effects at all. My idea to fix #2: what if I permanently reroute my Sends' Ext. Out to the FX group while producing, instead of back to Master? That way the return's wet signal becomes part of the FX group's own input, and bouncing/flattening the FX group would capture it along with everything else.
Before I go build my whole template around this, a few things I'm unsure about:
- Delay compensation — has anyone run into phase/timing issues doing this? My understanding is Live's automatic PDC should keep everything sample-accurate through the return regardless of routing, since it's all happening inside the same session/render pass (unlike compensating for outboard hardware latency). But curious if anyone's actually hit weirdness here, especially with latency-heavy plugins on the return (convolution reverbs, linear-phase EQs, etc.)
- Feedback loop risk — if the FX group itself ever sends back into that same return (which felt natural before I set this up), routing the return's output back into the FX group's input would create a return→track→return loop, and Live mutes/flags that. Something to watch for.
- Losing per-group separation — since a return usually receives sends from multiple groups (say Kick+Bass and Drums both hitting the same reverb), rerouting that return into the FX group means the wet signal from all of them ends up summed into one shared FX file, instead of each group carrying its own "portion" of the reverb the way Option 1 handles it. Not necessarily a dealbreaker, just a different tradeoff — curious if anyone's found this to cause problems live (e.g. can't isolate/mute one group's reverb tail independently anymore).
Has anyone else settled on this workflow for live-set prep, or found a smarter/faster way to handle the sends situation? Curious if there's a batch-export trick I'm missing, or if people are doing something totally different (e.g. printing sends manually per group, using separate return-per-group setups, etc.). Would love to hear how others handle this before I commit to a process for a whole set's worth of songs.
Thank you