Qlab to x32 osc

[Megadeal Events]

I have my behringer x32 set up to control qlab via midi commands and usb.

My question is, is there a way to do it the other way around.

For instance play a "play off queue" for an actor and have qlab send an osc command back to the x32 to mute the channel for his mic etc.

If so would someone have the /*/* command for this as I've read the manual on osc but it's like reading Urdu to me.

Also can midi and osc be used simultaneously.

Thanks

Carl.

[Drew Schmidt]

Can QLab send OSC to the X32? Absolutely

Set a static IP on the X32 and link that up into QLab (Port 10023).

Then follow this protocol guide to assist you (which is sounds like you've looked at).

http://www.behringer.com/assets/X32_OSC_Remote_Protocol.pdf

One gotcha is that if there are more than nine channels (i.e. 32 channels, but only 8 busses) you have to put a 0 in front of single digit channels. Meaning to mute channel two, you would make a new OSC cue with a custom message that would like like this:

/ch/02/mix/on 0

And to turn it back on: 
/ch/02/mix/on 1

If it helps you decipher the protocol guide, these commands came from page 10 ( /ch/[01..32]/mix/on ) which then states that it's an enum (ON,OFF) which means you need to send it a 1 or a 0. ( /ch/[01..32]/mix/fader ) level [0.0...1.0 (+10 dB), 1024]  would mean that to set a level, you need to give a value between 0 and 1024. On page 14 you'll find the settings for the main fader. 

Hope that helps!

As for OSC and MIDI simultaneously, I don't see why not. I've never done both at the same time, but don't see why not. 

[Megadeal Events]

That helps a lot. Thanks so much.

What I'm seeing though is when I drag a osc cue into qlab and put that

/ch/09/mix/on 1

As the command, qlab is reporting a red x with "missing qlab cue number"

[Chris Ashworth]

Hi Carl,

Sounds like your cue is set to be a QLab OSC message, which is a special case for sending OSC messages formatted specifically to send to other QLab machines.

You can switch it to a Custom OSC message to send arbitrary messages to other destinations.

-C

[luckydave]

On Sunday, December 28, 2014 at 5:43 AM, Megadeal Events wrote:

What I'm seeing though is when I drag a osc cue into qlab and put that

/ch/09/mix/on 1

As the command, qlab is reporting a red x with "missing qlab cue number"

You're entering that in the cue number field for a QLab OSC message, which would only work to control QLab. Change it to a custom OSC message, and you can put any old OSC command in. The QLab messages are shortcuts to some of the more common OSC methods for controlling QLab.

-- 

luck...@figure53.com

[Carl.]

You are my heroes.

Sorted!

Thanks.

[SmithAudio]

Hi, I'm currently having the same issue; all of my patching and OSC Cue are as written here; nor I don't have a red X next to my cue. I wondered if it was my physical connections? I'm running Qlab 3 - MOTU sound card via firewire - Midi in & out of the X32.

I am also running midi to cue scenes; which IS working. Can you run midi and Bosc in one cue stack? Sorry if this doesn't make any sense. Any Help Much appreciated