John Courte

Is there any efficiency to be gained by working with live.path vs M4L API calls? I guess that's an obtuse way to ask, what's the best option for track and scene selection, A/B assignment, mute, solo, etc?

Is there any efficiency to be gained by working with live.path vs M4L API calls?  I guess that's an obtuse way to ask, what's the best option for track and scene selection, A/B assignment, mute, solo, etc?

m4l-api-calls-vs-live-path-operations

Sorry, that was a noob post. It looks like the same thing, ex. M4L.api.SelectNextTrack is an abstraction containing live.path logic. Is that correct?

Sorry, that was a noob post.   It looks like the same thing, ex. M4L.api.SelectNextTrack is an abstraction containing live.path logic.   Is that correct?


Not really sure what the question is? live.path is almost certainly included in any code that talks to the API. You need to query live.path to find any id for live.object calls.

I posted that question before I figured out what abstractions were. :) M4L.api.SelectPreviousTrack is a wrapper around a bunch of other things that are themselves wrappers around live_path object, and I probably misunderstood the concept of a call in relation to M4L.

I posted that question before I figured out what abstractions were. :)  M4L.api.SelectPreviousTrack is a wrapper around a bunch of other things that are themselves wrappers around live_path object, and I probably misunderstood the concept of a call in relation to M4L.


M4L.api calls vs live.path operations