hello again, forget about the jack connections not listed... it works. But i found another something. After creating a setup, i changed a strip name. In the debug messages i can see that non is renaming all the osc paths. But in the GUI some plugins still have the previous name in the info bar. Maybe it can help track down some osc problem. This one is looking like a bug.
see some sort of screenshot : http://troll.ws/image/c61d44ad Raphaël Le 28 janv. 2014 à 18:55, J. Liles a écrit : > > > > On Tue, Jan 28, 2014 at 4:02 AM, Raphaël Mouneyres <[email protected]> > wrote: > 2014-01-28, rosea grammostola <[email protected]>: > > http://non.tuxfamily.org/wiki/BugReports > > > > obviously missed that page... > So after adding debug mode to non-mixer, i do have more messages at > startup. But still can't get my strip osc messages to be considered, > even if there is some progress : The osc server is actually running > and receiving osc messages as i've sent some commands found in the > nonlib/OSC/Endpoint.C file, and non-mixer is printing some > information. > Here it is : > > [seijitsu@astrux mixers]$ non-mixer-noui --instance main --osc-port 8000 > hand/ & > [1] 29359 > [seijitsu@astrux mixers]$ The Non-Mixer 1.2.0 -- Copyright (c) > 2008-2013 Jonathan Moore Liles > [non-mixer-noui] ../mixer/src/main.C:199 main(): Using OSC port main > [non-mixer-noui] ../mixer/src/main.C:195 main(): Using OSC port 8000 > [non-mixer-noui] ../nonlib/OSC/Endpoint.C:202 init(): Creating OSC server > [non-mixer-noui] ../mixer/src/Plugin_Module.C:257 discover_thread(): > Discovering plugins in the background > OSC=osc.udp://astrux.localdomain:8000/ > [non-mixer-noui] ../mixer/src/main.C:291 main(): Waiting for plugins... > [non-mixer-noui] ../nonlib/OSC/Endpoint.C:1148 osc_thread(): OSC Thread > running > ...loading project > ... connecting jack clients > [non-mixer-noui] ../mixer/src/Project.C:288 open(): Loaded project "hand/" > [non-mixer-noui] ../mixer/src/main.C:314 main(): Not Running UI... > ... > [seijitsu@astrux mixers]$ oscsend astrux.localdomain 8000 > "/strip/mic/Gain/Gain%20(dB)" f "-3.0" > [seijitsu@astrux mixers]$ > [seijitsu@astrux mixers]$ oscsend astrux.localdomain 8000 "/signal/list" f > "1" > [non-mixer-noui] ../nonlib/OSC/Endpoint.C:733 osc_signal_lister(): > Listing signals. > [seijitsu@astrux mixers]$ > ... > [seijitsu@astrux mixers]$ oscsend localhost 8000 "/signal/hello" ss "one" > "two" > [non-mixer-noui] ../nonlib/OSC/Endpoint.C:315 handle_hello(): Got hello from > one > [non-mixer-noui] ../nonlib/OSC/Endpoint.C:1113 add_peer(): Adding peer > one @ two... > liblo: protocol '(null)' not supported by this version > [non-mixer-noui] ../nonlib/OSC/Endpoint.C:1130 scan_peer(): Scanning peer one > [seijitsu@astrux mixers]$ > > so i checked my liblo version : > [seijitsu@astrux lib]$ pacman -Qs liblo > local/liblo 1:0.26-2 > A lightweight OSC (Open Sound Control) implementation > > it not the latest one (0.28), may it have influence ? > I have not installed gdb yet on the system, and debugging the program > may take some time. > > Let me know if the above new information can help understand why the > strip messages don't reach non engine. > > thanks > Raphaël > > > 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?
