Qlab MIDI CC to OSC /fader/ message conversion?

[Johnny Boy]

Hi there!

I have a question regarding sending a MIDI cc message from Qlab to OSC.

Is there any type of conversion program that anyone has used?

Essentially I'd like to send a MIDI cc say value 0 to 127 over 5 seconds creating a fade up.

Then on the OSC device have that now converted /fader/ command move the fader up slowly instead of having it be an interger and jump to the value between 0 and 1.

Anyone ever had luck with this?

OSCulator? 

I will say straight off that I have never coded so whenever I try out a piece of software I get into trouble real quick!

Plus - the equipment we have doesn't accept MIDI cc. Only Program changes...

Cheers! J :)

[Drew Schmidt]

Sure thing.

OSCulator is your program

• In Qlab ...
• Open QLab and OSCulator. In qlab settings, now you can make sure that OSCulator shows up in your MIDI patch
• Create your MIDI cue with your necessary settings and with OSCulator as the MIDI Destination. Hit GO
• In OSCulator
  
• Now you should see your MIDI message in a list in OSCulator
• For this "event", select "OSC Routing" from the event type. This will create an OSC message when this MIDI message is received
• Next click on "Value" and create a new value the "OSC Routing" window will pop up
  (Click on "Parameters" to open it back up if you close it)
• In the OSCulator OSC Routing window
• You'll first need to specify your target OSC device (i.e. your fader) in the format of "osc://[IP]:[PORT]" (i.e. osc.udp://10.59.25.175:53001)
• Then you need to create a routing table. When you receive this MIDI message, what OSC Address do you want it to be converted to?
• From the # column, choose the number that represents the target you created
• Double click the Rewrite cell
• Here's where you specify your OSC address (i.e. /fader/1)
• Then in the arguments specify "arg[0]" for the first argument being passed (the CC Control Value). You could even click on the drop down and specify that it should be passed as a float (a number)
• Hit close and try it out in Qlab

To help monitor, you can pop open the Quick Look window

Hope that helps!

[John Conlon]

Great stuff Drew!

I followed all the steps. Very nearly had it as I used TouchOSC on an iPad as a test.

I could see it getting OSC in from a MIDI cue.

I guess the bit I'm missing is the conversion from 0 to 127 as a Midi CC to the 0 to 1 value in OSC.

I include a screen cap to explain.

In OSCulator I set the rewrite address and the arg[0] but no trinagle came up.

Am I missing a step?

Many thanks again Drew as this would really solve our problems!

Cheers, J :)

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/2gqodd9ALzg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[John Conlon]

Also, just a query. How do you set the outgoing OSC port in OSCulator?

I just selected the iPad in the Targets section.

But when I set the OSC URL manually it says 'Invalid format: Port must be between 1 and 65535

[John Conlon]

Success!!!

I just didn't drag the arg[0] to the arguments field.

Did it, the triangle appeared. I then set as a float and BOOM!

My God I'm so happy!

As we say in Sweden - tusen tack! ( 1000 thank you!)

Drew - (as they said in the film Apollo 13) you, sir, are a steely-eyed missile man

[Johnny Boy]

One last thing!

It's all happy and working by sending OSC to the ipad as a test but when I go to hook up to our mixing desk it seems it doesn't show up in the gear menu.

What is the correct syntax to write in the OSC URL section?

Cheers again! J :)

[Drew Schmidt]

When you say gear menu, you mean the gear dropdown under Targets? 

This is a list of devices that are posting their "OSC availability" if you will to the network. Some applications and devices (i.e. Qlab) don't do that or at least don't show up on the list. This just mean you'll have to enter the data in manually.

So in your mixing desk, figure out what the IP address is as well as receiving port (what kind of desk are you using?). Then you can enter this data in manually in the following format

osc://{ip address}:{incoming port}    So you might double click the target spot and type osc://10.3.3.254:7000

Hopefully that's what you mean!

[Johnny Boy]

Drew!

It totally works!

Thanks ever so much for your help!

I'm so happy right now - the hours of programming snapshots is over. Phew...

Cheers! J :)

[Drew Schmidt]

No problem!

One thing we didn't walk about was the scalings page (View > Flip to Scalings Page). This will let you scale the output value based on the input value. so you can say 

Midi CC Value 0 = OSC Value 0

Midi CC Value 127 = OSC Value 1024

(Min / Max  Input / Output)

And it'll scale everything in between.

Not sure what your mixing desk is looking for, but something like the X32 is a 0-1024 input range, not a 0-1. 

[Johnny Boy]

Hi Drew,

When I go to open the Flip to Scaling Page, nothing happens...?

[Drew Schmidt]

It should change your list of incoming messages to a different version of a spreadsheet where the header bar lists Message, In Min, In Max, Out Min, Out Max etc. It doesn't open a new window or anything. 

[Johnny Boy]

Hi Drew!
When I say that nothing happens I mean the window doesn't open up.
I'll try a new clean test to see if that works.
Cheers J

[Johnny Boy]

Hi again Drew - sorry I'm an twat.

It came up in the same window and worked.