Subnets are complex, but we can keep it simple for now: So with two Eos family consoles, one could have the address 10.101.100.20, and the other 10.101.90.101 - so far so simple.īut the IP addresses of two devices must be in the same subnet, if those devices want to talk to each other. An IP address consists of 4 digits between 0 and 254 separated by decimal points. The trade-off is that OSC can be more time-consuming to set up.įor an in-depth look at how OSC is implemented in Eos, see the Eos Manual.Įach device on a network must have an IP address, which must be unique within that network. The advantage of OSC is that no additional MIDI hardware is required, as everything happens on the network, and that OSC is much more powerful. Luckily, both Eos and QLab are flexible enough to avoid this.įormerly, the MIDI protocol was commonly used for this purpose. If the sound software can only output in the format "/cue/1/go", but the lighting console can only understand in the format "/lights/cue/1/fire", we have a problem. Part of the trick in getting different devices to talk to each other is to have them speak each other's language. Other devices implement OSC in different ways for example, QLab would understand the incoming command "/cue/1/start". For example, Eos can understand commands like "/eos/chan/1/out", which would turn off channel 1, or "/eos/cue/1/fire" to run Cue 1. Thanks for reading.OSC is an open protocol which allows the sending and receiving of human-readable messages between sound, lighting and other entertainment technology systems. If you have questions, quibbles or comments- hit me up! I love discussing this stuff. If that works for you- this method will serve you well. This whole approach benefits from one person who can be in charge of numbering both cue stacks. When you go on Cue 1 in EOS, Cue 1 in QLab will fire as well. Make sure Use OSC Controls is engaged with a check mark.įrom here, the last thing is a working method: The lighting cue number must match the number of the sound cue you wish to trigger. Under Settings (cog in the lower right hand corner), select the OSC Controls tab. Cue and start are self-evident, but “%1” tells EOS to send the cue number of the cue that is being fired. In our case, we need to enter “/cue/%1/start” into that field. Last, we need to add some information to OSC Cue Send String to make it so Qlab can understand the OSC messages EOS sends. Under OSC UDP TX IP Address, enter your Qlab computer IP. Next, let’s tell EOS what IP address it should be sending these messages to. We need to tell EOS to speak on OSC UDP TX Port 53000 and listen on OSC UDP RX Port 53001(optional). So let’s turn on OSC TX (transmit) and it’s optional to turn on OSC RX (receive). Qlab has a fixed port it prefers to listen for OSC messages, and that is 53000. On the EOS side, we need to enable several things. In my case, I’m using 10.101.50.111 for the QLab computer. You can manually set your IP for the network adapter for your computer to anything complimentary. Since I’m a lighting person first (I have a long sound history as well, but I’ve always earned a steadier income from lighting), I suggest you have the sound computer follow your IP scheme from EOS. NetworkingĪs always, the first step is to plug in and network the two systems together. ![]() I chose short files so I can fire cues back to back without having to hear many songs overlap. In your Qlab file, create four or so sound cues numbered 1 through 4 of any sounds you like. We will again be using the ETC EOS Family Level 4 Complete file for our EOS showfile. ![]() We will only telling you the steps needed to sync it to the console. How you choose to configure Qlab for sound needs is beyond the scope of this tutorial. A Qlab computer, a network adaptor (most modern Macs have no network ports), a network cable and a console. The process of getting everything to work was just weird enough that I feel it could use a tutorial. Instead, we should use OSC and the network cables we always have to bring with us anyways. However, I cannot escape that there is seemingly no reason to get a midi interface for the console to transmit from plus the right length midi cable to plug into the audio interface for the sound (or video) computer. I remember the 80s, so MIDI has long been familiar to me. The last time I did this I was triggering a media server and I did it with MIDI. I have an illusionist tour that has very simple sound needs, so I’m having EOS trigger QLab for the sound cues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |