11/13/2023 0 Comments Ion controlling qlab oscYou may wish to remove the triggers for the cues inside the Group, or keep them in place. For example, to set selected cues to not loop and hold on their last frame, you would put the OSC cues for these two functions into a Timeline Group cue (start-all Group cue,) then assign a hotkey or MIDI trigger to that Group. You can combine these in Group cues and give the Group cue a hotkey to build up more complex actions. Here’s whats included in the example workspace: If you put all your editing hotkey cues in a separate cue list, you can simply disarm that list when you are not programming. Remember that batch commands are potentially dangerous, particularly when they can be triggered by simple key presses. ![]() Generally, it’s best to keep all your hotkey cues together in a separate cue list so that they don’t get confused for cues that are part of your performance. You can copy and paste any cues you might find useful into your own workspaces. The example workspace contains many useful OSC commands that will work in this way. The Network cue (OSC cue) will start, and the selected cue(s) will be set to loop. We can now select all the cues which we want to loop and hit ⇧L. The example workspace has a MIDI trigger listening for a note 60, note on with any velocity. If you have a remote control device that sends MIDI notes, you could also set a MIDI trigger for the cue. ![]() L is generally already in use, as a shortcut for the built-in command “load”, so we might use ⇧L (shift-L). To do this, we assign a hotkey trigger to the Network cue (OSC cue.) This is done in the Basics tab of the inspector in QLab 3, or the Triggers tab of the inspector in QLab 4 or QLab 5. So what we need to be able to do is trigger the cue while we have one or more other cues selected. Of course, if we run this cue as it’s shown in the screen shot, nothing will happen, because the only cue selected is the Network cue (OSC cue) itself. Here’s a screen shot of our OSC cue that will set the selected cues to loops: If you are typing an OSC string from memory then the general rule is, all letters are lower case except the first letter of any words that are joined to another without a space, like ‘infiniteLoop’ where only the ‘L’ is capitalized. IMPORTANT: OSC is case-sensitive, so you must enter OSC with the capital letters in the correct place. In the text field, type /cue/selected/infiniteLoop 1 to switch the loop on or /cue/selected/infiniteLoop 0 to switch the loop off.For QLab 3 or 4: in the Settings tab of the inspector, set the message type to “custom OSC message.” In QLab 5, the message type is defined by the patch.Create a Network cue (in QLab 3, it’s called an OSC cue.).To set up a hotkey which will set the selected cue to loop, we do the following: QLab 5 defaults to requiring a passcode for OSC messages, which you can configure here: In QLab 3, setting up that patch looks like this: By default, QLab workspaces have OSC patch 1 set as a “loopback”, i.e the OSC is sent to the Mac QLab is running on, which has a special address, localhost, and to the port number which QLab listens for OSC on, port 53000. But you can also send OSC messages from QLab to QLab itself. In QLab, OSC is often used to communicate with other pieces of equipment over a network, such as an ETC Ion or a Meyer Galaxy. You can create hotkeys to invoke any OSC command in the dictionary this example will focus on looping. The OSC dictionary for QLab found in the QLab manual: ![]() You can use similar OSC cues on hotkeys to control a huge range of parameters in QLab. QLab 4 and 5 allow some cue parameters to be edited on multiple cues simultaneously, and looping is indeed one of them, but the hotkey method is still useful because it can be invoked at any time, and you don’t have to be looking at the correct tab of the inspector to use them. Once you’ve created these cues, you can assign hotkeys to them which makes them behave almost like built-in functions just like copy ( ⌘C) and paste ( ⌘V). In QLab 3 and later, now you can also use OSC (Open Sound Control) which can be a bit easier to set up. ![]() In QLab 2, this could be done with a Script cue. But what if you frequently have large numbers of cues you want to set to loop? It is possible to create a cue that will can perform this action on all the cues that are selected. For instance, QLab 3 only allows you to turn looping on or off for one Audio cue at a time, using the checkbox in the Time and Loops tab of the inspector. One of the great things about QLab is that its capabilities can be extended beyond those included in the program.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |