According to the documentation of Ableton’s Max For Live LiveAPI Object, it is no longer possible to configure JavaScript functions to run in the high-priority thread of Max’s scheduler. So, Max For Live JavaScript functions run in the low-priority thread. However, I could not find any information on whether these functions are latency compensated or not.
Are Max For Live's JavaScript functions, which run in the low-priority thread, latency compensated?
For example, say I create a Max For Live device, which uses JavaScript functions, and the MIDI processing inside those functions takes 50ms. Assuming Live's latency compensation is enabled, will the 50ms of latency my Max For Live device induces be correctly compensated by Live?
Are Max For Live's JavaScript functions, which run in the low-priority thread, latency compensated?
-
- Posts: 6024
- Joined: Mon May 15, 2006 12:15 pm
Re: Are Max For Live's JavaScript functions, which run in the low-priority thread, latency compensated?
Not sure I understand properly, but from my experience, any API call from M4L has an unpredictable latency. It's just unusable for anything time critical.
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
Re: Are Max For Live's JavaScript functions, which run in the low-priority thread, latency compensated?
Thanks for the reply. Yeah, unpredictable and/or uncompensated latency is untenable for time sensitive operations.