• State Suggested Answer
  • Date
    british_lampy
  • Date
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 187 subscribers
  • Views 38 views
  • Users 0 members are here

Setting Cue Execute with macro

Hi all, Am currently playing OSC as research for a future project, does anyone know if you can set cue Execute parameters using a macro?

My current macro is as follows:

```Execute Send_String /example/output/cue=%1```
It's entirely possible my macro syntax is wrong, but right now it simply does nothing when I run that command.

Parents
  • 0

    This doesn't work for multiple reasons:

    1. Send_String is the wrong command. It's used when you want to send OSC directly from the macro. You need String.
    2. The per-cue executes don't have access to the variables like %1 representing the cue number.

    It looks like you want a cue to send an OSC command with that cue's cue number. Why not use either Setup > System > ShowControl > OSC > OSC Cue Send String, or the cuielist's OSC Cue Send String property?

  • 0 in reply to eos moderator

    Thanks for your quick response!

    I will take a look at using String instead of Send_String, that looks like it will fix the issue.

    The reason I wanted to use the argument to send the cue number was to avoid having to sift through all the cues in the other programme. For example triggering a standby command on certain cues, rather than having list of cues where there will be a standby, and comparing every time there is a cue update. I could look into having a dedicated cue list for the stuff, then trigger those cues which then trigger OSC, but that would become more friction for a programmer.

    What can probably do is use a macro to create each executor, and put the cue number in the command there, rather than trying to use the %1 variable. 

Reply
  • 0 in reply to eos moderator

    Thanks for your quick response!

    I will take a look at using String instead of Send_String, that looks like it will fix the issue.

    The reason I wanted to use the argument to send the cue number was to avoid having to sift through all the cues in the other programme. For example triggering a standby command on certain cues, rather than having list of cues where there will be a standby, and comparing every time there is a cue update. I could look into having a dedicated cue list for the stuff, then trigger those cues which then trigger OSC, but that would become more friction for a programmer.

    What can probably do is use a macro to create each executor, and put the cue number in the command there, rather than trying to use the %1 variable. 

Children
No Data
Related

www.etcconnect.com