![]() ![]() In a show situation I’d be running a redundant system for MA, and a redundant system for qLab. That’s why I love MA so much - it’s so simple to run hot backups. The above would fire cue number 2 in qLab.įor more info on grandMA3's sendOSC keyword check out the MA3 help page here: Īnd for more detail on the qLab OSC Dictionary, check out: Where To From Here So to fire cue 2, you would use the following syntax in the command line: And the cue number is obviously the cue number that matches in qLab. The s refers to how the message is formatted, in this case s means string. Breaking this down into the comma breaks, /go refers to the type of command we’re sending (a go command). After that it’s the OSC syntax that qLab requires to trigger the cue. sendOSC 1 is referring to the line number we set up in the In & Out page - hence 1 as we’re sending to qLab using line 1. Step 5 - Sending the Control Message in onPCįrom here it’s all work in the command line. Just enough so that you can see that the cue is firing. Step 4 - Create Cues in qLabĬreate a few different cues with cue numbers in qLab - this is just so we can make sure it’s working, so they don’t need to be anything specific. You also want to match the settings I have for Receive, Send, ReceiveCmd, SendCmd, EchoInput, and EchoOutput (all of which should default to Yes). As for the receive port, it’s the same deal but with the port qLab listens to (53001). I have also listed the IP Address of the qLab machine, to ensure the OSC messages are getting sent to the correct machine.įor the Send port, ensure this matches the port that qLab listens to (53000). Line 1 is the Send port, and Line 2 is the Receive port. Also make sure Enable Output and Enable Input are switched on.įrom here we’ll want to add two new OSC lines. ![]() Make sure this is in the same subnet as the onPC and qLab machines, in my case 192.168.0.0/24. Once you’re in In & Out, click on OSC on the left hand side.įirst thing to check is the Preferred IP.Luckily, it’s actually really straight forward. This is the part that I got stuck on - how to properly configure the MA3 OSC settings. Check that Use OSC Controls is switched on, the incoming port is 53000, and the outgoing port is set to 53001. Head to Workspace Settings ( Window > Workspace Settings) and navigate to OSC Controls. QLab should come pre-configured for OSC control, but just in case, and to make sure the default settings still match, we’ll just check a few things. Whilst this step isn’t strictly required, for me it’s one less thing that can go wrong, and makes things simpler down the track. This means setting a static IP address for both machines on the same subnet. First thing’s first - make sure you have configured your network settings correctly. I am using two separate computers - a laptop running MA3 onPC (Windows 10 Pro), and a Mac running qLab (Mac Mini). After scouring many different forums and web pages, I finally stumbled across the solution, and what a simple solution it was! I was kicking myself that it took so long to discover, so I wanted to share the steps with you to help get you up and running, and work towards an integrated show control system! Step 1 - Configuring Your Computers And since the software was released, I tried time and time again to get it working, but struggled as OSC wasn’t very well documented in the MA world yet. When I learnt of grandMA3 supporting OSC, it opened up a world of possibilities for me. Whilst it was ridiculously easy to set up (see my other post here), it seemed a bit redundant running an ethernet network with both machines on it, as well as MIDI, and on occasion even SMPTE timecode. It was clunky, but I would connect the grandMA2 onPC system via a USB MIDI adapter, which fed into the Mac running qLab with another USB MIDI adapter. In the MA2 days I would achieve this via MIDI control. Whenever I’m designing a show, I always try to integrate and automate as many functions as possible, so it’s less work for whoever is operating the show. Whilst each discipline needs to be independent, having one master control system that can trigger cues between each system, perfectly in time, is the perfect end goal for me. Those who know me can tell you I’ve always been a huge advocate for the integration of all audio visual control systems, especially over a network. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |