Ableton Live / M4L Crash Freezing since 11.3.10 when using observer API

[MichaelAbletonForum]

I've updated my live to 11.3.10 from 11.2 on my Windows 11 Workstation.

When closing Live it always crashes within seconds (unexpected error) and all resources were still blocked. Edit on M$L Dvices crashes the MAX App. So every time a restart is needed.

Now after many hours I've found one!! reproduceable error in one of the devices

If an observer in a chain is set to mute

Canonical path
live_set tracks N devices M chains L

Ableton live will crash on close, but the observer works well.

Any advise would help. Is there a common way to cancel the observe object.

[[jur]]

Might be because of the Max 8.5.5 bundled version. You can still use another external Max as a workaround.
Could you please report to Support?

[MichaelAbletonForum]

I found a second issue in the same LOM Path

muted_via _solo in a chain

Same behavior: Observer works but if you start M4L edit or close Ableton will freeze with blocking all resources

And it also affects the return_chain with the same properties: mute and muted_via_solo

About the version: Its not the 8.5.4 should be one bevor.

I have no experiences with running a different Max Version, and I'm little bit scared to do that. Does it also affect the factory M4L Devices?

In the meanwhile I gave up a lot of my projects are still crashing and i have to reboot the system to change a project. Then i have to edit the device with the MAX Standalone and try things (remove some functionality) go back and test -> crash -> restart and that in the loop.

But when I am the only one with this issue it could be that i doing things wrong. Could be that no one uses the chain via M4L

I will check it on a different workstation.

[[jur]]

I have no experiences with running a different Max Version, and I'm little bit scared to do that. Does it also affect the factory M4L Devices?

Nothing to worry about, it won't affect any device. It'll just use another Max version to run all the stuff.
Just download and install Max, then in Live's File Folder preferences you'll find an option to select an external Max build.
You can revert back anytime with a press of a button.

[MichaelAbletonForum]

Ok, but then I have to manage multiple installations of MAX. I’ve read with renaming the current installation and then install another one. What a mess. Then I have to keep track which patcher is developed with which version and always start the related version. In some patchers I use new functions. It’s not only the installation. That’s all to much for a nonprofit/ hobby . It works the last years and makes fun, but I think I’m not ready for such additional tasks

And I know how long bugfixing takes for issues that only a few people have. years!

I’ve read via Java script it is possible to cancel the observer, set it to null. This could be a solution:

Press a button bevor closing Live and remove the observer.

How can I cancel an observer? I’ve searched a lot. Any advise?

[MichaelAbletonForum]

Results so far

setting the observer (mute and muted_via_solo) to id 0 will prevent Live crashing. M4L Edit via device still crashes (i dont know why)

But:

I've added a button on the device to set the observer to id 0, that works.

Then i tried to do it via freebang or closebang but the crash is faster. I also used some "tricks" closebang in the subpatcher, nothing works.

What is the earliest event that i can use within a patcher when M4L starts the closing event chain? Audio engine? GUI? Any adwise would be awesome. (Has to be push 3 standalone compatible, so no js)

[MichaelAbletonForum]

So i found a workaround so that my devices work, not so elegant but it helps.

Bug is reported to the MAX Team.

[[jur]]

So i found a workaround so that my devices work, not so elegant but it helps.

Bug is reported to the MAX Team.

Pleas also report to Support! Thanks.

[MichaelAbletonForum]

Live still freezing with update 11.3.20.

[MichaelAbletonForum]

Live 12 still crashing!!!

Only one m4l device used. Crash! Ableton said that they aware of this. Then: When you are not willing to resolve this bug. Remove it from your description! So bad, very bad!