Jump to locator
Hi, I'm trying to build a simple patch that jumps to a locator based on two int data entered by the user. So it finds such locator by name in the arrangment. Is that at all possible or do locators follow an internal ID instead?
In my mind it would work as follows. In the arrangment I will have a few locators called:
Cue.1.1
Cue.1.2
Cue.2.1
(Where the first number is Set and the second is Cue)
What I would try but don'tknow how is a simple max device with two dials from 1-100 and a Go button. When the go button is pressed it will check the dial numbers, compose the name following the naming convention avobe ("Cue." + "$Set" + "." + "$Cue") and check if such a locator exists. If it does it will jump to it. If more than one exist with that name it will jump to the first one.
Does this sound doable?
Thank you!
Check for CuePoint in the LOM.
I guess first you need to get the list of all locators using cue_points (child of the Song)
Then you can get the name of each of these locator by getting their name property.
Then it's a matter of patching the required logic allowing you to retrieve the locator index depending on its name.
Then you can use the jump function to jump to the desired locator.
you need to build name - id linked locator list.
then querry locator ID by text.
But I don't quite understand what you want to do ?
type something in the text, and f there is exact match,
jump to that locator ?
Or you maybe simply mean - let me jump to name selected locator from the umenu ?
here you have both options - fill umenu with names and other one with ID's
or fill coll.
one can recall ID's from coll by inputting symbols which should match.
if that is what you are after ...
You have changed initial post.
it is easy to form a symbol from a piece of text and few numbers.
it is collecting locator names which is difficult,
in first place because live.observer takes no notice if one renames a locator.
So you need to either rescan locators manually
or using metro …
Those are very good leads I will follow. Thank you ever so much!
To clarify what I'm trying to do is a Cue Book, a bit like Q-Lab but simpler and within Ableton. To control live stage performance like musicals and such. This will be used in combination with Clyphx.
The way it goes is, I will have a multiple .csv (currently just one) called sets that Live is reading and each row contains cue data like, text for the stage manager to read out, what Cue it has to go next (in case the user wants to have rehearsal marks that get skipped in a real performance) what actions to perform when the GO button is pressed etc. So far there are 4 possible actions triggerable by GO and the goto locator is the only one not working yet:
1 - Go to the locator matching the locator name tag in one of the fields on this row. ie Cue.12 or Song1Start (so scrap part of my brief in the opening of this thread) as now I'm thinking the name of this locator should be better defined in one of the fields rather than using the number of the cue.
2 - Start playback (working)
3 - Stop Playback (working)
4 - Trigger a midi note defined by numerical values in the CSV (working but not useable for Ableton control without rewiring like with loopMidi)
Hope this clarifies things, sorry for the convoluted explanation. I'm very new to dev/design. I'll sare a version of what I've got so far next time I'm at the studio pc
So what I think I need to figure out now is to:
0 Receive a string - receive a bang
1 collect all the locators in the scene
2 check if any of these locators match the string given
3 if one of them does, interrupt and jump to that number
4 if none of them do, do nothing
But I lack any knowledge on how to do this in max, unrotunately.
Thanks for reading, I feel like I'm a few inches away :D
No problem, once you provide all infos needed it is easy to make it work.
But you have several requests, could you delete all and make new, correct plan of it ?
1- what do you mean by "If more than one exist with that name it will jump to the first one."
the first one could be one with lowest/earliest position in timeline
or one closest to current play position ?
or is that now irrelevant ? (no duplicate locator names)
2- where are infos with stored cue names available to max device ?
3- "Cue.12 or Song1Start"
does live allow more than one Song (set ) to be opened at same time ?
also :
"collect all the locators in the scene"
Does Live have locators per scene ?
and so on ...
P.S.
first rescan locators, then recall if matched will cost a bit of time .