[PD] suggestion... or question

[B. Bogart]

Hey,

I use an abstraction [dir2abstractionArray] in pixelTANGO for the pixel
effects stuff, which makes a dynamic array of abstractions that are
listed in a directory. Dynamic patching gets more ugly with many many
objects, but I've not needed to do manual connections for some time.

Most of the time I use [constructor] which was once in the pmpd stuff,
maybe its in pixelTANGO, and therefore pd-extended too, I'm not sure.
Anyhow its just a abstraction that makes arrays of abstractions.

dir2abstractionArray does this for abstractions listed in a directory,
and also brokers the communication. You give it an index, and it routes
two inlets and two outlets to the abstraction selected by the index.

I'm sure there are better repeat/nqpoly ways of doing this stuff, at
least arrays of abstractons, but I've not gotten my head around those
quite yet.

.b.

hard off wrote:
> i used to spend a LOT of time renaming multiple send / recieve pairs,
> making giant [route a b c d e f ....z] objects, etc....then connecting
> hundreds of patch cords by hand.
> 
> but i generally don't do that at all anymore.  there are usually other ways.
> 
> for example:
> 
> *store your data in tables and use tabread to access it
> 
> *use qlist, or even better [msgfile] to access lots of data
> 
> *
> [pack f f]
> |
> [;
> $1-send $2<
> 
> 
> however:  >>what do you think of a new type of object, that can act
> like a subpatch
> (or abstraction) does, and provide yet multiple inlets for controlling N
> instances of that subpatch?
> is this (already) possible to do?
> perhaps can be made with an external...?<<
> 
> 
> i think it might be handy, and i think you could make an abstraction
> that does this for you.
> 
> have a think.  good luck.
> 
> _______________________________________________
> PD-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
>