Iain Duncan

Hi folks, I'm wondering if anyone can point me at resources on how the threading/scheduler model is different when working in M4L instead of Max. I'd like to start work on a Live oriented version of Scheme For Max this spring and figure there must be things I need to know!

Hi folks, I'm wondering if anyone can point me at resources on how the threading/scheduler model is different when working in M4L instead of

threading-model-differences-between-max-and-m4l

Hi IAIN, It's not different afaik. I know "overdrive" is always on in m4l. More important is if the editor is opened in m4l, the patch runs in a separate thread communicating with the Live thread. If it's closed, the device runs included in the Live thread which sometimes leads to different behaviour in one of the cases. But you probably know that.

Thanks. So rules about low and high priority thread still apply? Do you know if the thread we get in when the patch is open is the same as the low thread?

I'm not completely sure. I think hi and low are present in both situations but when editor is open it's like 2 apps are open (Live and Max) and communicating with each other. Compared to runtime mode where it's only the Live app running the MAx process internally where a hickup of Max is blocking the complete Live app.

But to deal with it we have the preview mode in the editor. Device runs in Live but editor remains open.

Thanks, sounds like I'll need to do some experimenting!

Threading model differences between Max and M4L?