hi,
it's not my intent to start an aesthetic war, just i have mental pain with chords going straight across from bottom to top, especially since you cannot readily see which direction the data flows, so i started to use a lot of pvar associations in max. believe me, i use a lot of encapsulation and abstractions. i'll have a look at "sl"
ciao, -sciss-
Do you Yahoo!? Yahoo! Personals: It's free to check out our great singles! http://au.personals.yahoo.com
Hallo, Item State hat gesagt: // Item State wrote:
it's not my intent to start an aesthetic war, just i have mental pain with chords going straight across from bottom to top, especially since you cannot readily see which direction the data flows, so i started to use a lot of pvar associations in max.
Okay, I now looked up, what pvar/pv is, in the Max Reference manual. For storing single float values you can use the [value] object with $0 as in: [value $0-x].
For storing lists you could use a little abstraction as attached. It will not automatically get new values if you create a new [pvar] like the original or like value does, but it may still be of use to clean up patches a bit.
A third aproach is to use a [table] for storing lists of floats. Get them with tabread, set them with tabwrite or [s tablename].
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
Personally, I find it hard to follow when the patch coords are routed
thru some convoluted path, and merged together. There are occasional
times where a segmented patch coord would help to make things clearer,
but I find that those situations can almost always be solved by adding
a [float], [bang], etc. to route the coord.
.hc
On Feb 13, 2006, at 1:45 PM, Item State wrote:
hi,
it's not my intent to start an aesthetic war, just i have mental pain with chords going straight across from bottom to top, especially since you cannot readily see which direction the data flows, so i started to use a lot of pvar associations in max. believe me, i use a lot of encapsulation and abstractions. i'll have a look at "sl"
ciao, -sciss-
____________________________________________________ Do you Yahoo!? Yahoo! Personals: It's free to check out our great singles! http://au.personals.yahoo.com
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
"Terrorism is not an enemy. It cannot be defeated. It's a tactic.
It's about as sensible to say we declare war on night attacks and
expect we're going to win that war. We're not going to win the war on
terrorism."
- retired U.S. Army general,
William Odom
Hans-Christoph Steiner wrote:
Personally, I find it hard to follow when the patch coords are routed
thru some convoluted path, and merged together. There are occasional
times where a segmented patch coord would help to make things clearer, but I find that those situations can almost always be solved by adding a [float], [bang], etc. to route the coord.
I agree that segmented cords can be more confusing than straight ones when they overlap. I also find that multi-coloured patch cords can make a patch a lot easier to follow.
Martin
On Tue, 14 Feb 2006, Item State wrote:
abstractions. i'll have a look at "sl"
sl and rl stand for sendlocal and receivelocal, two externals I wrote at a time when there was no $0 mechanism available.
Now that you can use $0 there is probably no need for them anymore.
Günter
ciao, -sciss-
Do you Yahoo!? Yahoo! Personals: It's free to check out our great singles! http://au.personals.yahoo.com
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
geiger wrote:
sl and rl stand for sendlocal and receivelocal, two externals I wrote at a time when there was no $0 mechanism available.
Now that you can use $0 there is probably no need for them anymore.
Günter
i like the idea of [sl], [rl] because it makes a subpatch "local" like abstractions with $0-sends/receives it does,but with the advantage that i can change a few things in a single subpatch without to changing all copies of this subpatch. sl/rl makes a subpatch more like a "subclass".
[~~~] Moritz
I can't explain it, but sometimes $0 didn't work for me, I think as the name of an array maybe? I wanted to have multiple instances of a sampler subpatch, and each had an array inside, but I had to rename each instance manually, because pd didn't seem to understand the $0 in this case.
~David
geiger wrote:
sl and rl stand for sendlocal and receivelocal, two externals I wrote at a time when there was no $0 mechanism available.
Now that you can use $0 there is probably no need for them anymore.
Günter
Hallo!
I can't explain it, but sometimes $0 didn't work for me, I think as the name of an array maybe? I wanted to have multiple instances of a sampler subpatch, and each had an array inside, but I had to rename each instance manually, because pd didn't seem to understand the $0 in this case.
I think this was a bug long time ago ... but of course you have to start in the arrayname with $0 - e.g. $0-name !
LG Georg
hi
cyborgk@nocturnalnoize.com wrote:
I can't explain it, but sometimes $0 didn't work for me, I think as the name of an array maybe? I wanted to have multiple instances of a sampler subpatch, and each had an array inside, but I had to rename each instance manually, because pd didn't seem to understand the $0 in this case.
~David
i think that was with older versions of pd, < 0.36 or so, i'm not sure. but it should work now.
roman
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
-
cyborgk＠nocturnalnoize.com -
Frank Barknecht -
geiger -
Georg Holzmann -
Hans-Christoph Steiner -
Item State -
Martin Peach -
moritz -
Roman Haefeli