Ableton Live 12

We’ll see on Friday, I guess

2 Likes

Installed, seems awesome! Notion is sweating now :joy:

Maybe Tomorrow I read on the Push thread…

1 Like

Last 2 years they’ve done the week before BF (aka last week). But historically the 3 years before that was the week of BF exactly, and always on a Thursday. Obviously no guarantees, but by that logic, it should be worth checking in tomorrow to see if they put the deal on.

1 Like

pls pls pls push 3 SA sale pls pls

Also controller. Maybe…:. :smiley:

I’m crossing my fingers for this myself. :crossed_fingers:t2:

Assuming “freeze and flatten” is the same thing as “bounce to audio” in MPC Software, I must say I am very disappointed in Ableton how slow it does this.

I have no idea why Ableton is so slow at bouncing. It literally takes 2+ hours to export stems from a project (M1 MAX).

Anyone have tips to make it faster?

1 Like

That sounds extreme. I have never encountered such large rendering times for stems neither in large track count renders nor in lengthy projects :scream:

2 Likes

I just bounced 67 tracks and it took exactly an hour. I went out, walked my dog and came back it was still going on. And I really use very few plugins and mostly stock plugins like Eaq-eight and utility.

It takes so long, because what it does - behind the scenes - it’s soloing each track and rendering the master. So heavy project with lots of tracks = basically playing it x (times the) number of tracks. It only makes sense if you’re using lots of return FX, with multiple tracks using them. Are you?

I’m experiencing this with projects with 40 tracks. It seems the main culprit is that it doesnt render multiple tracks at the same time. So gets bottlenecked.

Also frustrating not to have a numerical progrss indicator eg 66/40 tracks rendered.

And the killer that it doesn’t save any of the rendered tracks to disk until it finishes the whole task - so if something goes wrong at 30/40 you have to start all over again

2 Likes

I’ve actually never exported stems from Live, but it sounds to me like it’s one of those things that has been around in the code base for years without much in the way of backend or UX optimizations.

Might be a good candidate for a feature request on Centercode.

1 Like

i freeze and flatten each track then consolidate each track then just dig them out of the file structure in the project file. i’ve used the consolidate feature this way forever. it’s so easy to just right click “show in finder” and see where all the files are… then view by “date modified” and all the files will be shown… so, it’s quite easy to grab the stems and put them in Logic which is generally where I like to mix. edit: should add i rarely have a project that has more than 20 tracks including busses/returns

3 Likes

Actually a proper stems export was added not so long ago, i.e. around v10/11.

If you choose “All Individual Tracks” and “Include Return & Master Effects” it will in practice solo each track one after another & render the master. If your project is heavy, e.g. it uses almost 100% of the CPU, then rendering a single track lasts as long as playing it in real-time (or longer, if you choose higher bit depth and audio rate). So producing all stems for a CPU heavy 5 minute song of 50 tracks can be 250 minutes or more!

BTW, that is how it works in all DAWs, no way to get around it if you REALLY want your group, send & master FX applied to every individual track separately, not rendered collectively. Agreed, other DAWs present it more clearly:

Cubase: Export Audio Mixdown • Cubase Pro Help • Reader • Steinberg

Studio One: Export Stems from your Song

BF sales are up, everything 25% off. :partying_face:

8 Likes

Hmm… I was afraid it will come to this. Do I get P3 (controller), or not? Damn :frowning:

1 Like

I just snagged one. I sold some things last month specifically for this.

1 Like

Get one :wink: but don´t get Standalone. You can get an M4 mini for 600-700

So much more Power. For on the run one could get Move now.

3 Likes