Live Suite 12.1.11 -- Any more stable than 12.1.10?

[otalgia99]

Hello, Ableton-O-Sphere

I rolled back Live Suite from 12.1.10 to 12.1.5 on account of experienced instability in ".10."

Do any of you have stability remarks or observations regarding 12.1.11? Is it still shaky or can I jump back up?

o-99

[Sterioevo]

Hi,

Not for me unfortunately, no improvement. I did a couple of crash reports and then went back to 12.1.5 for production.

You can install multiple versions at the same time to test, just rename your existing install so it doesn't get written over.

Steve

[Gral]

The update from 12.1.5 to 12.1.10 also caused me serious problems. Above all, I could no longer freeze tracks. The update to 12.1.11 did not bring any improvement either.

Since there are hardly any other problems reported here with these versions, I took a closer look at what could be the cause. The culprit was the options.txt file. I had entered a few things there that no longer work together from 12.1.10 onwards. Unfortunately, I can't say which entries were involved as I'm currently working on a different computer. In any case, all my problems disappeared after I had properly trimmed the options.txt.

If you are using the options.txt, I would rename it and see if the problems disappear.

Greetings

Gral

[otalgia99]

The update from 12.1.5 to 12.1.10 also caused me serious problems. Above all, I could no longer freeze tracks. The update to 12.1.11 did not bring any improvement either.

Since there are hardly any other problems reported here with these versions, I took a closer look at what could be the cause. The culprit was the options.txt file. I had entered a few things there that no longer work together from 12.1.10 onwards. Unfortunately, I can't say which entries were involved as I'm currently working on a different computer. In any case, all my problems disappeared after I had properly trimmed the options.txt.

If you are using the options.txt, I would rename it and see if the problems disappear.

Greetings

Gral

Thank you!

I'm entirely new to options.txt. I'm not intentionally using it -- so far as I know -- but are items written to this file "under the hood" when one assigns various preferences? Or is its use something one must proactively engage

Best regards,
o99

[otalgia99]

Hi,

Not for me unfortunately, no improvement. I did a couple of crash reports and then went back to 12.1.5 for production.

You can install multiple versions at the same time to test, just rename your existing install so it doesn't get written over.

Steve

Thank you, Steve -- not perhaps the answer I was hoping to hear, but extremely helpful and informative nonetheless.

Could the difficulties be in any way associated with operating system versions? (I'm using OS14.7... maybe the newer versions of Live are looking for 15?)

Again, very much appreciate you taking the time to offer your observations.

o99

[Sterioevo]

I am using Sequoia 15.4.1 on a M2 Max Mac Studio. These issues have persevered through operating system updates.
I feel my issues appear relate to existing Sets that make extensive use of Max for Live devices.

[otalgia99]

I am using Sequoia 15.4.1 on a M2 Max Mac Studio. These issues have persevered through operating system updates.
I feel my issues appear relate to existing Sets that make extensive use of Max for Live devices.

Thanks for the perspective! I've been contemplating the move from Sonoma to Sequoia on my performance laptop (tho my production environment might not be ready for that step) so this is very interesting information apart from my prime topic.

Returning to my original question -- I enjoy using a number of M4L devices myself, and your remark makes me realize that I really don't know whether or not M4L development occurs independently of advances made for Live.

If Max For Live has its own development track, then perhaps we're all waiting for it to "catch up" to the current version of Live?

o99

[Calagan]

I am using Sequoia 15.4.1 on a M2 Max Mac Studio. These issues have persevered through operating system updates.
I feel my issues appear relate to existing Sets that make extensive use of Max for Live devices.

I had the exact same issue with Live 12.1.10, running on a Mac M1 Pro / MacOs 14.7.5.
No problem on a basic Live set, but as soon as I started to use some M4L mapping devices, it became a crash party.

In my case, it was only when operating the M4L devices. When M4L devices were not in use (even if they were present in the tracks), I didn't have troubles.

So I had to downgrade to 12.1.5
I've sent a support request to Ableton (and please, do the same on your side), but I don't know if the latest beta versions did fix the issue so far...

The support team suggested me to use the Max 9.0.4 version (instead of the one bundled with Live), but I didn't test this suggestion yet : I use Live on stage, so I can't tolerate any unstability (nor any "testing different versions and see if it works").
I just downgraded to 12.1.5 and everything is fine now.
But I miss for the last features of Live so I'd be glad they fix this issue...

So I would suggest you first to test if your issues are associated with the use of M4L devices, then to send an email to the support with the most informations you can gather, and then to test with the Max 9.0.4 version (or the latest one, that is not bundled in Live).

[otalgia99]

I had the exact same issue with Live 12.1.10, running on a Mac M1 Pro / MacOs 14.7.5.
No problem on a basic Live set, but as soon as I started to use some M4L mapping devices, it became a crash party.

In my case, it was only when operating the M4L devices. When M4L devices were not in use (even if they were present in the tracks), I didn't have troubles.

So I had to downgrade to 12.1.5
I've sent a support request to Ableton (and please, do the same on your side), but I don't know if the latest beta versions did fix the issue so far...

The support team suggested me to use the Max 9.0.4 version (instead of the one bundled with Live), but I didn't test this suggestion yet : I use Live on stage, so I can't tolerate any unstability (nor any "testing different versions and see if it works").
I just downgraded to 12.1.5 and everything is fine now.
But I miss for the last features of Live so I'd be glad they fix this issue...

So I would suggest you first to test if your issues are associated with the use of M4L devices, then to send an email to the support with the most informations you can gather, and then to test with the Max 9.0.4 version (or the latest one, that is not bundled in Live).

I contacted support and was given the same suggestion to update Max.

Unfortunately however, I don't own "for real" Max -- I have to rely on the bundled M4L version. Still curious what the update path of M4L is -- whether it advances along with Live, or has its own development timeline.

I can't imagine that Ableton support isn't aware of the difficulties folks are experiencing with versions above 12.1.5 as we are not the only ones who have discussed this, but I guess another support request is in my future.

With thanks,
o99

[Calagan]

In the beta 12.2b9 (released march 12) there's a M4L update to the Max 9.0.5 version and there's a little mention that says : "Max for Live: fixed crash when loading some devices". And there's also a huge quantity of new features.

Since then, the beta updates are only refining the version and fixing some bugs...

I don't use the betas, but it seems promising. I asked the support if it fixes the issue we have, but of course they don't know...
So let's wait for the next official update and let's see if it's working.

Until then, I'm a bit surprised there's not more noise about these issues. Or maybe they are only related to specific systems, but M1 pro/Sonoma and M2 max / Sequoia are not rare systems in the audio production world...

[otalgia99]

In the beta 12.2b9 (released march 12) there's a M4L update to the Max 9.0.5 version and there's a little mention that says : "Max for Live: fixed crash when loading some devices". And there's also a huge quantity of new features.

I don't use the betas, but it seems promising.

Promising, indeed!

So let's wait for the next official update and let's see if it's working.

That sounds like the best approach for now.

Until then, I'm a bit surprised there's not more noise about these issues. Or maybe they are only related to specific systems, but M1 pro/Sonoma and M2 max / Sequoia are not rare systems in the audio production world...

I know, right? I'm a bit curious about that too -- a prior thread on the same topic had quite a bit of participation. Perhaps 12.2 will solve all.

o99