Ableton Forum

Making progress.
Simply observing the two properties "muted_via_solo" and "muted" on a chain, does NOT crash live on close.

chapelier fou wrote: ↑

Wed Jun 12, 2024 12:01 pm

Thanks for PMing the set.
It does crash on close, indeed. That's a serious issue.
I'll try to reduce the problem to the smallest patch possible and pass it to support.

Thanks also for the confirmation. As described here, all you have to do is deactivate the connections to the two observers and nothing will crash anymore.

MichaelAbletonForum wrote: ↑

Fri Jun 14, 2024 12:28 pm

Thanks also for the confirmation. As described here, all you have to do is deactivate the connections to the two observers and nothing will crash anymore.

Yes but that doesn't necessarily proves that the observers themselves are responsible for the crash, it can be what's processing their output, for instance.

chapelier fou wrote: ↑

Fri Jun 14, 2024 1:16 pm

MichaelAbletonForum wrote: ↑

Fri Jun 14, 2024 12:28 pm

Thanks also for the confirmation. As described here, all you have to do is deactivate the connections to the two observers and nothing will crash anymore.

Yes but that doesn't necessarily proves that the observers themselves are responsible for the crash, it can be what's processing their output, for instance.

It crashs also if the output is not connected.

Data is not arriving at the [join] simultaneously, yet all inlets trigger the output. So when one inlet receives data, signals (incomplete) are already sent.
The device no longer crashes when I add a [buddy] before the join. The device doesn't work properly anymore because you have to change things, but I would investigate this further.

I just realised this could explain the same type of crash I've been experiencing for at least 2 years now... in devices where the mute property is indeed observed.
My workaround has been to edit those devices in Max standalone instead.

[jur] wrote: ↑

Mon Jun 17, 2024 3:09 pm

I just realised this could explain the same type of crash I've been experiencing for at least 2 years now... in devices where the mute property is indeed observed.
My workaround has been to edit those devices in Max standalone instead.

Ok that’s a workaround for edit, but should I always restart the workstation when I change the project. This bug here is exactly introduced with 11.3. Until 11.2 everything works perfectly. But I found half a dozens crash setups introduced between 11.2!and 11.3. All my devices are effected and are now worthless. I’ve stopped working with M4L since then.

OMG! Its fixed with 12.1!!

THX a lot!

Really ? Good news !