Hi
I'm just interesting about the best way to build a patch. Because, I fight certainly against problems of programmation in pd. I've read this Pd convention : http://www.earcatching.com/pdconv/index.htm
And I think, it's a great idea. An idea of how to do a patch clearly ...
But it can't answer to my present problem : I want to make a kind of array of routing with two parameters (x and y) which could be changed (it would be the best). At the beginning, without reflexions, it looks like this : http://giair.music.free.fr/images/pd/ouaou_PUREDATA.jpg
interesting, no? so?
In my new patch, I'm using the object matrix (Zexy lib) which allow to edit in the array independantly the two parameters.
My questions are :
- Is it possible, an array of three parameters changeable ?
What is the best way for a big numbers of parameters (here, my x values are about 29 elements, my y values are 7 or plus) :
- Do you privilege the direct connections with threads. So, with 29 * 7, its
like a forest of threads, it's impossible to update, and not clear at all. And, it could generate some digital artefacts (**#!!!CLICKS !!). aNd sharing patchs, how it could be possible if after three days we can't understand the patch. And make threads, it's not my favorite job!
3.Do you privilege to creat send and receive objects. It's more clear, but it's 29 * 7, alias 203 objects more in the patchs. In the pd convention, they don't advise this objects (WHY ?)
- Or create unit abstraction which group for this example the 7 parameters.
It's more clear, and more updatable. But it's 29 objects more again !
- And create abstraction of abstraction ?
So for you, what is the best to control a lot of parameters ? jerome
Hallo, abel.jerome@free.fr hat gesagt: // abel.jerome@free.fr wrote:
But it can't answer to my present problem : I want to make a kind of array of routing with two parameters (x and y) which could be changed (it would be the best). At the beginning, without reflexions, it looks like this : http://giair.music.free.fr/images/pd/ouaou_PUREDATA.jpg
Quick remark: If you use the delay object to order the data flow, you should better use a [t b a] object there.
In my new patch, I'm using the object matrix (Zexy lib) which allow to edit in the array independantly the two parameters.
My questions are :
- Is it possible, an array of three parameters changeable ?
I don't see why it shouldn't be.
What is the best way for a big numbers of parameters (here, my x values are about 29 elements, my y values are 7 or plus) :
I would recommend to stay with matrix, it's great for this stuff.
- Do you privilege the direct connections with threads. So, with 29 * 7, its
like a forest of threads, it's impossible to update, and not clear at all. And, it could generate some digital artefacts (**#!!!CLICKS !!). aNd sharing patchs, how it could be possible if after three days we can't understand the patch. And make threads, it's not my favorite job!
3.Do you privilege to creat send and receive objects. It's more clear, but it's 29 * 7, alias 203 objects more in the patchs. In the pd convention, they don't advise this objects (WHY ?)
- Or create unit abstraction which group for this example the 7 parameters.
It's more clear, and more updatable. But it's 29 objects more again !
- And create abstraction of abstraction ?
I favour 4 and 5, but in a slightly different way. Abstractions are there to make often used functionality into a module you can reuse. Attached is a cleaned up version of your first patch which shows this: The selection of (i,j) pairs is abstracted out into an abstraction, xymatch.pd, there. I show how to use this as well in xymatch-help.pd
You will see how this could be adapted to select from a lot of objects. In fact, it's just a quick start to illustrate the approach.
You should try to deeply understand argument passing into abstractions ($1, $2,...) it's a great way to reuse the same abstractions with different variable values.
Ciao
Frank Barknecht _ ______footils.org__
-
abel.jerome＠free.fr -
Frank Barknecht