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?
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,
The Eos Family Show Control User Guide Rev B. doesn't list any /eos/set message. You likely want /eos/cmd or /eos/newcmd. I'm not sure about label commands since it involves strings of strings so some testing is required.
There are several different ways to construct an OSC message for /eos/cmd, string with command line text:
True, but according to that reference:
Typically you should build Eos command lines and send them with the command /eos/cmd or /eos/newcmd.
I have the same plan and would like to control cues via Filmaker. Can I ask which plugin you use? Is it the MBS FileMaker plugin? Did you make the system run stable?