Ableton 12 - Generative MIDI, Multiband Distortion and more

[Yorrrrrr]

Yes, it’s kinda ridiculous, I know. I need that beta to test Live 12’s performance in an old machine and make a decision for a new one. Live 11 is only OK, I expect 12 to be the same(ish), regardless of new features.

[gnu23]

Just want to share how i have my browser set up for anyone out there who is curious about how some people are using it. Ive scaled the pictures down as they took up a whole thread page if i didnt. Im using the collections still to organize my browser to not have a million categories.

Interesting, this is useful. For me the big problem is all the Kontakt instruments that I have. Do you see any way to list and categorize Kontakt instruments separately?

You can load a library in Kontakt and save it as a vst/au preset by dragging to the user library. giving it the library name and then tag accordingly. I go one step further by adding utility, eq and comp and create a group and save that as a rack.

I did not know that was possible Thank you!

[machinesworking]

Yes, it’s kinda ridiculous, I know. I need that beta to test Live 12’s performance in an old machine and make a decision for a new one. Live 11 is only OK, I expect 12 to be the same(ish), regardless of new features.

I think it’s pretty close to release, but even still no way of knowing if Ableton don’t have some phone home features that mess with your machine, and a cracked beta is not guaranteed to be the latest version so more likely to have weird beta tags in it. T this point O would only consider a crack for a deprecated plugin from a no longer existing company like Camel etc.

[Yorrrrrr]

Indeed. Patience then. I'm very excited about Live 12. I hope I can have it soon enough.

[thecontrolcentre]

I need that beta to test Live 12’s performance in an old machine and make a decision for a new one. Live 11 is only OK, I expect 12 to be the same(ish), regardless of new features.

It's running OK on my Windows 8.1 laptop (It's about 10 years old now) ... seems a little "smoother" than 11 if anything. Early days tho' ... the browser will take a bit of setting up.

Hang on in there for the beta ... there must be many applicants. It was a nice surprise when I got the beta invitation this afternoon. Any crack is likely to be less stable, and many packs will be missing from the suite version.

[nanostream]

Great to hear! How's it going performance and stability wise (specially compared to v. 11 or 10)?

About the same on a M1 Mac, I’d say. Which is good. But it’s still a beta, so who knows.

After spending more time with the beta, I’ve found it to be quite unstable in certain situations, i.e. it crashes a lot when loading or opening plugins. It’s a beta, after all.

[elxsound]

Great to hear! How's it going performance and stability wise (specially compared to v. 11 or 10)?

About the same on a M1 Mac, I’d say. Which is good. But it’s still a beta, so who knows.

After spending more time with the beta, I’ve found it to be quite unstable in certain situations, i.e. it crashes a lot when loading or opening plugins. It’s a beta, after all.

Which plugins are your experiencing crashes?

L12 has been rock solid for me.

Performance using plugins should really be the same or similar to L11.

You should see improvements using the browser and loading saved projects.

[rod_zero]

