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" ?

[Sterioevo]

I now use https://maxforlive.com/library/device/10291/remote2mod which allows a similar behaviour to Midihub regarding "permanent" mapping.
It doesn't have some of the other features such as curve and min/max, although it is an attenuator. You could use another device upstream to do this though, such as https://maxforlive.com/library/device/6779/mapul8tor or https://maxforlive.com/library/device/6968/mapper-ki.

Edit: you would need a cc mapping device upstream to receive your controller data (or add this functionality to an existing device).

I often modify max devices for my specific needs and when I do this a "Project" folder is created in the Max folder (in Documents on my Mac) with any required files, such as images and others, that are part of/referenced in the Max device. When installing Live 12.2, Max 9 is installed and the Project folder is empty. So when I open existing files using these max devices they don't appear or work as expected. I need to copy the project files in the Max 8 folder across to Max 9 and restart Live to get the working as expected. I speculate this may be because I haven't repacked the max devices as you would for distribution.

[Calagan]

I now use https://maxforlive.com/library/device/10291/remote2mod which allows a similar behaviour to Midihub regarding "permanent" mapping.
It doesn't have some of the other features such as curve and min/max, although it is an attenuator. You could use another device upstream to do this though, such as https://maxforlive.com/library/device/6779/mapul8tor or https://maxforlive.com/library/device/6968/mapper-ki.

Edit: you would need a cc mapping device upstream to receive your controller data (or add this functionality to an existing device).

I often modify max devices for my specific needs and when I do this a "Project" folder is created in the Max folder (in Documents on my Mac) with any required files, such as images and others, that are part of/referenced in the Max device. When installing Live 12.2, Max 9 is installed and the Project folder is empty. So when I open existing files using these max devices they don't appear or work as expected. I need to copy the project files in the Max 8 folder across to Max 9 and restart Live to get the working as expected. I speculate this may be because I haven't repacked the max devices as you would for distribution.

thanks a lot for the detailed explanations. I'll check this out (I already planned to buy Mapper Ki : it's not exactly done to do what I need, but it seems it CAN do what I need. I already sent an email to the dev).
But whatever, it seems MidiHub will not work in Live 12.2... I would be curious to know why...

EDIT : I think I will try to use the built in Expression Control instead, adding some CC translator before it. So for exemple I could use my knob sending CC14 in order to map something. And if I need to use my knob sending CC15, then I will add another Expression Control with another CC translator before it. Convoluted, not very elegant, but it should work. I'm a bit fed up with being dependant on third party devices that are never updated (of course it's free, so I understand why)...
I don't understand why they don't add the basic feature of choosing what CC you want to receive in Expression Control, instead of using only CC11...

[Sterioevo]

Totally understand things can get convoluted. I have found on more than one occasion though that devices such as Killihu’s can open up a solution not previously considered.
An alternative approach to cc is to use remote maps for macros (or devices). For example I have a remote map for my midi fighter twister for the macros in chain 1 of a grouped track (so a second layer of macros). This can allow a standardized midi setup.

[Calagan]

I've just updated to 12.2
I don't have my keyboard under the hand now, but with the quick tests I did so far using another M4L sending some midi CC (instead of my keybord), it seems Midi Hub is working without crashing Live.
@Sterioevo : did you experience any crash with Midi Hub used in a 12.2 session ?
I know, I need to test it by myself in real life context, but I'm curious

[chimp_spanner]

I'm back to Live after a couple of years away learning Logic. This is WAY more my vibe. Especially with Reason Rack Plugin. Dream combo. I'm loving the new filter. And bounce in place is working great for me.

Also I don't know at what point this changed, but I can finally see all of my samples within subfolders (like I can search my entire Splice location for "kick" - never worked before). So that's great also!

One thing I would really like to see is Group Track Container Regions *or* the ability to interact with the contents of a collapsed Group track in the arranger when folded. Intuitively I feel like I should be able to select a region on the folded track and click/drag to move it around. What I can do is CMD+D to duplicate it. So there's that, at least! But I'd love to be able to move it, option drag to copy it somewhere else, etc.

Sorry, realise that's a feature request. Maybe I'll submit it properly haha.

[Calagan]

I just tested the new 12.2 update with the Live set I previously had issues with (Midi Hub and/or other M4L mapping devices were crashing Live).
It's working fine now !

I couldn't test 12.2 on many sessions yet, but so far it seems very stable, maybe even a bit snappier than before.
And of course, the new features are great !

Thanks to all the Ableton team for this great update !

[Sterioevo]

I've just updated to 12.2
I don't have my keyboard under the hand now, but with the quick tests I did so far using another M4L sending some midi CC (instead of my keybord), it seems Midi Hub is working without crashing Live.
@Sterioevo : did you experience any crash with Midi Hub used in a 12.2 session ?
I know, I need to test it by myself in real life context, but I'm curious

I did just manage to open a previous version of a track with multiple midi hubs without a crash in 12.2, however I don't think the performance is as effective in my case as compared to some changes I have made (replacing the midi hubs), as it seems a bit glitchy/cpu heavy.
@Chimp_Spanner - I haven't delved into the new filter yet..........