![]() ![]() While building projections can be incredibly impressive, and they’re usually created and displayed at sizes well above TV and even cinema. There are a variety of techniques available to do this. 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.Īfter three sold-out shows, I’d say it was worth it. When producing large scale video projections it’s important to establish some type of preview, to guage how the content will look when projected. 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.Īdditionally, 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). What I needed was on the second (at timecode) OSC fades. 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. 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. I was building out slowdanger’s – empathy Machine show and needed a way to automate various visual changes over the 1hr+ performance. I’ll add more to this page if I make them. I put two quick tutorials together for anyone interested. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |