So, to begin, ensure you have installed or downloaded all the prerequisites. We’ll walk you through these anyway. We’ve only ever tested our scripts on Windows, so your experience may vary on other systems or platforms.

First, head over to the OBS website and download your preferred version of OBS.

After downloading, the next step is to install Python, as the scripts require it to run. OBS supports external scripts but needs Python installed on your system first. During our testing with OBS version 31.0.3, Python 3.11 was the correct version. So head over and download that, making sure you choose the appropriate installer for your system.

Now open OBS and check that the Python installation path is set correctly. In OBS, go to Tools -> Scripts -> Python Settings. If the “Python Install Path” field is empty, locate it using the browse button. For reference, ours was at:

C:/Users/User/AppData/Local/Programs/Python/Python311

You should see a message in OBS like “Loaded Python Version: 3.11”.

Next, we’ll add the scripts, which you can download from this page. Use the + button under the Scripts tab in OBS to add them. The download includes three files:

• obs_eos_osc.py – An ETC Eos script to receive and display current/next cues

• obs_mtc.py – A script to display live MTC from a MIDI source

• obs_qlab_osc.py – A script to receive other OSC text from QLab

All of these files can be loaded into OBS. Once that’s done, set up your environment: enable Eos to output on a chosen port, and match that port in the obs_eos_osc.py script.

Included in the download is a .json file called OBS-Template.JSON. In OBS, go to Scene Collection -> Import, and find this file to import it. After importing, select it from the Scene Collection menu. This gives you a great starting point, with all text elements added and named to receive your production data.

That’s it! The other scripts have descriptions within OBS, and following those should give you a robust setup.

Enjoy! Any questions—don’t hesitate to reach out.