Hello,

I have an audio abstraction that is using [f $0] to define various components of each unique instance. I have multiple instances loaded and for some reason, when I initialize one of these abstractions, the unique id assigned by Pd changes for all instances. This is a nightmare because I am using unique instances of [catch] / [throw] to send audio around using the [set( argument.

Does anyone have any idea why this might be happening?

Ricky

can you post an abstraction where this happens?

Sure. I've attached an example abstraction and host patch for the instances. There are two problems here:

1. When I call a second instance of the abstraction, it creates an additional outlet. I suspect that is an issue with my ordering in the abstraction.

2. When I call multiple instances, the unique [f $0] id changes in previous instances, which screws up previous relationships

dyn-patch-ex.pd
main.pd

I want to be able to create multiple grains (granular synthesis) modules that don't rely on a predetermined dac~ configuration. Rather, I'd like to create a unique outlet and receive the audio in a main patch for spatialization.

So, every time I create an instance of a grain, it sends audio for each voice to a main patch. This is proving to be a problem that I thought I could overcome by using broadcast messaging.

Currently, I'm trying to do this using multiple (unique) [throw] and [catch] as send and receive are not configurable. If anyone knows of any simpler ways to do this, please let me know.

@ricky I'm not sure at all if this will help, sorry. But a long long time ago I tried this solution by Thomas Grill called UPP:
http://grrrr.org/research/software/upp/

...
The Universal Polyphonic Player (short UPP) is an infrastructure for all kinds of polyphonic events – be it note-like events, other generated sounds or short grains in granular synthesis. The strengths of the system are a modular, easily extendible design, almost unlimited polyphony, ease of control, DSP load scaling and sample-accurate timing.
...

Cheers~

@EEight Hey! Thanks for the link. I will have a look. Here's the issue in context (see the attached .zip). It seems that using the broadcast message [s pd-patchname~.pd] will affect all instances, which is a real shame. I hope I'm wrong!

gram_test.zip