3 Mar
2013
3 Mar
'13
12:45 a.m.
On Sat, 02 Mar 2013 13:12:12 +0100
Christoph Kuhr <christoph.kuhr(a)web.de> wrote:
On 02.03.2013 13:00,
linux-audio-user-request(a)lists.linuxaudio.org
wrote:
hmmm... strange.
Did you try the different versions of the OSC server that are in pyOSC?
Hiho, I've only worked with the python2
version, but I may have an
idea where things go wrong. On Wed, 27 Feb 2013 15:54:42 +0100
Christoph Kuhr <christoph.kuhr(a)web.de> wrote:
Hi, thanks for the advice, but i already tried that one out earlier
without success. I have a python3 app, that calls a class
OSC_Communication.
address = localhost, port = 9001
Try for an address 0.0.0.0 instead, then the
program will listen on
any interface, and not just localhost.
It may be that the program you are using to send is using the
IP-address connected to one of your physical interfaces as a targer,
rather than the loopback (localhost) address.
In a sense this difference allows you to make your program more
secure, by ignoring messages coming from outside of the machine, but
unfortunately, not all other OSC-enabled programs allow you control
over how they send the messages.
sincerely,
Marije I switched to pyliblo, which works like a charm!
the disadvantage with that lib I found is that it is not so easy for
crossplatform distribution of the code, since you need a compiled liblo
to link to.
sincerely,
Marije