Hello there,

i would like to share two abstractions which allow you to create and control many instances of the same oscillator voice. The [polyx] object has two creation arguments, the number of voices and the name of the voice abstraction. The [sweepOsc] abstraction contains a comlex oscillator with a frequency ramp and an envelope.

The polyx-help shows how you can address single voices with lists or i.e. generate a chord from 3 notes containing 10 harmonics each.

If you want the [polyx] to use any of your abstractions you need to take care of the send/receive arguments, since they are desgined for the [sweepOsc] abstraction.

This method can be used for any kind of abstraction from arrays to voices, filters or whatever you might need hundreds of (the loading of the objects though will definitely take a while).

Any comments appreciated.

gn8, kq

http://www.pdpatchrepo.info/hurleur/polyx.zip

Hi all,

since nobody comments on my idea i would really like to get some advice on future posts.

Please help me to improve my presentation.
Is this idea to basic to post about it?
Was something like that posted already so it could be considered a double post?

I had the feeling it is a generic way to get an "array of objects" like it is used in any other programming language, but with way less effort than something like the [polysynth] object with the wrapper and several sub-patch levels.

thanks, kq

That's a good idea and a nice patch indeed Don't take it personally if nobody comments, it happens ! My only concern with [polyx] is how you deal with saving the patch. When doing dynamic patching, i always found myself ending each modification with [dirty 0< in order to avoid Pd to ask you whether you want to save or not the changes in your abstraction.

Hi dwan,

thanks for the input. If you change the number of voices in [polyx] via numberbox on the right inlet, you can change the number of abstractions loaded without invoking a modification in any patch, but i'm not sure why actually. [polyx] itself doesn't get modified by changing the content of the [pd $0-voices].

Since you need to modify [polyx] for use with different abstractions, it should be possible to use it as a template and then stop worrying about the saving issue.
I thought about adding the possibility to change the abstraction you want to load also, but this won't work because the list in [polyx] is specifically designed for my [sweepOsc] abstraction.

greetings from a snowy alps lodge, kq