![]() Important: Spaces are not permitted in OSC addresses, so if you are using OSC to control your workspace, it’s a good idea to avoid spaces in cue numbers. A cue’s ID can be discovered using the AppleScript property uniqueID Cue ID is a unique identifier for each cue which never changes, even if you change the cue’s name and number. These commands have the structure /cue/ with the cue ID of the cue you want to target. There are also a variety of commands that can be directed at cues themselves. You can find a list of application level OSC messages in the Application Messages section of QLab’s OSC dictionary. There are also several application level messages which interact with QLab itself, “above” the workspace level. If you are using a device or program which sends specific OSC messages that you want to associate with workspace level events such as and panic, you can do that in Workspace Settings → Controls → OSC. You can find a list of workspace level OSC messages in the Workspace Messages section of QLab’s OSC dictionary. ![]() So sending /go to QLab from an external device will cause the exact same thing to happen as sitting down in front of QLab and clicking on the GO button with the mouse. When QLab receives these messages, it behaves exactly as though the corresponding button, menu item, or keyboard shortcut occurred within QLab. QLab accepts commands like /go, /panic, and /save, which are referred to as workspace level messages because they are directed at a workspace. The long and short of it is that devices must be on the same network, on the same subnet, and use IP addresses that permit them to communicate with each other. A good, but rather dry, introduction to setting up devices on a network can be found here. The sending device must be on the same network, and both the Mac running QLab and the other device must be configured correctly to share network traffic. QLab accepts incoming OSC messages via TCP and UDP over a local network. You can use programs like Max, Medialon Manager, and TouchOSC, or hardware like ETC’s EOS family to send messages that exist in QLab 5’s OSC dictionary.Īlternately, if your software or hardware does not allow you to program your own messages, you can use the OSC controls in Workspace Settings → Controls to capture your device’s OSC messages, and map them to several of QLab’s workspace-level commands like, Panic, Load, and so on. Understanding OSCĪll software or devices which support OSC have their own dictionary of commands. OSC is a great way to control QLab from other software and hardware because it’s relatively simple to set up, requires no specialized hardware, and uses networking infrastructure that is often either already in place or easy to implement. QLab has extensive support for the Open Sound Control protocol, a network communication standard for computers and multimedia devices. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |