The positive Side-effect is, that no Driver for OSX or iOS is needed. My tests showed up, that the connection of a USB-Keyboard is the fastet way for executing the Cues. The Main Focus was to have a fast, save, reliable and easy to use Controller. I programmed it to act as USB Keyboard, Audio and even Midi-Interface. The Controller using the Teensy Platform from Paul Stoffregen by PJRC, because it is very good and has a lot of functions ready. To have some flexibility, there are 3 Mode buttons that switch the USB Commands and the Hardware Midi Output Commands. The Push-Buttons are for GO, STOP ALL (Panic), Select previous Cue, Select next Cue, Volume Up and Down. So you get an All in One Solution especially when using GO-Button with iPad or iPhone. It has a built in Stereo Audio Output with Line Level, running on 44.1kHz. It has a Serial Midi Output, to control a Backup-Player or other Devices. It can control the Software via 6 Push-buttons and 3 Mode Switch. LetsGO is a professional developed and testet device, which is used all day in different by Theaters and Artist. (Similar to Devies Like Audio-Ape or AirTurn, but with more functions integrated) The Functionality goes up to USB and MIDI Cue Control, Wireless-Remote, USB-Audio and MIDI-Interface! This Project let you easy build USB Cue Controller, with integrated Audio and MIDI-Interface for using with QLAB®, GO-Button® and Ableton© Live®. This was a revelation as much as it was a disappointment because it makes quick programming an absolute pain in the ass…īut it might inform you guys about this a bit more.Advanced Remote CUE Controller for QLAB®, GO-Button® and Ableton© Live® MSC-messages are strings of hexadecimal numbers that tell the receiver what to do with the info inside the message, in the GO-message you’ll see what I mean…į0, 7F - says hey this is a system exclusive message and opens the message.Ġ0 - is the device ID, default set to 0 in Qlab, but you can change this yourself.Ġ2 - tells the device it’s a MSC command (MIDI Show Control).Ġ1 - tells the device it’s a Lighting/General commandĪfter the GO command (01) you could implement the cue number and cue list to tell Qlab to start a specific cue, and this is where it gets a bit confusing… because we’re dealing with hexadecimal numbers in 8 bit single bytes (single message length) we’ll have to divide the numbers in single digits and their hexadecimal ASCII equivalents starting from 30h to 39h to resemble 0 to 9… (go with it for now, you’ll see)Ī cue number 3 would have to be called 33 in the string…Ī cue numer 12 would have to be called 31,32 in the string…Ī cue number 2.4 would have to be called 32,2E,34 in the string…Ī cue number 13.2 in group/sequence 4 would have to be called 31,33,2E,32,00,34 in the string (00 to devide cue from cue list) To really get what’s going on in a MIDI Show Control message I’ll have to bore you with a very short explanation (or that’s what I’m aiming for). When using the above MIDI Show Control (MSC) Strings to talk to Qlab, you can use the System Exclusive Data format to direct Qlab to the corresponding cue, inside the corresponding cue-list or group. To get Qlab to respond to midi Show Control strings including specific cue’s, even in cue groups or Sequences as they would like to call it, some of your brain will have to melt when calculating the Hexadecimal 30h to 39h ascii …. So to add to, and (slightly) correct the above list of usable MIDI strings in your Dlive…Īlthough I got really far I would like to find out how to link cue numbers to the strings so I can have scenes trigger certain ques, and the stop all function is just a blunt stop…. I’ve been building a Qlab Go button (and then some) and was searching for MSC/Sysex commands to get Qlab to respond to, and I was surprised to find just what I was looking for in the Dlive Forums!! I’ve recently aquired a C3500 and a CDM48 rack, and I will be using Qlab and MIDI on a regular basis… I would like to add to this topic with my own findings…
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |