#Qlab show how to
#Qlab show Patch

I found the tutorial by Mark on using OSC with QLab (which was great), but I'm still unclear about MIDI. QLab 3 Show Control: Projects for Live Performances & Installations is a project-based book on QLab software covering sound, video, and show control. Would QLab send STOP signals when cues are stopped, which I could use to trigger the deactivation of scenes in Isadora?įinally, if that is the case and MIDI is an option that provides more granular control, I would hope to get some help in setting it up. For corporate video programming on Qlab in NYC, you’d find it hard to get me in the room for less than 70-80/hr with a 10 hour minimum. Push for 10hr minimums, but perhaps give an option of 5hr minimum with OT rate starting at the 6th hour. I did some more research and saw that MIDI can be used instead of OSC for communication. Personally I would charge closer to 100-150/hr.

#Qlab show how to

For example, it's easy in an Isadora Control Panel to have an OFF button that deactivates everything, but QLab is just a linear list and I don't know how to properly integrate something like that. My intuition was to create an empty scene that just has a bunch of Deactivate Scene actors to make everything dark, but I don't know how that can be integrated into the linear structure of QLab.

#Qlab show Patch

If the Stage Manager stops all cues to reset or go back, my Isadora patch won't know. I'm trying to figure out the best way to be able to stop everything from QLab smoothly as needed. Automate building and targeting fadeins and fadeouts for lightning fast slideshow generation.

I suppose jumping back to a previous cue will be simple enough since the current scene will deactivate, although I'll have to figure out some logic for deactivating the internal auto-follows. I use this hotkey all the time and it is my biggest time saver. However, while building the patch I realized that I may run into issues during our tech rehearsals with stopping/resetting/going back/etc. These would be treated as a single cue from QLab since they auto-follow in Isadora.)

I'm designing video for a theatre show and could use some guidance on best practices for integrating QLab to trigger scenes in Isadora.īased on my initial research, my plan was to make a 'Controller' scene that would always be set to Active, and then use the OSC messages from QLab to trigger Jump actors to travel between scenes as needed. (I should also mention that there are a few instances where I use Trigger Delays and Activate Scene actors for internal cues, layering multiple scenes to aachivebackground and foreground videos.