Re: [QLab] OSC control of LXConsole?

[Dave "luckydave" Memory]

On Friday, May 31, 2013 at 11:29 AM, technical.to...@googlemail.com wrote:

Hi 

i am trying to control LXConsole with OSC messages from Qlab All on the same Macbook 

i am using the same commands that i use in touchosc on an ipad but not getting any response.

i have tried using my computers ip address and localhost, with both the port i use on the ipad (9000) and 53000.

any help would be gratefully received  

In OSC Settings, set up a patch sending to localhost on port 9000. Port 53000 is QLab's listening port, so sending messages there will work for QLab, but not other software that's listening on a different port. In your OSC cues, send a raw message, and whatever you use in TouchOSC should work. If you're already doing all of this and it's not working, maybe more details will help.

-- 

luck...@figure53.com

[technical.to...@googlemail.com]

On Friday, May 31, 2013 4:29:03 PM UTC+1, technical.to...@googlemail.com wrote:

Hi 

i am trying to control LXConsole with OSC messages from Qlab All on the same Macbook 

i am using the same commands that i use in touchosc on an ipad but not getting any response.

i have tried using my computers ip address and localhost, with both the port i use on the ipad (9000) and 53000.

any help would be gratefully received  

Matt

[technical.to...@googlemail.com]

Hi 

i have tried all that 

attached are screen shots of the set up ?

[Dave "luckydave" Memory]

On Friday, May 31, 2013 at 12:19 PM, technical.to...@googlemail.com wrote:

Hi 

i have tried all that 

attached are screen shots of the set up ?

Hm. Could be that you've capitalized "localhost". Try using a lower case "l", or if that doesn't work, try 127.0.0.1 (localhost is an alias to that IP address).

-- 

luck...@figure53.com 

[technical.to...@googlemail.com]

no luck with either of those ?

[Dave "luckydave" Memory]

On Friday, May 31, 2013 at 12:47 PM, technical.to...@googlemail.com wrote:

no luck with either of those ?

I don't know what to tell you. I'm hoping there's something missing in the OSC message, or something similar. I tried to check the documentation for LXConsole, but I have to download it to get to the documentation, and I have to register with my email address to download it, and I'm not interested in registering on their site.

I looked a little bit at the forums, and it appears they have a pretty robust OSC implementation, and they seem very helpful, so that may be the next place to look.

-- 

luck...@figure53.com 

[Mark Nizer]

My experience is that you must select your IP address in the OSC IP Address field. ANY doesn't work

Mark Nizer

When the Entertainment Matters

http://nizer.com

ma...@nizer.com

--
--
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 the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 
<LXconsole.tiff><Que.tiff><Seetings.tiff>

[technical.to...@googlemail.com]

Thank you for your help
I have asked the same questions on the Lx console forum so I will report back if here anything
Matt

[technical.to...@googlemail.com]

Below is response from LXConsole forum
For other users Benefit.

First, the OSC connection in LXConsole's preferences need to match the one in QLab's workspace settings.

If you have no active network connections, you can use the internal loopback connection, 127.0.0.1. (This should also work if you do have an active connection.) By default, QLab has the connection "localhost" and port 53000. If you have any other active network connections, change this to 127.0.0.1 and you can leave the port at 53000. The, in LXConsole's OSC preferences tab, choose 127.0.0.1 from the popup list. And, change the port to 53000 to match QLab.

There is one additional thing about sending OSC from QLab to LXConsole that is not obvious. OSC messages are comprised of an address followed by data. The way that TouchOSC works is that when a button is pressed, it sends a message with the OSC address for that button (Set in TouchOSCEditor) AND the data has a value of 1. This is important because when the button is released, TouchOSC sends an OSC message with that address and a value of 0.

LXConsole will respond to a command with an address such as /cmd.lxconsole/GO only when the associated data is greater than 0. You can probably see why: When used with TouchOSC, a "Go" button sends a message when it is pressed and when it is released. So, if not for the distinguishing data, that would cause two GO messages to be executed. (This is similar to the way that MIDI notes must have a non-zero velocity for LXConsole to react to them.)

QLab is capable of sending data along with the address. It is specified by leaving a space after the address in the OSC message field. To send LXConsole a GO command, the OSC message set in QLab would be "/cmd.lxconsole/GO 1" Note that this does not mean "cue 1 go"! The 1 is simply the positive data value necessary for LXConsole to react to the message. BTW, to tell LXConsole "cue 1 go", the OSC message field in QLab would read "/cmd.lxconsole/GO:1" and "cue 2.5 go" would be "/cmd.lxconsole/GO:2.5" (The data test only applies to GO, HOLD and STOP)

[Johan]

Works!