#Q lab 4 windows#
Note: If you're running Eos ETCnomad on a laptop, you will have to set the IP address in Windows or macOS, rather than in Eos. That's everything set in the shell, so hit Accept and head back into Primary. If you're connecting to sound using your port 2, you may want to turn off sACN and Artnet for this port, to avoid spamming the sound network with level data.įor this article, we'll assume we're using Port 1 on an Eos Ti, with an IP address of 10.101.92.101. Ensure that UDP Strings & OSC is ticked for the port you want to use. Once this is set, scroll down to the Interface Protocols section. If you need to change it from the default, do so - a reboot will be required. The IP address for each port is set at the top of this window. To edit the network settings on a console, exit to the shell, and go to Settings > Network. This may depend who has the fewest devices to readdress! Of course, if you don't use your console's network port (because you use DMX only), you can follow option 1 above. If your console has 1 network port, you will need to come to an arrangement so that the console and the QLab computer end up on the same subnet.If your console has 2 network ports (see below), use the second port to connect to the sound department, and choose an (unused!) IP address in the same subnet as their QLab computer.
#Q lab 4 full#
If you have full control over all devices on the network (including the sound computer), or the sound department also use the 10.101.x.x range, it is easiest to stick with these defaults, and ensure the IP address of the QLab computer is in the same range.īut often, someone else is running sound, and they may have their own network, with their own IP address scheme. Consoles with 2 network ports (Windows 7 or 10 consoles) use the .x range for their second port by default. Consoles with 1 network port (Windows XP consoles and ETCnomad Puck) use a default IP address in the 10.101.x.x range. This is all you need to know for a basic network setup between Eos and QLab - for more detail, see the et cetera blog post on IP addresses and subnets.ĮTC uses default IP addresses per product type, as detailed in this article. Another device with the IP address 192.168.1.55 could not talk to them. In the example above, the two Eos family consoles can talk to each other because they share the 10.101.
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.
#Q lab 4 software#
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. OSC is an open protocol which allows the sending and receiving of human-readable messages between sound, lighting and other entertainment technology systems.
0 kommentar(er)
