On 03/12/2012 03:50 PM, Martin Peach wrote: > On 2012-03-12 14:35, Marco Donnarumma wrote: >> hello folks, >> apparently [routeOSC] behaves differently between 42.5 and 43.1 releases >> (I'm aware mrpeach has been updated in between). >> >> I have sliders sending out messages as >> [list /bla/1/blabli 0.437( >> >> with Pd-extended 0.42.5 and the related "older" mrpeach lib, I used to >> route these messages with >> [routeOSC /bla] >> >> I gave it a try with the 0.43.1 and the "new" mrpeach lib, but now I >> need to do >> [route list] >> | >> [routeOSC /bla] >> >> If the [route list] is omitted, [routeOSC] won't output anything, and it >> does not complain. >> >> >> it's really a minor fix for the patch, but I'm a bit confused: >> - was I doing something wrong before? > > I think so. [routeOSC] expects messages whose selector is an OSC path. > If it worked before with list selector it was by accident, because > routeOSC used to have a list method but now there is an anything method. > >> - is this a new feature? > > I suppose it must be new that it ignores lists, but it's not really a > feature. > >> - should [routeOSC] tell me something if it can't parse the message? > > It tells you if the path is not a valid OSC path (no slash) only if > you send it a [verbosity 1( message.
IMHO, [routeOSC] should accept these two as the same thing: [/bla/1/blabli 0.437( [list /bla/1/blabli 0.437( It'll make life easier for a lot of people, and I can't see any disadvantage in that setup. hc _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list