Is there anything that cannot be routed through a subpatch? I've been told that osc~ and phasor~ objects do not work properly inside a subpatch, but so far all that I've tested have worked fine. I remember encountering strange errors before, though, but I can't remember what they were... Is there any documentation for what can and cannot be used inside a subpatch without errors?

I'm using 0.43.4 extended on windows 7, btw

I've been told that osc~ and phasor~ objects do not work properly inside a subpatch

I never heard of such a thing nor did I find any troubles with these objects inside a subpatch before, and as a matter of fact I never faced a situation in which any object would in a patch but not inside a subpatch - but as always I may be wrong.

Take care,
Gilberto

If there is sthg Pd does incredibly well is routing signals. All you need is creating appropiate inlet~ and outlet~ objects, as well as other objects tilde ~ objects. Read Pd's theory of operation. It's slightly dated but it has all you need to know: http://msp.ucsd.edu/Pd_documentation/x2.htm

@AWilliams
I've run into a problem where I can't use $0 inside multiple copies of subpatches, at least on my system (extended-43.4, OS X). Only in abstractions do $0's become unique. Can anyone validate that?

@rjp9 indeed this behaviour is present in both pd-extended and Pd-l2Ork on my Linux machine.

@rjp9 Do you mean nested subpatches?

$0 is the same for a patch and all it's subpatches.

If subpatches are not enough, you go for abstractions. Or, maybe, you can achieve what you want using global variables, [value], [v].