doesn’t the bounce feature already work like that?
2 Likes
I think the Bounce options provided by Live are limited. For example, I would like to bounce things to a particular folder, bounce without losing the MIDI Track and Clips, bounce to a particular Track, etc.).
What’s been added is an improvement on what was there, but there wasn’t much there to begin with, IMO. Being able to customize bouncing options would be welcome.
3 Likes
I wonder if they’ll let us hook more deeply into the native UI (beyond context menus) in the future. If that happens, I have a certain linked clips design concept waiting in the wings…
4 Likes
Are you already using CMD+B / CTRL+B?
Not to say I wouldn’t like more options. I really like the bounce options in Luna (but not much else from Luna).
I think they need more ways to export designed samples out of Live, because it’s still tedious.
2 Likes
This talented, generous fella has already written a handful of useful extensions and made them all available on his GitHub. (Just a reminder that these only work in the beta.)
6 Likes
Could this allow for proper transient detection to fix Live’s dumb broken system?
Seems like this just executes Bounce to New Track? Perhaps I am missing something.
I was only asking because it seemed you might still be using the bounce per track option in the right-click/contextual menu.
*and seriously asking, not assuming or judging, because I know you know your stuff.
If not, it’s great for bouncing sections of a track instead of the whole track while retaining existing MIDI and respective clips. It does deactivate the source selection, but easily reactivated.
1 Like
No offense taken or detected!
I admit that my bouncing needs are perhaps a bit specific/particular, but isn’t that what extensions are all about? 
I honestly have not used the Bounce feature a lot since it was introduced because of the limitations (in my mind) that I have described, but maybe I can try and work around it. The implementation just makes a lot of assumptions about what the end user is looking for and/or trying to accomplish.
1 Like
Is there a DAW that gets this the right way for you? - asking so I can check it out. Again for me, Luna added some nice features.
With the extensions SDK, the next step is to create an official MCP server.
Then rename the daw to Ableton Vibe.
6 Likes
Regarding the bouncing question discussion and potential SDK use-cases, I’m pretty sure this isn’t possible but my most pressing use case and, something I struggle with a lot because it’s very annoying to setup, is breaking out rhythm VSTi’s (Fors Opal, Battalion, Triaz) onto seperate tracks for better seperation/FX/control and then rendering those tracks as audio. I do this a lot when sessions get heavy and the only way I’ve found that works is creating an empty parallel audio track that’s setup to record the output of the rhythm track. I do this 6-10 times for the rhythm VSTi, setup all of the routing information, set input to lisening, arm the track and then playback and record the output of all of those tracks in realtime. There’s no faster way to capture.
The first use-case I tried to work through with Claude was setting up an extension that could automate this setup process for me so at least setup could be quick. Unfortunately, at the moment the current API (v1.0.0 beta) doesn’t expose audio input routing or monitoring mode. The TrackMixer object only gives you volume, panning, and sends. There’s no property for “Audio From: Ext. In → 1/2”, “Audio From: 3/4”, etc., and no monitoring state toggle (In / Auto / Off).
If they add those in future revisions, it’ll be the thing I instantly build. I’d love a native way of just rendering this audio offline (for both these rhythm tracks and also things I use sequencers on different tracks to then play on parallel vsti tracks which then later need to be captured. That just doesn’t seem to exist yet.
What I have started building this morning is an extension that connects to the BBC sound library. It’s an easy build and I love the weird collection of sounds they’ve got up there. I’ll put it up when I’m done with the getting it tested.
I love that all of these things are opening up. In another life I might have learned how to code, but my 52 year old brain just doesn’t have it in me. However, I have a ton of fun use-case things I’d love to build out and now I’ve got a buddy who’s happy to help.
6 Likes
100%. They should also turn the browser panel into a chat window and rename the Groove Pool to ‘Vibe Zone’.
3 Likes
This is up and running now. So far it works very well on my machine.
If anyone’s interested in checking it out, it’s available here:
Release v0.1.0 — Initial Release · ancientplaces/bbc-sound-effects-ableton · GitHub
This is my first time ever pushing something out, so if you have issues please feel free to DM me about them.
The extension can be invoked within an audio track (arrange or clip view) or from a Midi track with an instance of Simpler already on it.
The extension displays a BBC archive browser view where you can preview audio samples before choosing to add them. The BBC archive has a lot of interesting environmental sounds. It’s a fun addition to Live.
I hope someone finds it useful.
7 Likes
I wonder if an extension could be written to give more control over MIDI routing? 
I would love to be able to assign specific devices and channels to a track instead of:
- All devices, all channels.
- All devices, one channel.
- One device, all channels.
- One device, one channel.
I want to be able to set ‘these several devices and specific per-device channels’ without needing to create additinal MIDI tracks and sending the MIDI to my target track.
4 Likes
Oh, I would also love to see the crossfader outputs as a selectable audio source for audio tracks.
Instead of audio just going to the Master track, you could select ‘Crossfader A’ and ‘Crossfader B’ as audio sources in an audio track. Personalization option to ‘Disable crossfader output to Master track’.
This would open up a lot of possibilities.
2 Likes
I’ll take anything that automates and simplifies megabreak of doom
I had to downgrade on my main Mac because 12.4 doesn’t work well with Push 2, anybody else have issues?
Also I noticed last night on my mac mini that did get the latest version of 12.4 that the cpu meter spikes like crazy now. Never goes over 35ish% but we are talking one instance of simpler playing a kick drum sample, no plugins at all. on 12.3 using the same project it stays around 7% on the cpu meter.
This is the first example of this new functionality that has made me want to install the new version ASAP… what a nice idea, great work! Thanks 
3 Likes