• State Not Answered
  • Date
    mikewoodld
  • Date
  • Replies 10 replies
  • Subscribers 88 subscribers
  • Views 12206 views
  • Users 0 members are here

OSC Integration Questions

I am experimenting with getting the EOS to talk to filemaker via OSC and I'm running into some issues. I am very new to this, so it might be simple things. 

I'm using a plugin to send TCP/UDP strings out of filemaker. I'm directing the string (osc text) to go to the console IP on port 3032. I can send UDP commands easily - well, some of them. I can turn channels and groups on and off, fire cues, those things work without any problems.

For the life of me, I can't figure out how to get /eos/set/ commands to work, nor can I get command lines to send. 

I'm wondering if I don't have the syntax right? Assume the label for this cue is "test"

/eos/set/cue/1/1/label=test - "Correct" way using EosSyncDemo

I've found that using this plugin or a packet sender app, I have to add /enter to the ends of my commands. This doesn't seem to work on this one, though. 

I then tried to use a TCP connection instead. In filemaker, I can connect and the eos shows connected in diagnostics, but then my strings aren't arriving. Having the same issue when connecting via Packet Sender. This could be another issue.

So I guess the main question here is what should my syntax be to send UDP strings for the command line or for /set/ commands? What am I missing?

Parents
  • 0

    Mike,

    If you are using a UDP plugin there is additional work to make it OSC.  There is a difference between OSC over UDP and UDP strings.  Each has its own ports in the show control setup and needs different formatting on the application side. 

    If you can clarify what exactly you are using we may be able to help you get it working.

    TCP based OSC is a different animal as well.  

    I would suggest you get a firm grasp of how the console side works with UDP, UDP OSC, TCP OSC before trying to send packets from a plugin.  I would suggest TouchOSC as a starting point.

    In the console software Tab 99 is your friend. There are buttons to turn on OSC in/out monitoring so you can see what the console is receiving.

    It sounds like you are trying to get filemaker to send cue labels to the console.  This can be done simply by using UDP strings without any OSC involvement.

    OSC is nice because the console transmits information in addition to receiving it but you need more specificity with your packet wrapping etc to get it working on the filemaker side.

    Hope this helps,

  • 0 in reply to Druuka
    Thanks, Andrew - after reading my post from last night, I made it sound more complicated than it was... it was 4:00am. haha,

    Anyway, I'm familiar with how the console side works and I've been monitoring the messages on Tab99; my problem is in the formatting of the messages. I can get simple things like /eos/chan/1/out/enter to work. But I can't get things to post to a command line nor can I use things like /eos/set/cue/1/1/label=xxxx. Wondering what I'm missing in the syntax for those, and I'm assuming it's something to do with needing the /enter command but no matter where I put that command, it doesn't work.

    I'd like to get the OSC working because eventually I'd like to bring data back into filemaker as well, though as a first step, labeling cues via UDP string would work instead. Would the syntax for such a string be $ Cue 1 Label labeltext #?
Reply
  • 0 in reply to Druuka
    Thanks, Andrew - after reading my post from last night, I made it sound more complicated than it was... it was 4:00am. haha,

    Anyway, I'm familiar with how the console side works and I've been monitoring the messages on Tab99; my problem is in the formatting of the messages. I can get simple things like /eos/chan/1/out/enter to work. But I can't get things to post to a command line nor can I use things like /eos/set/cue/1/1/label=xxxx. Wondering what I'm missing in the syntax for those, and I'm assuming it's something to do with needing the /enter command but no matter where I put that command, it doesn't work.

    I'd like to get the OSC working because eventually I'd like to bring data back into filemaker as well, though as a first step, labeling cues via UDP string would work instead. Would the syntax for such a string be $ Cue 1 Label labeltext #?
Children
No Data
Related

www.etcconnect.com