This will also make programming in Qlab easier. Then I can tune the starting and end-point of the parameter using parameter controls in Resolume, use the OSC-command for the dashboard-controls, and always set the fade in Qlab with 0 starting value and 1 end value. composition/layers/1/clips/1/dashboard/link1 What I think I will do in my workflow, is to use the dashboard-controls, and remote-control that from Qlab using 1d fade. Sometimes though it seems that the "speed" settings is a bit tricky to work with, it would be easier if "speed" could be replaced with "fade time". Zoltans idea is good also, it could be simpler to keep as much possible inside Resolume. With the osc-cue in the previous post, the picture will first jump from 1320 to 0, then fade to -320. so if the x-axis of the clip is currently at 1320, after the relative fade the clip will be at 1000. ![]() However, I'm not sure if you understood what I meant by "relative" fades: with this I mean that the cue should tell the picture to move 320 pixels to the left, regardless of what the original position is. 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.Thanks a lot for replies and the video, it explains a lot. 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. |