Help with porting example patch to be an abstraction

Reply to Help with porting example patch to be an abstraction on Sun, 16 Jan 2022 03:04:35 GMT

dr_kd — Sun, 16 Jan 2022 03:04:35 GMT

Help with abstraction.

I'm trying to adapt the shepard tone example so that I can run two of them at once with different parameters. .

The issue I'm having is naming things to convert the patch to an abstraction. You can see the highlights where I've moved pitch+ to $0-pitch, and where dropoff+ remains the same. Where I keep the name as per the original everything works fine. Once I move the variable names to $0-pitch the slider functionality is no longer there.

Any idea what I've missed or misunderstood here?

Reply to Help with porting example patch to be an abstraction on Sun, 16 Jan 2022 03:53:41 GMT

bocanegra — Sun, 16 Jan 2022 03:53:41 GMT

The value of $0 is relative to the patch/abstraction. As [shepvoice] is an abstraction, $0 will have a different value in each instance. A way of circumventing this is to pass $0 in the abstractions arguments and invoking it inside the abstraction as $2 (or whichever # argument you reserve for it). Concrete example: [shepvoice 500 $0] and inside [shepvoice]: [r $2-pitch], [r $2-dropoff] etc

Reply to Help with porting example patch to be an abstraction on Sun, 16 Jan 2022 08:21:03 GMT

dr_kd — Sun, 16 Jan 2022 08:21:03 GMT

well that makes total sense (i.e. I can see how $-\d+ expands to a memory address or something, and your explanation makes complete sense. I'll report back once I've given it a try.

Reply to Help with porting example patch to be an abstraction on Sun, 16 Jan 2022 22:44:28 GMT

dr_kd — Sun, 16 Jan 2022 22:44:28 GMT

Thank you, worked beautifully. For the future reference below is how the patch looks now. Next up will be throwing around some LFOs for maximum weirdness.

I think this is because $0 is a pseudo argument that represents something like the memory address of the current abstraction.

Reply to Help with porting example patch to be an abstraction on Mon, 17 Jan 2022 07:17:15 GMT

whale-av — Mon, 17 Jan 2022 07:17:15 GMT

@dr_kd $0 is a real argument assigned to every patch according to the order in which they are created.... so from a fresh start of Pd the first patch opened will have 1001 assigned to $0.
You can find its value for a patch by banging a [$0] object into a number box.
The next patch opened will have a $0 value of 1002......... and each abstraction put in a patch is also a patch....
A sub-patch will have the same value as its mother.
The actual value is of little interest as it can change (for a particular patch) depending on the order in which patches are opened..... so we cannot rely on it.... but $0 is an important variable for building abstractions.
David.