Great, thanks for the clear and concise explanation. I thought I must have been wrong :)
M > - 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. > > Martin > > -- Marco Donnarumma New Media + Sonic Arts Practitioner, Performer, Teacher, Director. ACE, Sound Design MSc by Research (ongoing) The University of Edinburgh, UK ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Portfolio: http://marcodonnarumma.com Research: http://res.marcodonnarumma.com | http://www.thesaddj.com | http://www.flxer.net Director: http://www.liveperformersmeeting.net
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list