I did sleep, and it was like waking up and finding a big ol' present under the tree this morning. You the man! microphones_on_off is very cool. Full of shiny new things I've not seen before . Thanks a million David. You've been beyond helpful.

Cool. Thanks again.

Thanks for all your help. I'm getting rejection with route as well, except on #4. It seems like that's the core of the problem, and that all the routing stuff is probably fine. Whichever instance of Microphone is created last seems to be the one that works. I've re-read the chapter on encapsulation from Miller Puckett's PD book, plus the section on flossmanuals, and I can't see anything different from what I'm doing. I keep feeling like I'm going to have one of those elusive missing semicolon moments, only it never comes.

Hmm. It seems OSCroute is rejecting the messages as well. I even tried making it /microphone$1 as you suggested. No dice. I have however just discovered something interesting. I wondered why it seemed to match for #2, so I created two more instances of Microphone, and now it's matching on #4, but not #2. This seems like some sort of bizarre scope issue, but surely $1 etc. are locally scoped for abstractions, or else they wouldn't be of much use, right?

Oops, I didn't realise I'd missed an 's'. Well spotted! Sadly that didn't seem to stop routeOSC rejecting the messages. Everything is now 'microphone', and the message looks good at both print objects. I even tried removing the 0/1 on the end of the message, and sending the message manually. Still rejected. The only way I can get it to match is to get rid of the $'s and use the actual strings. Could this be something weird with the routeOSC implementation?

Thanks for the help. I tried your suggestion, but routeOSC seemed to just reject the messages. They're of the format:

/microphone/[#] [0 or 1]

I've attached some cut down versions of the patches I'm using to demonstrate/test. testOSC.pd is the parent patch. Hopefully I'm not just being dense here, but I've tried so many things that I'm starting to feel a little boggled .

Patches.zip

Hi all,

I'm a little stuck trying to use routeOSC within an abstraction, with one of the abstraction parameters as a routeOSC filter.

Basically each abstraction object is given a number in the parent patch, e.g. Microphone 1, so if I print $1 within the abstraction on loadbang, I get 1 in this case.

In the abstraction patch itself, I've got a routeOSC objects like so:

[routeOSC /microphones]
|
|
[routeOSC /$1]

I'm trying to have it match only the microphone related to a particular instance, but from what I'm seeing it doesn't seem to do what I want (it seems to only be matching /2 for whatever reason). Any ideas what I'm doing wrong or how to go about it? I'm fairly new to PD, so I'm not sure I've quite got my head around messages and dollar signs yet.

Thanks,

Alex.