Affordable Qlab "GO" Button Box

Question... can the top be taken off and rotated 180 so the plugs come off the left side?
Also, would love a USB-C version too...
I took mine apart when I got it because I couldn't help myself. There didn't seem to be anything stopping me from doing so, although I left mine how it was.
 
Question... can the top be taken off and rotated 180 so the plugs come off the left side?
Also, would love a USB-C version too....
Yup, and I can also build it that way if you make a note. I've always been a rack to the right of the console person, so thats the way my brain things but not all people are that way. I don't wire these with such tight tolerances that you should be able to do it with all of them.... but no guarantees.
 
Few updates. Had a customer ask for a light up version, so here is V1 of that. If I can source them I'll probably switch to using the same round buttons I use for the double USB box.... and I'll move the double USB box to light up by default if possible. I have 1 USB micro box left in my inventory. After that sells all boxes going forward will be USB C.
PXL_20230217_154359698.jpg
 
Am I nuts, or should the Go button be a different shape?

I suppose the separation is probably good enough...
Most consoles its the same shape as the rest. Ion Go and hold/back are the same. Express go is exactly the same. Most audio consoles its the same. On the single box the go button feels totally different. On the double box I don't have multiple sourcing for the switch. The light up box will be moving to the same round buttons used on the double.
 
So I’ve got a related question. Can this be set up on a Mac to trigger QLab, while another app is running in the foreground? My specific use would be QLab running my led wall and preview showing the script. I use the keyboard to advance pages on the script, and would love to have this to advance QLab without switching windows for it to work. I currently do this with QLab remote as a work around.
 
So I’ve got a related question. Can this be set up on a Mac to trigger QLab, while another app is running in the foreground? My specific use would be QLab running my led wall and preview showing the script. I use the keyboard to advance pages on the script, and would love to have this to advance QLab without switching windows for it to work. I currently do this with QLab remote as a work around.
Probably not at least in its current state. This box acts as a keyboard emulator, so it needs qlab to be in the foreground. It can run Midi, which I believe qlab will still take midi messages if its not in the foreground. Let me look into what that programming would look like and I'll let you know. I've always avoided it because it requires additional setup in Qlab to make work, but if you are wanting it we certainly can make that happen.
 
So I’ve got a related question. Can this be set up on a Mac to trigger QLab, while another app is running in the foreground? My specific use would be QLab running my led wall and preview showing the script. I use the keyboard to advance pages on the script, and would love to have this to advance QLab without switching windows for it to work. I currently do this with QLab remote as a work around.
Yup, got midi working on it. I'll give it a run in qlab today to make sure everything is good to go and I'll let you know.
 
So I’ve got a related question. Can this be set up on a Mac to trigger QLab, while another app is running in the foreground? My specific use would be QLab running my led wall and preview showing the script. I use the keyboard to advance pages on the script, and would love to have this to advance QLab without switching windows for it to work. I currently do this with QLab remote as a work around.
Hey, it does work and you can run it with qlab minimized. All function (Go, pause, resume, panic/stop all, up, down) all work with midi mappings. Pretty easy to setup and I'll send along a default show file if you don't want to do the mappings yourself.

For the larger world, is this something you would want as an option? I have always avoided it due to the less plug and play nature of it. But, should I add midi as an option?
 
For the larger world, is this something you would want as an option? I have always avoided it due to the less plug and play nature of it. But, should I add midi as an option?
Is it an either or? Or is it a hardware change? I do use MIDI in my setup from my audio board (then qlab can trigger everything else as needed) wouldnt mind just straight USB, but maybe MIDI is just as solid?
I will be ordering one soon...
 
Is it an either or? Or is it a hardware change? I do use MIDI in my setup from my audio board (then qlab can trigger everything else as needed) wouldnt mind just straight USB, but maybe MIDI is just as solid?
I will be ordering one soon...
Ya, its an either or thing, but it is possible to re-flash it yourself so if you wanted to switch later that would be possible. Not something I'd publish on my listing pages but something that could be done. With the code I usually send it with it shows up as a keyboard. With the midi code on it it shows up as a midi device. It would cause conflicts to run them both at the same time on the same bus.
 
True, MSC and OSC have the command embedded so that's what that button does, whereas you can map any note to anything in qlab, so the go button doesn't have to be go if you want it to do something else.
Plus I don't think MSC can move the playhead like you can with notes or keyboard. Could be wrong there.
 
So got mine in the mail while I was in LA for Wrestlemania. Was able to set it up last night, map the midi in qlab, and get it working with no issues. Qlab in the background, script in the foreground. Perfection!
 
Yup, that's working as intended. I source the Arduinos from a few different companies depending on where I can get them. Some of them use red, some use green. Lately I have been getting red. Glad they are working for you!
What arduinos?
 

Users who are viewing this thread

Back