Is someone on the list has a working setup of non-mixer ADN osc under arch ?

> I have not tried 0.28 yet. 0.26 should work. The message "protocol '(null)' 
> not supported" is strange. You say you're running remotely via ssh -X. If so, 
> then try running regular non-mixer (not noui). In the module parameter editor 
> you should see the correct osc path in the info bar when you hover the mouse 
> over the control you want to affect. Is it as you expected? 

Nice shot, i hadn't noticed that info bar, when looking for a way to confirm 
the need of %20.... So yes all the printed path are what expected.

there may be no relation with this other strange issue, but we never know :
I can make jack connections with the gui using the small plugs. When i make a 
first connection, i can see the source/destination name appear under the plug.
Then if i add more connection to the same destination port, the jack connection 
is made, but the source/destination names are not added to the list, as i've 
seen in some screenshots.

This second issue is probably more related to the NTK lib. May the NTK lib have 
an influence on OSC ? ... i think no but just trying to find a way. 

after more tests, non-mixer received all (well-formed) osc messages with path 
/signal/*
did i mention it is segfaulting with the hello message ?

[non-mixer] ../nonlib/OSC/Endpoint.C:315 handle_hello(): Got hello from astrux
[non-mixer] ../nonlib/OSC/Endpoint.C:1113 add_peer(): Adding peer astrux @ 
localhost...
liblo: protocol '(null)' not supported by this version
[non-mixer] ../nonlib/OSC/Endpoint.C:1130 scan_peer(): Scanning peer astrux
Segmentation fault (core dumped)

some old similar issue with sooperlooper using liblo too : 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596392

Raphaël

Reply via email to