[PD] bug in pd-osc package in Ubuntu utopic

Roman Haefeli reduzent at gmail.com
Fri Nov 7 09:48:54 CET 2014

On Thu, 2014-11-06 at 17:53 +0100, IOhannes m zmölnig wrote:
> On 11/06/2014 11:21 AM, Antoine Villeret wrote:
> > 2014-11-06 10:26 GMT+01:00 IOhannes m zmölnig <zmoelnig at iem.at>:
> > 
> > here is a minimal patch that remonstrate the issue
> > [print bug] prints the right float to console
> > but the number box doesn't understand it...
> > 
> > this is of course with pd-osc-1.0-2 from wheezy
> > current SVN revision works well
> ah i see and can reproduce the problem (my last email used the wrong
> version of [routeOSC], so forget that).
> afair, [routeOSC] used to only be able to route a *single* element from
> the OSC-address. so [routeOSC /a/b] was an illegal string.
> at least that was my understanding (as it didn't work).
> i checked the actual output of the buggy example, and it really sends a
> message with an empty selector ("") followed by the number you were
> expecting.
> so putting an [unpack s f] after the [routeOSC] will give the number on
> the second outlet.
> of course this is really a bug.
> it's a bummer that Debian/jessie was frozen yesterday, which means that
> a minor bug like this won't get fixed for jessie :-(

That is really unlucky. Thanks for reporting this, Antoine. I was
surprised to read about that bug, since I've been working a lot with OSC
classes and never triggered it. I've used [routeOSC] in so many ways,
but obviously not this :-/


More information about the Pd-list mailing list