metamax

I am just beginning to explore M4L and I have noticed that some of my devices are painfully slow to edit. When I click the edit button of a loaded device, the patch opens but it pinwheels for well over a minute when I attempt to toggle from presentation view to edit view. Is there something I can do to fix this?

I am just beginning to explore M4L and I have noticed that some of my devices are painfully slow to edit.  When I click the edit button of a loaded device, the patch opens but it pinwheels for well over a minute when I attempt to toggle from presentation view to edit view.  Is there something I can do to fix this?


m4l-editor-slow-to-open

I am using the 32bit version of both Max and Live so I'm not sure anything beyond 4GB is even relevant. Regardless.. I have 16GB of RAM in my system. There is no room for more. :/

Are there any significant differences between patching in Max and patching in M4L? Do I need to be careful of certain things in M4L to prevent this kind of lag?

I am using the 32bit version of both Max and Live so I'm not sure anything beyond 4GB is even relevant. Regardless.. I have 16GB of RAM in my system.   There is no room for more.  :/

Are there any significant differences between patching in Max and patching in M4L?  Do I need to be careful of certain things in M4L to prevent this kind of lag?


In my experience the slowness of M4L editing mainly depends on the number of API controls (eg. live.remote~) that are used in the patch. Apparently maintaining the connections in the editor is rather complex, especially in preview mode where 2 copies of the device must be handled.

https://cycling74.com/docs/max5/vignettes/core/live_preview.html

Hmmm.. well, thing is, there aren't any API controls except for a single live.thisdevice to bang some initial settings. I think I may have had too many live.grid objects in the patch. Now there is just a single live.grid object but it still pinwheels for several seconds when I initially go from presentation to edit view. Other patches don't do that, so it's not a hardware issue. I think I just need to get familiar with the idiosyncrasies of M4L. In general, it definitely seems a bit clunky and buggy compared to regular old Max.

Hmmm..  well, thing is, there aren't any API controls except for a single live.thisdevice to bang some initial settings.  I think I may have had too many live.grid objects in the patch.  Now there is just a single live.grid object but it still pinwheels for several seconds when I initially go from presentation to edit view.  Other patches don't do that, so it's not a hardware issue.  I think I just need to get familiar with the idiosyncrasies of M4L.  In general, it definitely seems a bit clunky and buggy compared to regular old Max.

I think it happens to me even when there are no API calls in the patch.

M4L editor slow to open