Christoph Mann

I´ve built a massive preset controlling M4L-device, a kind of pattr-variation. It allows browsing the Live_Set, creating and wiring control-objects automatically (path,observer+remote), and interpolation of the values etc.

Problem: After leaving edit mode, or after deleting-and-re-inserting the device, some of the other various M4L-devices in the patch are messed up with their settings. I have about 50+ control-object, each receiving its path when the device is running.

Is there a limit for live.object / remote inside m4l?

Are there known side-effects of inserting live-devices to a session?

Maybe someone has the same problem (solved :-}

Is there a limit for live.object / remote inside m4l?
Are there known side-effects of inserting live-devices to a session?

Maybe someone has the same problem (solved :-}
Greetings,
Christoph


inserting-m4l-device-into-live-messes-up-other-m4l-devices

The only thing I can think of (with my limited experience of Max) is that, what with so many objects, you may have used some 'send' or 'receive' objects, and you may have given them the same name. If so, the messages won't just travel within a patch - they will travel between patches, throughout the entire Max environment. So that's probably worth checking. Make sure you name your 'send' and 'receive' objects with globally unique names.

I've found that after editing or changing M4L devices you sometimes have to save and reload the whole Live set.

This seems necessary to ensure certain initializations. Have you tried if it works for you?

I've found that after editing or changing M4L devices you sometimes have to save and reload the whole Live set.
This seems necessary to ensure certain initializations. Have you tried if it works for you?


@broc I've had the same issue - turns out that if you delete, then undo-delete the device you get the same effect.

In the end it turned out that I use such a big Liveset, that it pushes Live out of its "safe zone". Live has a maximum memory consumption smaller than the 32-bit/4GB threshold.

Beyond there, it shows up to be unpredictable. So no help for me, except outsourcing some fat Sampler instaces...

In the end it turned out that I use such a big Liveset, that it pushes Live out of its "safe zone". Live has a maximum memory consumption smaller than the 32-bit/4GB threshold.
Beyond there, it shows up to be unpredictable. So no help for me, except outsourcing some fat Sampler instaces...


Inserting M4L device into Live messes up other M4L-devices