OSC control of cue firing from Show Cue System

Are you sending an argument with the message?  number for button edge: 1.0=down, 0.0=up (optional)

If you are sending it just with the 1.0 then you are not releasing the button and the action would not trigger.  Either send it with a 1 and a 0 or send it without an argument.  

Does SCS transmit arguments or just the message?

 

I haven't used this particular command over osc but have used the /eos/macro/#/fire successfully.

 

Are you sending an argument with the message?  number for button edge: 1.0=down, 0.0=up (optional)

If you are sending it just with the 1.0 then you are not releasing the button and the action would not trigger.  Either send it with a 1 and a 0 or send it without an argument.  

Does SCS transmit arguments or just the message?

 

I haven't used this particular command over osc but have used the /eos/macro/#/fire successfully.

 

SCS gives a choice of gadgets to send OSC to, including PJLink, and Lightfactory. All the info I can find says that the above command "/eos/cue/x/fire" will work, and it has on Qlab. I chose "any Device" from the list, as it is the only one that doesn't come up with an error message. When the signal to Element is sent, the cue gets selected, but does not "fire".

And I cannot get MIDI Show Control to do anything, and I've tried 4 different midi cards, cables and many setup options in the Element. MIDI IDs go from 1-127, or 0-126. i tried offsetting, to no avail.

I gotta be missing one argument, as you say.

It will transmit anything i type in.

Have you tried to get a macro to fire. This is one of the easy events you can fire to tell if you are formatting everything correctly. Also Tab 99 diagnostics had osc monitoring in/out that you can turn on. This will allow you to watch the messages come in and see what the console is doing with them.
If you want to use the arguments you need to either transmit the 1 and then the 0 or don't transmit either one. If you just transmit a 1 then you are basically holding down a button and never releasing it.
It would be useful to know what software version you have on your element as well.

the 1 in the message is the cue number. There is no mention of adding anything to the message, but is I did want to release the "button", where would that "0" go? Would i need to put a "1" (press) in the message somewhere?

It is interesting that the manual does not list a "fire" or "start" command for the eos. just a few variations of "go" (page 90). But then again, "fire" worked with Qlab. go figure. (53)

the OSC documentation is not in the eos manual itself but in the Eos Family Show Control User Guide that can be downloaded from the Eos Family product pages where the manual lives as well. there you will find that /eos/cue/1/fire is legal syntax. but there can be arguments sent along with this message. if there is no argument then /eos/cue/1/fire is ok, but if there is an argument of 1 sent with it, you need to follow it up with the same message and an argument of 0.

Thanks, ueliriegg. I did mean page 90 of the supplement. "fire" worked for Qlab but not SCS. I think it may be the message sent by SCS itself. I have sent this question to their forum as well.

ah sorry. have you tried checking in eos diagnostic tab (Tab 99) with osc message rx enabled to see the exact message that eos receives from scs?

Somebody earlier mentioned Tab 99, and I was just going to ask what the heck that was. I will investigate. Thanks!

keep [Tab] pressed, type 99, release [Tab] ;)

thanks again!

okay- I finally got it to work! in frustration I added another"/fire" after the first one and BINGO. so it is now
/eos/cue/x/fire/fire

don't ax me why. thanks all.

What does it list the incoming OSC message in tab 99? If it is really taking an additional /fire to make it happen it may be a bug. Please take a look and post a pic.

E

SCS screen shot. Network via UDP.                                    Element screen shot                                                    

Telnet is the other choice, but won't work.

In tab 99, right hand side towards the bottom there is a button to enable OSC Rx traffic to be shown. Could you activate that and taste the picture again?

sure