•    Actively manage departmental technology inventory of computers, monitors, peripherals, cables, adapters, etc.
•    Makes recommendations on technology to purchase based on current and future needs
•    Installs projectors with their related computer systems and networking every semester based on show needs
•    Trains projection designers/operators how to use rigs and occasionally gives QLab 4 training
•    Moves lighting and sound consoles for technical rehearsals and establishes temporary networking for those systems
•    Sets up lighting clients for designers and stage managers
•    Sets up and trains operators on networking show controls such as OSC and MIDI Timecode
•    Occasionally helps professors with IT tasks such as video calls, software installation, cloud storage, etc. 

Highligh: EOS Show Controller using OCS
Task: Have and ETC Ion trigger cues for a QLab 4 projection and sound rig simultaneously
For UB's Dance Production in Fall 2020, we were filming the pieces to be streamed later. Because of this, the design mentor wanted all of the show control systems to be triggered from one machine to limit error during a narrow filming window.  
The Tool that made it work
After some research I found a tool called OSCRouter that allows a computer to translate the OCS command coming over a network from an EOS console (Link to OCSRouter: 

Screenshot of OCSRouter

Rudimentary Signal Path made by TJ

After this I ran into an issue; At the time, unlike QLab, EOS only supported sending OCS to one IP Address. Since the Sound and Projections systems are different machines I wasn't able to get both of them to "listen" to the Ion at the same time. The workaround for this became to have the Ion send OCS to the Sound Computer, have the Sound Computer listen to command via OCSRouter, then have QLab on the Sound Computer sending OCS to the Projection Computer and the Projection Computer taking cues from that. It was a bit of a workaround that may have been able to be solved with clever subnet masking however based on the time constraint this was the simple, easier to understand solution.

I also made a rudimentary signal path to show how the systems were connected.
Back to Top