I put two quick tutorials together for anyone interested. I’ll add more to this page if I make them.   (Project brief below):



I was building out slowdanger’s – empathy Machine show and needed a way to automate various visual changes over the 1hr+ performance.  The beginning would trigger a preshow look that would loop for as long as it took to seat the entire audience, and then would fade into the main show with more complicated changes and timings.   At first, I explored Veźer, and while I feel pretty confident that Veźer would have worked, a bit of its UI felt clunky for what I needed.

What I needed was on the second (at timecode) OSC fades.  Simple right!, but by default, Qlab doesn’t see its own internal timecode, and unlike Veźer with OSCquery, Qlab needs you to add an extra little #v# at the end of the OSC address otherwise it will send the wrong values to the madmapper sliders.

Additionally, most theatrical spaces love Qlab these days, so making a show file that they would understand is a lot easier than explain the intricacies of LED pixel mapping and custom OpenFrameworks camera apps (by Char Stiles).  The show is simply two “Go” commands, or another way of thinking about it is that the entire show can be run by a single user by hitting the spacebar twice!  <- That’s the power of Qlab.

After three sold-out shows, I’d say it was worth it.

# controlling madmapper from qlab


syntheticlivesc · September 10, 2019 at 2:19 pm

Cool stuff. I think the time code triggering can be super helpful.

    Cornelius Henke · September 10, 2019 at 2:27 pm

    Glad you like it. You can also make a timeline for triggering by grouping items, but I prefer the time “specific” triggers from MTC.

Projection mapping mask V3 debut and process – Projectile Objects · October 28, 2020 at 1:38 pm

[…] OSC over WiFi. (note: Qlab is a preferred standard for the spaces we were working with. Please see this article if you are curious about using Qlab for OSC […]

Comments are closed.