I have a question for those beta testing Live 12. Live 12 has a huge quantity of workflow improvement features, but I'm still missing a new mapping system : to me (and for my use) it would be a game changer to be able to choose between midi learning (like in Arturia and NI synths) and mapping in Live 12.
Mapping is exclusive (if you map your sustain pedal CC64, you can't use the pedal anymore as a sustain pedal) and goes through the chains and midi filters unaltered. It is very often a huge limitation, especially when using Live on stage in a way where you play "songs", with different instruments for each song and even different instrument between each section of a song.
Midi learning is like midi notes : exactly like a chain is filtering the midi notes, so I play a bass when chain 1 is active and a rhodes when chain 2 is active, I could assign CC11 to an Utility's gain in chain 1, to a macro in chain 2 or a filter in chain 3, and to nothing when the chain 4 is active. So I would be using the same knob (or fader) for controling different parameters, without excluding the use of CC11 for other tasks in the future.
The best exemple would be the sustain pedal : it could serves as a sustain pedal most of the time, but in some chains it could trigger a different function. With mapping, if you map your pedal, you can say hello to the sustain feature !
Some M4L devices are doing this, but I would be so happy to have this built-in in Live...
Am I the only one to consider this as a workflow improvement ?
I did propose the feature in the Beta Center Code, but it seems I'm quite alone in seeing any usefulness to this...

Ableton has scripts for controllers to and using macros you can do what you want.

[SLiC]

High Contrast mode looks great on a small laptop screen to my old eyes, love the GUI now, everything seems to be in the right places.

[Calagan]

I have a question for those beta testing Live 12. Live 12 has a huge quantity of workflow improvement features, but I'm still missing a new mapping system : to me (and for my use) it would be a game changer to be able to choose between midi learning (like in Arturia and NI synths) and mapping in Live 12.
Mapping is exclusive (if you map your sustain pedal CC64, you can't use the pedal anymore as a sustain pedal) and goes through the chains and midi filters unaltered. It is very often a huge limitation, especially when using Live on stage in a way where you play "songs", with different instruments for each song and even different instrument between each section of a song.
Midi learning is like midi notes : exactly like a chain is filtering the midi notes, so I play a bass when chain 1 is active and a rhodes when chain 2 is active, I could assign CC11 to an Utility's gain in chain 1, to a macro in chain 2 or a filter in chain 3, and to nothing when the chain 4 is active. So I would be using the same knob (or fader) for controling different parameters, without excluding the use of CC11 for other tasks in the future.
The best exemple would be the sustain pedal : it could serves as a sustain pedal most of the time, but in some chains it could trigger a different function. With mapping, if you map your pedal, you can say hello to the sustain feature !
Some M4L devices are doing this, but I would be so happy to have this built-in in Live...
Am I the only one to consider this as a workflow improvement ?
I did propose the feature in the Beta Center Code, but it seems I'm quite alone in seeing any usefulness to this...

Ableton has scripts for controllers to and using macros you can do what you want.

This is what people usually answer, but you can't do what I describe with scripts. More precisely, you can't do that if you have more than one controler and you don't want to use the screen.
To my knowledge, you can't use a sustain pedal like I describe with scripts.
Scripts are ok when you are alone in front of your screen and want to navigate in your session visually, but when you can't use the blue hand because 2 or more musicians are using a controler and tweaking things, or because your computer is not in front of you because it's a live show (and your controler doesn't have a screen), scripting is not useful...
Anyway, no issue, I can do that with some M4L devices even if it's less elegant and stable than a built in feature, I'm just surprised not more Live users are in search for such possibilities...

[jules99]

This kind of mapping behavior is one of the most asked-for features from the live performance community and has been for years. It's not on the radar for most KVR Ableton users as they don't perform live and don't necessarily need it.

It's not integrated at this point, so I doubt it'll happen with this release.

[nanostream]

[snip]

[SLiC]

Can also report no crashes with extensive use on Windows 11, not been able to make it fall over yet!
Still serval months of Beta to go probably, but looking OK for Windows 11 users at least.

[Trancit]

I find Ableton´s behaviour silly and like spitting on their customers...

Because the beta has been leaked to the warez scene every crack kiddie can get their hands on the new version but people who paid for it like me are still outside of the beta access...

With the crack having appeared Ableton should have at least opened the door for everybody who has already paid for it for not having a disadvantage compared to the warez users...

I was honestely expecting and hoping this but nope... the beta is already out there since 2 weeks (actually 2 iterations already) and I sit here with my bought serial and have nothing...

[SLiC]

I find Ableton´s behaviour silly and like spitting on their customers...

Because the beta has been leaked to the warez scene every crack kiddie can get their hands on the new version but people who paid for it like me are still outside of the beta access...

With the crack having appeared Ableton should have at least opened the door for everybody who has already paid for it for not having a disadvantage compared to the warez users but actually having paid for it...

I was honestely expecting and hoping this but nope... the beta is already out there since 2 weeks (actually 2 iterations already) and I sit here with my bought serial and have nothing...

Frustrating- I was in the same boat until a few days ago when it just dropped for me - paid for update, PUSH 3 SA user, Live 11 beta tester...I was like...what's the criteria! They pushed out a new update today, I wonder if that broke the existing cracked beta!