maybites

is-there-or-will-there-be-an-sdk-for-m4l

There is no separate SDK. Is there something specific for which you are looking?

There is no separate SDK.  Is there something specific for which you are looking?

I have written a Patch with a JavaScript subpatch in it to handle OSC Events which in turn control Lives Parameters. While it works fine for a handfull of events a second, I notice huge latencies once there are hundreds of them. it looks as if max is queuing the not yet processed events and my javascript subpatch is to slow to handle them in time.

To be more precise: Is there an API for C similar to the one for JavaScript?:

https://cycling74.com/docs/max5/vignettes/js/jsliveapi.html

I have written a Patch with a JavaScript subpatch in it to handle OSC Events which in turn control Lives Parameters. While it works fine for a handfull of events a second, I notice huge latencies once there are hundreds of them. it looks as if max is queuing the not yet processed events and my javascript subpatch is to slow to handle them in time.
To be more precise: Is there an API for C similar to the one for JavaScript?:

At this time there is not. Javascript is it. Good luck!

At this time there is not.  Javascript is it.  Good luck!


If you are sending in a lot of values for a single parameter or parameters, like an LFO or some such, you are going to be much better off filtering these messages into your patch and modifying the target params with live.remote~ then you would trying to handle them all inside your js. The bottleneck in Live API communication is the cross process communication, not the speed of js or C. JS is more than fast enough to keep ahead of it for now. But live.remote~ was specifically designed to be able to modify Live parameters at audio rate.

Feel free to send the patch and script and what have you into support and we can have a look at it as part of optimization efforts

If you are sending in a lot of values for a single parameter or parameters, like an LFO or some such, you are going to be much better off filtering these messages into your patch and modifying the target params with live.remote~ then you would trying to handle them all inside your js. The bottleneck in Live API communication is the cross process communication, not the speed of js or C. JS is more than fast enough to keep ahead of it for now. But live.remote~ was specifically designed to  be able to modify Live parameters at audio rate.

thank you for this info. based on this I retested my JS patch and can now confirm your statement regarding live.remote~. the reason I got those latencies was the wrong string comparison method I applied:

it is now as quick as I can wish for, without any feelable latencies and even with up to 350 osc messages per second.

I will post the patch to the community anyway, as soon as I have done some cleaning up, I think some people might be interested in it.

thank you for this info. based on this I retested my JS patch and can now confirm your statement regarding live.remote~. the reason I got those latencies was the wrong string comparison method I applied: 

var a = "set";
if(a.indexOf("set") == 0){
   etc...
}

is much slower than:
if(a == "set"){
   etc...
}

is there, or will there be an sdk for m4l?