Sound f/x custom hardware for ergonomic programming of QLab?

Ken Porter

New Member
Greetings all.
I’ve wandered through some conversations about controlling QLab with hotkeys, OSC, and so forth, but here’s what I’m not finding. My (new) dream is to set up a customizable piece of hardware, similar to a big X-Keys device, which would be an ergonomic leap toward making the programming of QLab much more efficient. i.e. replacing a lot of pointing and clicking with task-specific button presses & perhaps a jog/shuttle wheel to rapidly affect timings, levels, what-have-you. I’ve asked the X-Keys folks, but while they’re great at making text macros feed a USB port, they don’t make their devices talk MIDI, nor do they send their results out a network port to reach some UDP or OSC listener.

Then I get to thinking I need some software solution for either the Mac or my networked Windows laptop, which could intercept communication from a specific USB device (in the X-Keys example) and just send it along down a network port… but alas, I can’t find a software solution that would keep some exclusivity, such that it would be the ONLY software to pay attention to what the X-Keys device might generate...
Then I come back to the concept that … Wait a sec - I can’t be the first person to want a big set of custom buttons to help efficiently program a piece of industry standard software… So, I search again, and find stupidly-expensive controls that are used for video editing, or live-event video switching/fun. And they don’t mention how they communicate, or how, if at all, the commands they send might be customizable… Or I find things that talk to a DAW, which I guess is closer, but it’s still not customizable, and who has the time to reverse engineer something that’s not ideal to begin with?

From what I see, the library of OSC commands that QLab can respond to is pretty extensive. And having a few available on some other complicated device to tell QLab what to do now and then seems completely feasible. But I want that x 100. I’ve always found pressing shortcut keys on a keyboard to be far more efficient than hunting and pecking with a mouse. Now I want more immediate access to all the controls that there aren’t enough hotkeys for. I want a jog & shuttle device to tweak pre-wait times. (Maybe at some point I’ll want a display of the QLab UDP text responses, but not now.)

So I guess my question is this:
Has anyone previously had success in the realm of some magic box, sitting next to your computer keyboard, that could be used to make, alter, tweak, rearrange cues significantly faster than typical keyboard & mouse methods?
Given how much time we spend programming, I’m a bit surprised that this doesn’t exist yet, or that it’s hidden so well from the interwebs.

Thoughts?
- K
 
The amount of programming that would go into that would be rather daunting. I'd be interested to see how many Qlab users even go beyond simple playback and dive into stuff that deep. Of course people do, but I bet its less than 10%. The keyboard shortcuts Qlab offers are rather limited. What I personally think would be better is to either open up way more options for shortcuts that you can map to the X-Key and/or support some kind of basic DAW controller.

I've been looking for a way to add a "scrub" feature to my button box for awhile... and its just not there.
 
Its a pretty common occurrence to be rehearsing a piece, have to pause, go back 20 seconds or so, then start again. So, current active cue.

it certainly is! but unless you're working in dance, it's equally common to have several cues running at once, so i was just wondering if you had a specific workflow in mind about how you'd want to tell your control hardware which of those cues you'd want to scrub.
 
it certainly is! but unless you're working in dance, it's equally common to have several cues running at once, so i was just wondering if you had a specific workflow in mind about how you'd want to tell your control hardware which of those cues you'd want to scrub.
Well, my snappy answer to that :)-)) is "if I have a stack of cues running at once, I can *pause* them all at the same time, and then restart them, right?" So there is, at least to some degree, a framing for scrubbing them all at the same time too (which seems the obvious answer to your actual question)...
 
hello jay

with respect, what’s obvious to one person may be obscure to another, and may be irrelevant to a third. forgive me if i misread your tone, but i find it slightly combative and for no reason that i can see.

i am genuinely interested in the answer to the questions i ask precisely because i think the answers are not obvious. QLab is a very flexible tool, and many people use it very differently. for this reason, it is difficult to design dedicated programming hardware for QLab, since the chief virtue of such hardware would be precision and speed, which are usually derived from the hardware being designed to the workflow.

i asked @Footer whether he would want to scrub all active cues, the most recently started cue, or the selected cue. he didn’t answer yet, but your answer appears to be “all active cues,” so that’s one data point.

if i were going to use such a feature, given the way that i design shows and the way i program QLab, i would want to be able to be more granular than that. so there are two answers.

i would love to hear others!
 
Well, my snappy answer to that :)-)) is "if I have a stack of cues running at once, I can *pause* them all at the same time, and then restart them, right?" So there is, at least to some degree, a framing for scrubbing them all at the same time too (which seems the obvious answer to your actual question)...
I would concur. Though variety is a spice of life. It adds complexity, but an option next to the "Scrub wheel" could be. All (Default), most recent now playing, Most recent and all fade/control cues child'ed in, selected cue.

Has this ever been addressed or requested through the Qlab Google group feature request. I love this idea.
 
most recent now playing

i’m so sorry, i do NOT mean to be pedantic, but do you mean “the most recent single cue amongst all that are now playing” or do you mean “all the cues that started with the most recent GO” or something else?

Most recent and all fade/control cues child'ed in,

i would love to know more about what you mean by this! what do you mean by “child’ed in”?

Has this ever been addressed or requested through the Qlab Google group feature request. I love this idea.

well to be clear, there is no official or formal process of making feature requests via the Google group. people make requests and we see them and. keep track of them when we think the requests are plausible, but ultimately we build QLab according to our own internal process.

this thread was originally about hardware for aiding in QLab programming, and we don’t make hardware of course, but in any case there have been occasional requests for scrubbing and those are indeed in our issue tracker.
 

Users who are viewing this thread

Back