Jump to specific cue points?

Feb 14, 2012 at 6:08pm

Jump to specific cue points?

From the the LOM (Live Object Model Reference) it seems it is NOT possible to jump to a specific marker/cue point using MaxForLive commands.

I can only find things like “jump_to_next_cue”.

Is this correct? Any known workarounds?

Feb 14, 2012 at 9:11pm

Cue points are children of the Song class numbered from 0 to N (just like tracks or scenes).
You can jump to a specific point by using its path and call the ‘jump‘ function.

– Pasted Max Patch, click to expand. –
Feb 14, 2012 at 9:29pm

Thanks so much for the suggestion, but I don’t think that will work very well for what I want. I want to have, say, 20-30 locators, and jump at will between them. With the solution above, with each locator having its own object, this would become very messy – I think.

Strange that this hasn’t been done in a more easy way, considering it’s possible to assign keys and MIDI notes to locators.

EDIT! Never mind, figured it out! Since live.object accepts “id” messages, there are no problems sending “id 1″, “id 2″, “id 5″ messages etc. into the right inlet of live.object, at least after the “live_set_cue_points” have been triggered once. That makes this a lot easier … thanks!

Jan 14, 2014 at 7:04am

Thank you BROC and OIVINDI! I’ve been pulling my hair for the last hour. The little word “call” worked the magic.


You must be logged in to reply to this topic.