Hi everyone,

I'm new to this forum so I hope I got the right one . I'm fiddling with Pd since a couple of weeks and am now in the process of building a 16x16 routing patchbay (I didn't find anything like that via search, but maybe I didn't search well enough ). Everything is going well but it seems I'm hitting a wall with the following:

Inside the patch I have a number of canvas objects which I plan to use to label the patchbay. All of them have receives ala $0-1h-label, $0-2h-label, $0-1v-label and so on. Now I figured out how to set one individual label sending one message [1h-label string( - however, for 32labels that's a tad bit too cumbersome, so I'd like to handle this using a message of the form:

[ 1h-label string; 2h-label string; 3h-label string ... 16h-label string(

But I have no idea how to process such a message so that I end up with individual [; $0->foo string( messages (I know, I could as well just make the abstraction use an $1 argument and set the receives to $1-h1-label - but I figured there must be a way). I suppose I have to somehow loop through the individual messages but I don't know how.

I'd be glad about any pointers into which direction I should proceed.

Thanks in advance !

I've attached the abstraction (it's not finished yet, audio routing etc. works but I want to add some Midi/OSC handling as well).

http://www.pdpatchrepo.info/hurleur/patchbay16x16.pd

I don't know other than the [; $1-$2 label $3( solution you already have, what to suggest, I don't think I understand the question.

Do you want to have lots of message boxes with predetermined send addresses, to which maybe a [route] object would route the incoming message to the correct message box?

@arif said:

I don't know other than the [; $1-$2 label $3( solution you already have, what to suggest, I don't think I understand the question.[/quote]
I try to clarify. At the moment the receives of the canvas objects look like $0-1h-label. I'm using $0 throughout the whole abstraction for all sends/receives. I want to be able to pass a long message of the form:

[1h-label label1;
2h-label label2;
3h-label label3;
...
16h-label label4(

into one inlet of the abstraction. Now, inside the abstraction I would have to translate all those parts of this long message to single [$0-1h-label label label1( messages to set the respective canvas label (prepending $0 to all parts of the incoming message). I'm looking for a more abstract way to handle this so I don't have to create a massive amount of "routes", but instead just handle this one incoming long message and dispatch it, i.e. like foreach(incoming_msg as part) { set label $0-[label] to label }.

I think your current setup is okay. Try using commas instead semi-colons for the incoming message. If you use semi-colons, everything after the first one won't be sent out the outlet of the message box. It will just look for a [receive 2h-label], [receive 3h-label], etc. and send the arguments there. Commas just treat it as a series of messages.