Hi Attached patch exhibits different behavior depending on where and how [routeOSC] was built. It seems pre-built binaries from the Debian repositories insert an empty symbol (see attached patch) in the output, but only on amd64 and armhf (Raspberry Pi), but not i386. Also, when I compile routeOSC myself on those platforms (amd64, armhf), the result shows the expected behavior.
routeOSC from Pd-extended works as expected on all platforms. It looks to me as if the way the external is compiled is responsible for the differences. Among others I'm in charge of the package pd-osc in the Debian repository, but I don't have a clue how to track such a problem. That is why I am asking the list. Any clues? How likely is it that other externals are not working exactly the same on different platforms? I'm more concerned about 'not exactly' than about 'not at all'. Roman
#N canvas 572 292 688 284 10; #X obj 21 134 list; #X obj 21 156 list length; #X msg 21 48 /bla/blu 99; #X obj 21 70 osc/routeOSC /bla/blu; #X obj 21 179 sel 1 2; #X obj 21 22 loadbang; #X obj 21 99 t a a; #X obj 69 99 print OUTPUT; #X obj 21 250 print EXPECTED; #X msg 21 208 YES; #X msg 53 208 NO (Are you on Debian amd64?); #X text 190 64 On Raspbian (armhf) and Debian (amd64) \, an empty symbol is prepended by [routeOSC]; #X connect 0 0 1 0; #X connect 1 0 4 0; #X connect 2 0 3 0; #X connect 3 0 6 0; #X connect 4 0 9 0; #X connect 4 1 10 0; #X connect 5 0 2 0; #X connect 6 0 0 0; #X connect 6 1 7 0; #X connect 9 0 8 0; #X connect 10 0 8 0;
_______________________________________________ Pd-dev mailing list [email protected] http://lists.puredata.info/listinfo/pd-dev
