One of the the church's that I work for regularly uses ProPresenter to control their lyrics/ graphics along with an ETC Ion for lighting. They often have problems staffing the lighting position for normal Sunday services yet want to be able to create some different lighting looks through out the service. With the most recent versions of the Eos software ETC added OSC command functionality to the console allowing just about anything to be remotely triggered. OSC (Open Sound Control) is somewhat of a successor to the original MIDI protocol that sends data over network connections in a much more user readable format for editing. Through ETC's implementation of the protocol you can get an Eos/ Ion console to remotely complete almost any action you could while sitting at the console. The full guide to what ETC has allowed users to do with OSC is available in their latest Show Control User Guide.
With the added communication module ProPresenter has the ability to send MIDI notes when a slide is advanced making it possible to control external gear. Unfortunately, the Ion is not able to receive MIDI notes and perform actions with them, only MIDI commands. However, the implementation of OSC commands it is possible to make these MIDI notes be useful. A software called OSCulator can run on the same computer as ProPresenter and translate the MIDI notes to OSC commands and send them to the Ion. This unlocks the ability for ProPresenter to control the Ion without having a separate lighting operator present.
In discussions with the worship leader, we were able to figure out the best way for the console and ProPresenter to work together based on their normal usage. For most services only a few looks are needed which could be programmed at any point through out the week and submasters for various areas are brought up throughout the service. We wanted to be able to make this without the need for an extra volunteer operator. To implement this, we decided to use the person running video to help control the the lighting. When setting this up we decided to use the main cue list to control the scenic elements and background while the band, house, and other key lights were still controlled by subs as was being done previously. In order to make this work we decided to make cues 1-200 recallable with MIDI notes and subs 1-10 controllable at 0%, 25%, 50%, 75%, and Full. The decision behind the cue number rather than the "GO" button was that it enabled the slides to be mixed around and not cause a ton of problems if things happened out of order. In the end we did include the GO and BACK functionalities in case we needed to run point cues through ProPresenter control. One setback that I found was that I was unable to control the timing of subs with the OSC sub commands so I ended up using macro commands to set the sub levels even though the console lacks moving faders.
The rest of this post is a how to guide. It is more geared towards ProPresenter but references this guide from the ETC forums by Paul Toben which is referring to QLab which I would suggest following for the initial setup for the computer and console. I'll stick mostly to the ProPresenter side with some OSCulator info thrown in.
- ETC Eos based console running v2.3 or later
- Mac OSX based computer
- Possibly a second NIC card for connecting to your lighting console depending on how the computer is set up
- ProPresenter with either the MIDI or Full Communications Module
- Ensure OSCulator and ProPresenter with the MIDI/ Communications Module are installed on your computer
- Complete the network setup as described in the Paul Toben guide
- In ProPresenter create a MIDI device by following the instructions on pages 126 & 127 of the ProPresenter user guide
- I forgot to grab a screen shot of this but its fairly simple
- I chose to name my device OSCulator which appears in the rest of the guide
- Select a slide and add a not
- Right click and select “Add Cue> Communication Cue> OSCulator> MIDI Note On”
- Select the channel and note and send
- An item should appear in OSCulator
- This is only the channel which you will want to expand to give yourself more option
- Highlight the note/ pitch section and "Edit> Demux"
- Keep changing the notes in ProPresenter and more lines should appear
- If you change to another channel you'll have to Demux again
- Keep sending notes to OSCulator until you're satisfied
- You'll get something like this without the Event Type and Values filled in
- Set the Event type to OSC Routing
- Set the value based on what you would like by clicking on the blank field
- This will bring up the routing table
- Click the add new address section and type in the desired values in the new window
- Go to Cue #= /eos/cue/(list)/(cue)/fire
- This executes with the time applied to the cue, not the standard goto cue time
- Go= /eos/key/go_0
- Back= /eos/key/stop
- Macro #= /eos/macro/#/fire
- For subs my macro is "Sub 1 @ Full Time 3 Enter", running in the background mode
- In my file I used macros 151-200 because that was available in the base show fil
- Test sending note
- The box by the given note should flash when the command is sent from ProPresenter
- On the console if you open the Diagnostics Tab (Tab 99) and set it to display incoming OSC you should see the items incomin
- If you see the notes incoming and you see the message coming in make sure the velocity on ProPresenter is 1 or greater
- If nothing is coming in check your network setup
- Once you are sure setup is done you may want to lock OSCulator through "Routing>Lock Routing"
Hopefully this is helpful in getting you started using ProPresenter and OSC. Here is a ZIP file containing the various manuals, a usage guide once set everything is set up, and my OSCulator file withe cues 1-200 mapped and subs 1-10 mapped as well.