Make sure OSC RX and TX are enabled, and enter under OSC UDP RX Port the port number 8000 (or whatever you have chosen). Go to Setup>System Settings>Show Control>OSC. It’s arbitrary, and you can use any number port you wish as long as EOS and Qlab agree.īack in EOS, sign in as Primary (keep in mind you can only send OSC triggers to the Primary on any network). I went with 8000 since that’s what many other people do. Name it, choose the network port/adapter then list the Destination IP address for your console, and finally what port you wish to use for your OSC messages.
#Qlab midi trigger Patch#
Add a second Patch for your EOS console by clicking New Patch in the upper right hand corner. In Qlab, click on the cog in the lower right hand corner. If you needed to change anything at all, press Accept at the bottom of the screen. Make sure UDP Strings and OSC is turned on for the network port you are using. In EOS, go to the shell, Settings>Network.
Since I’m a lighting person, and EOS is my primary console, I use 10.101.100.2 for my console and 10.101.50.111 for my Qlab computer with a subnet of 255.255.0.0. You need compatible IP addresses and subnet masks between the two. We will be using the EOS Family Level 4 Complete show file from so we don’t have to invest any time writing cues. You could even run both programs, EOS and Qlab, on the same computer using 127.0.0.1 as your IP, but I won’t be specifying instructions for that. I highly recommend using a simple unmanaged switch, since it has solved a variety of networking mysteries in my life as a programmer, but I don’t think it is required. Qlab version 4.3 or above is needed and I will be using EOS software 3.0.2 today. Since fewer and fewer people even know what midi is these days, we will be using a networking to join our two systems and we will be using OSC as our protocol. Triggering cues between sound and lighting used to only be done with midi.
#Qlab midi trigger how to#
If not- check back in next week when I do a tutorial on how to get timecode out of Qlab that you can then set up your own triggers inside EOS for cues. If that sounds like something you want, read on. It is especially for people who like to look at a music file wave form and place lighting triggers directly onto it to see where the beats fall. This tutorial is for those who are doing performances that use pre-recorded music (like a dance recital) and have equal access to both EOS and Qlab during tech rehearsals, since adjustments in triggering the lighting cues will need to be made in Qlab. It seems a fairly common desire to have EOS triggered by Qlab, but sometimes programmers get intimidated.
0 kommentar(er)
