OSC-Input - Problems also with 4.10.1

[pogay]

Hello again

We have some installation with QLC 4.8.5 and OSC-Input was never a major problem.
OSC is traceable with tcpdump -i eth0 udp -X, and the "hands" can be seen on input/output screen.

Recently I had problems with OSC in QLCPLus 4.9 and 4.10m which I didn't investigate further.
But there was recently an announcement of a bugfix -> 20151021 concerning a OSC problem which I try just at the moment.
All t I can say now, is the my 4.8.5. shows the hands, and the 4.10.1. doesn't do anything (but receives the UDP-Calls).

QLC 4.10.1
there are two lines (sees to be changed)
OSC: 127:0.0.1
OSC: 192.168.0.252 (doesn't make a difference when I make the cross here).

(in 4.8.5)
OSC 1; OSC-Network1 (for universe 1)
OSC 2: OSC-Network2



Capture of UDP
14:40:47.469470 IP (tos 0x0, ttl 64, id 7457, offset 0, flags [DF], proto UDP (17), length 44)
192.168.0.108.42826 > 192.168.0.252.7770: [udp sum ok] UDP, length 16
0x0000: 4500 002c 1d21 4000 4011 9ae7 c0a8 006c E..,.!@.@......l
0x0010: c0a8 00fc a74a 1e5a 0018 1278 2f66 696c .....J.Z...x/fil
0x0020: 6d2f 3300 2c66 0000 3f80 0000 55b0 m/3.,f..?...U.


My driver, which usally sends to two QLC 4.8.5. maschines, which is in "production" and works.
on wheezy-machine:

client = OSCClient()
client2 = OSCClient()
client.connect( ( srvIP, int(srvPort)) )
client2.connect( ( srvIP2, int(srvPort)) )

client.send( OSCMessage("/film/"+bez, [1.0] ) )
client2.send( OSCMessage("/film/"+bez, [1.0] ) )


regards
Patrick

[mcallegari]

OSC lines changed in 4.9.0. I have written it in the release announcement.

Questions:
- do you load a project on your Raspberry ? If so, how does the <InputOutputMap> section of the qxw looks like ?
- I see you are using the standard static IP 192.168.0.252. Have you tried with a dynamic IP ?
- has the trace above been captured on the RPi itself ?
- if you turn on the Rpi and don't load any project, go to IO panel, select the 192.168.0.x line, and start sending some OSC data, do you see the joystick blinking ?

[pogay]

Dear Massimo
thanks for the fast reply

I did a new test -
PI1 .0.108 (sendOSC) - PI2-qlc .0.110 (dhcp)

the tcpdump I take on the Pi QLC-4.10
19:48:37.433172 IP 192.168.0.108.40308 > 192.168.0.110.7770: UDP, length 16
0x0000: 4500 002c 4ba2 4000 4011 6cf4 c0a8 006c
0x0010: c0a8 006e 9d74 1e5a 0018 1adc 2f66 696c
0x0020: 6d2f 3500 2c66 0000 3f80 0000 77ad


the section is: (as I take an "old Show").
<InputOutputMap>
<Universe Name="Universe 1" ID="0" Passthrough="False">
<Input Plugin="OSC" Line="0" Profile="None"/>
<Output Plugin="DMX USB" Line="0"/>
</Universe>
<Universe Name="Universe 2" ID="1" Passthrough="False"/>
<Universe Name="Universe 3" ID="2" Passthrough="False"/>
<Universe Name="Universe 4" ID="3" Passthrough="False"/>
</InputOutputMap>

with and without show, I don't see the joystick on the 0.110 (qlc 4.10.1 git)
On a second QLCPlus I see definitly the joystick.

I understand, that the show might be not compatible, but qlcplus should show the joystick.
May be my osc messages are not compatible... could try "touchosc"

[mcallegari]

I think this is wrong:

Code: Select all

<Input Plugin="OSC" Line="0" Profile="None"/>

On the Raspberry Pi (and PC too) line "0" is 127.0.0.1 (loopback)
You don't have to use that.
Try to use line="1"

[pogay]

thanks for the hint

my OSC works now!
I checked the ports aswell...
The problem was that I sent a message to 7770 ( 7700 seems to be the default value in 4.10.1)
(did I change accidentally the default port?)

thanks a lot for the support! and the great software.
Patrick

[pogay]

For the following problem concerning my OSC-message I searched quite a while
At the time I was installing my jessie, the original pyosc sources were not available,

So I installed different available pyosc sources.
there seem to be different version of pyosc.
originally I used from an example (worked).:
client.send( OSCMessage("/movie/"+Nr, [1.0] ) ) # UDP message 16 o.k. second parm no data I use, was just the example

there seems to be a version of pyosc where OSCMessage takes only on param.
client.send( OSCMessage("/movie/"+Nr) # UDP message 12 =>QLCPlus didn't recognize

#I corrected to this (added the second part just for having the length).
# and it worked qlcplus now shows the joystick
msg = OSCMessage("/movie/"+Nr)
msg.append([1.0]) <- just for getting the length, without this dummy stmt, qlcplus doesn't show the joystick
client.send(msg)

maybe QLCPLus needs a minimal length of UDP-Call.
As the UDP was traced in tcpdump I don't think it was a filter issue.