OSC Inputs - Use arguments to fire cues within specific cue list

I see that /eos/cue/fire=<cue number> treats the argument as the cue number to fire.

Is there a way to specify a target cue list, fire a cue within it, but still use the OSC argument as the cue number? Currently it automatically assumes I'm firing cues in cue list 1/, when cue list 1 doesn't even exist and I have my target cue list loaded.

Parents
  • Yes.  Have a look here: OSC Dictionary

    "/eos/cue/<list number>/<cue number>/fire"

    /eos/cue/35/123.4/fire

    will fire cue 123.4 in list 35.

    You can also use variables in the OSC pattern. The general syntax for "Make Eos fire an arbitrary Cue List # / Cue # with variables 1, 2" is:

    /eos/newevent=Run_Cue %1 / %2,1,1
    So for example, to fire Cue List 58, Cue 35, this style of syntax is 
    /eos/newevent=Run_Cue %1 / %2,58,35
    It's described partway down in that same OSC User Manual page.
Reply
  • Yes.  Have a look here: OSC Dictionary

    "/eos/cue/<list number>/<cue number>/fire"

    /eos/cue/35/123.4/fire

    will fire cue 123.4 in list 35.

    You can also use variables in the OSC pattern. The general syntax for "Make Eos fire an arbitrary Cue List # / Cue # with variables 1, 2" is:

    /eos/newevent=Run_Cue %1 / %2,1,1
    So for example, to fire Cue List 58, Cue 35, this style of syntax is 
    /eos/newevent=Run_Cue %1 / %2,58,35
    It's described partway down in that same OSC User Manual page.
Children
Related