Live 12.2 is out now !

[Calagan]

It's alive !

I'm very frustrated because I will not be able to update my 12.1.5 version until the next week (I've got a gig and never update nothing if I don't have few weeks free in front of me in order to check if everything is working).

Please share your thoughts on the new update here.
(I'm particularly interested in knowing if it's stable for you and if they fixed the M4L issues I had with 12.1.10 and 12.1.11, where mapping M4L devices were crashing Live)

[Rivanni]

It's alive !

Please share your thoughts on the new update here.

Just keep an eye on all the different forums, social media etc from now on.
Many have already installed the release version, so you can find posts about it.

if they fixed the M4L issues I had with 12.1.10 and 12.1.11, where mapping M4L devices were crashing Live)

Without specifying the issue you had, nobody can give you an answer.

[overdrivenundercrunched]

When filtering in the All label, presets are now grouped into their device folders.

Why does this also include presets that are specifically tagged themselves? I have an instance of OTT with a macro that changes the upward compression and one that controls the downward compression, and now instead of being easily accessible in my Compression tag, it's nested under Audio Effect Rack. Why can tags not simply work like Collections, where I can decide exactly what I want to be shown under them?

[Calagan]

Without specifying the issue you had, nobody can give you an answer.

For clarifying : since the 12.1.10 version, Live is crashing when I use some specific M4L devices, usually mapping devices.
In particular MidiHub.

It's not crashing immediatly, but usually at some random moment when I use these mapping devices.

[Rivanni]

When filtering in the All label, presets are now grouped into their device folders.

Why does this also include presets that are specifically tagged themselves? I have an instance of OTT with a macro that changes the upward compression and one that controls the downward compression, and now instead of being easily accessible in my Compression tag, it's nested under Audio Effect Rack. Why can tags not simply work like Collections, where I can decide exactly what I want to be shown under them?

A group of users requested that the presets be grouped by device. Rather than allowing users to customize their preset display, Ableton opted to discard the flat list and group the items by device.
In the Plugins section, there is an option to group by Creator, enabling users to select their preferred plugin display. Similarly, a group-by-device option for presets should have been added.
There is a workaround. Select the 'Preset' tag under Content, and you'll get a flat list of presets that fit the other selected tags. You can save the chosen tags as a label in the sidebar, allowing you to access your presets this way.

[As_Yoesual]

*looks around*
This might be my first post here after all those years of lurking.

So, I just downloaded 12.2, and dropped the new auto filter.
But all I'm getting is the "Auto Filter Legacy" version.
--generally-- after an effect/module gets updated, it will have a nice big shiny "update" or "upgrade" button on it.
But, not for my auto filter.

What... am I missing?

Edit:
Just when I wanted to post this, I realized it was because my template hadn't been resaved, so it was considered legacy.
Resaving it in 12.2 fixed it.

[Sterioevo]

Without specifying the issue you had, nobody can give you an answer.

For clarifying : since the 12.1.10 version, Live is crashing when I use some specific M4L devices, usually mapping devices.
In particular MidiHub.

It's not crashing immediatly, but usually at some random moment when I use these mapping devices.

I have also found MidiHub to be potential problem. I haven't communicated with the author in relation to this, but I have replaced the devices in live sets and crashes I have been experiencing since 12.1.10 have disappeared. This is consistent through 12.1.12 (I think) to 12.2. In my case I switched to modulation/remote rather than cc (MidiHub).
I will say though that I have this recurring issue when I install a new version of Ableton that my (modified) max for live devices do not work as expected out of the box. I need to copy the project files across into the max installation folder to get things working as expected - **** this information may be useful to someone...
Thanks Ableton. Things are rockin and rollin again

[Calagan]

Without specifying the issue you had, nobody can give you an answer.

For clarifying : since the 12.1.10 version, Live is crashing when I use some specific M4L devices, usually mapping devices.
In particular MidiHub.

It's not crashing immediatly, but usually at some random moment when I use these mapping devices.

I have also found MidiHub to be potential problem. I haven't communicated with the author in relation to this, but I have replaced the devices in live sets and crashes I have been experiencing since 12.1.10 have disappeared. This is consistent through 12.1.12 (I think) to 12.2. In my case I switched to modulation/remote rather than cc (MidiHub).
I will say though that I have this recurring issue when I install a new version of Ableton that my (modified) max for live devices do not work as expected out of the box. I need to copy the project files across into the max installation folder to get things working as expected - **** this information may be useful to someone...
Thanks Ableton. Things are rockin and rollin again

I'm curious about what you mean by "I switched to modulation/remote rather than cc (MidiHub)" ?
On a Live set I'm using on stage, MidiHub is a central and essential part : I need to be able to control many different parameters through CC without permanent mapping (for exemple, CC14 controls FX-A on scene 1, and FX-B on scene 2, and so on).

How did you replace it ? And with what stable device ? I like midi Hub because I can set different curves and also min-max for each situation. I didn't find any "official" or built-in tool in Live that can do that : temporary mapping + curves + min-max settings...

Finally, what do you mean by "I need to copy the project files across into the max installation folder to get things working as expected" ?