I've been reading obiwannabe's great tutorials, and he keeps using [ead~] where can i get this? Oh and I dont want to install a new version of PD, I'm in the middle of a big project and I don't want to risk some things changing.
thanks,
pete
maybe say which os you're on. i used to have a working version on osx, which i deleted when i refreshed my hard disk, but the only way i could get it going again was to install the new pd-extended.
yes,
sorry i'm using XP so i'd probably need a .dll
hard off wrote:
maybe say which os you're on. i used to have a working version on osx, which i deleted when i refreshed my hard disk, but the only way i could get it going again was to install the new pd-extended.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[ead~] is part of Tom Schouten's Creb library. And it's not installed properly on my version of PD-extended on OSX, although Hans may have put it in a later one. I recall some problems building the creb lib from CVS, but it's too hot out to figure that out right now. You could also try building it from here:
http://zwizwa.fartit.com/pd/creb/
as padawan12 suggested in a suspiciously similar-titled thread on this list not too long ago (less than one month to be exact).
Happy hunting!
d.
hard off wrote:
maybe say which os you're on. i used to have a working version on osx, which i deleted when i refreshed my hard disk, but the only way i could get it going again was to install the new pd-extended.
derek holzer wrote:
[ead~] is part of Tom Schouten's Creb library. And it's not installed properly on my version of PD-extended on OSX, although Hans may have put it in a later one. I recall some problems building the creb lib from CVS, but it's too hot out to figure that out right now. You could also try building it from here:
http://zwizwa.fartit.com/pd/creb/
as padawan12 suggested in a suspiciously similar-titled thread on this list not too long ago (less than one month to be exact).
Happy hunting!
d.
hard off wrote:
maybe say which os you're on. i used to have a working version on osx, which i deleted when i refreshed my hard disk, but the only way i could get it going again was to install the new pd-extended.
hm, here is a binary: http://www.netpd.org/creb.dll
[moritz~]
Thanks all. I am really beginning to regret my penchant for the seductively useful [ead~], but I'm sure the current situation will resolve nicely in time.
At the risk of being controvertial, there really are certain units that one would consider ** absolutely essential ** that haven't found their way into the intrinsic core of Pd, from the top of my head things like [adsr~], [ead~] [inv] (simple reciprocal) come to mind. Of course I don't keep abreast of dev at the cutting edge of Pd which is a fast moving, very active community, so I am probably out of date and wrong on this.
From a users perspective might I suggest a poll? Something like...
"Ten things I can't live without in Pd that are not in the core"
Vote your ten frequently used externals that reside in an supplementary library and at the end approach the authors to ask if they can be folded into the main build?
Just my loose change on the subject. Best, Andy
On Wed, 21 Jun 2006 17:35:18 +0200 moritz erstens@gmx.ch wrote:
derek holzer wrote:
[ead~] is part of Tom Schouten's Creb library. And it's not installed properly on my version of PD-extended on OSX, although Hans may have put it in a later one. I recall some problems building the creb lib from CVS, but it's too hot out to figure that out right now. You could also try building it from here:
http://zwizwa.fartit.com/pd/creb/
as padawan12 suggested in a suspiciously similar-titled thread on this list not too long ago (less than one month to be exact).
Happy hunting!
d.
hard off wrote:
maybe say which os you're on. i used to have a working version on osx, which i deleted when i refreshed my hard disk, but the only way i could get it going again was to install the new pd-extended.
hm, here is a binary: http://www.netpd.org/creb.dll
[moritz~]
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, padawan12 hat gesagt: // padawan12 wrote:
At the risk of being controvertial, there really are certain units that one would consider ** absolutely essential ** that haven't found their way into the intrinsic core of Pd, from the top of my head things like [adsr~], [ead~] [inv] (simple reciprocal) come to mind.
An ADSR is included in Pd as an abstraction, once in the audio examples, once as "gadsr" in doc/7.stuff/synth
[inv] is simply:
[f ] | [1 $1( | [/ ]
or [expr 1/$f1], one could make it an abstraction as well.
Cloning [ead~] is a bit more tricky, but not too much. Btw: Cloning ead~ and using [vline~] while doing so would allow envelopes to start in the middle of a 64-sample block, which would have important advantages for timing (see the recent "metro below 1ms" thread).
doc/3.audio.examples/D03.envelope.dB.pd could be a starting point. Any takers?
Frank Barknecht _ ______footils.org_ __goto10.org__
Frank Barknecht wrote:
[inv] is simply:
[f ] | [1 $1( | [/ ]
or [expr 1/$f1], one could make it an abstraction as well.
GridFlow has [inv*] and [inv+], or you can use [swap] like this:
| [swap 1] | | [/ ] |
Attached is an example.
I would not want an abstraction that does this to be called simply [inv], as it doesn't tell you to which operator the inverse is to be taken.
http://claudiusmaximus.goto10.org
#N canvas 31 56 316 196 10; #X obj 17 58 swap 1; #X obj 17 86 /; #X floatatom 17 108 5 0 0 0 - - -; #X floatatom 18 11 5 0 0 0 - - -; #X obj 18 31 sel 0; #X connect 0 0 1 0; #X connect 0 1 1 1; #X connect 1 0 2 0; #X connect 3 0 4 0; #X connect 4 1 0 0;
On Jun 22, 2006, at 12:07 AM, Frank Barknecht wrote:
Cloning [ead~] is a bit more tricky, but not too much. Btw: Cloning ead~ and using [vline~] while doing so would allow envelopes to start in the middle of a 64-sample block, which would have important advantages for timing (see the recent "metro below 1ms" thread).
doc/3.audio.examples/D03.envelope.dB.pd could be a starting point. Any takers?
hi i made once a vad using vline~. but maybe there is a better way to do that. let me know what you think.
eni
Hallo, Enrique Erne hat gesagt: // Enrique Erne wrote:
On Jun 22, 2006, at 12:07 AM, Frank Barknecht wrote:
Cloning [ead~] is a bit more tricky, but not too much. Btw: Cloning ead~ and using [vline~] while doing so would allow envelopes to start in the middle of a 64-sample block, which would have important advantages for timing (see the recent "metro below 1ms" thread).
doc/3.audio.examples/D03.envelope.dB.pd could be a starting point. Any takers?
hi i made once a vad using vline~. but maybe there is a better way to do that. let me know what you think.
Perfect, that is *exactly* what I meant. (One could replace the dbtorms~ with a table lookup as in the doc-patch, if performance is imporant.)
Frank Barknecht _ ______footils.org_ __goto10.org__
Hallo, Frank Barknecht hat gesagt: // Frank Barknecht wrote:
Enrique Erne hat gesagt: // Enrique Erne wrote:
hi i made once a vad using vline~. but maybe there is a better way to do that.
Perfect, that is *exactly* what I meant.
Attached is another version using quartic envelopes as in doc/3.audio.examples/D04.envelope.quartic.pd
Frank Barknecht _ ______footils.org_ __goto10.org__
Frank Barknecht wrote:
Hallo, Frank Barknecht hat gesagt: // Frank Barknecht wrote:
Enrique Erne hat gesagt: // Enrique Erne wrote:
hi i made once a vad using vline~. but maybe there is a better way to do that.
Perfect, that is *exactly* what I meant.
Attached is another version using quartic envelopes as in doc/3.audio.examples/D04.envelope.quartic.pd
Ciao
ola i have modified a little the vadsr~ from cvs from ben saylor to a var~. i like this one, because you are able to change the curve.. [moritz~]
#N canvas 371 28 768 683 10; #X obj 69 166 ead~ 0 0; #X obj 69 95 metro; #X floatatom 99 67 5 0 0 0 - - -; #X floatatom 94 119 5 0 0 0 - - -; #X floatatom 120 141 5 0 0 0 - - -; #X msg 22 67 stop; #X obj 69 68 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1 ; #N canvas 0 22 424 420 vad~ 0; #X obj 159 214 vline~; #X obj 31 174 vline~; #X obj 159 234 dbtorms~; #X obj 31 194 dbtorms~; #X obj 15 230 -~; #X obj 15 210 sig~ 1; #X obj 102 48 max 0.1; #X obj 202 48 max 0.1; #X obj 31 88 f 3; #X text 100 5 attack (ms); #X text 200 5 decay (ms); #X text 30 5 trigger; #X msg 159 194 0 , 100 0 $1 , 0 $2 $1; #X msg 31 154 100 , 60 $1 0 , 100 0 $1; #X obj 31 108 pack 3 4; #X obj 31 28 inlet; #X obj 102 28 inlet; #X obj 202 28 inlet; #X obj 88 360 outlet~; #X obj 31 48 b; #X connect 0 0 2 0; #X connect 1 0 3 0; #X connect 2 0 18 0; #X connect 3 0 4 1; #X connect 4 0 18 0; #X connect 5 0 4 0; #X connect 6 0 8 1; #X connect 7 0 14 1; #X connect 8 0 14 0; #X connect 12 0 0 0; #X connect 13 0 1 0; #X connect 14 0 12 0; #X connect 14 0 13 0; #X connect 15 0 19 0; #X connect 16 0 6 0; #X connect 17 0 7 0; #X connect 19 0 8 0; #X restore 93 249 pd vad~; #N canvas 0 22 450 300 graph3 0; #X array ead 500 float 2; #X coords 0 1 500 -1 200 140 1; #X restore 552 48 graph; #N canvas 0 22 450 300 graph3 0; #X array vad 500 float 2; #X coords 0 1 500 -1 200 140 1; #X restore 552 188 graph; #X obj 251 49 loadbang; #X msg 214 92 5; #X msg 246 98 9; #X msg 284 104 ; pd dsp 1; #X obj 24 192 tabwrite~ ead; #X obj 39 275 tabwrite~ vad; #X msg 100 31 1; #N canvas 0 22 450 300 graph3 0; #X array qad 500 float 2; #X coords 0 1 500 -1 200 140 1; #X restore 552 328 graph; #X obj 136 340 tabwrite~ qad; #N canvas 147 462 472 436 qad~ 0; #X obj 251 224 vline~; #X obj 69 307 -~; #X obj 158 65 max 0.1; #X obj 258 65 max 0.1; #X obj 87 105 f 3; #X text 156 22 attack (ms); #X text 256 22 decay (ms); #X text 86 22 trigger; #X obj 87 45 inlet; #X obj 158 45 inlet; #X obj 258 45 inlet; #X obj 144 377 outlet~; #X obj 87 65 b; #X obj 251 248 *~; #X obj 250 273 *~; #X obj 87 218 vline~; #X obj 87 248 *~; #X obj 86 273 *~; #X obj 87 125 pack 3 4; #X obj 36 272 sig~ 1; #X text 129 193 attack; #X text 287 195 decay; #X msg 87 171 1 , 0 $1 0 , 1 0 $1; #X msg 251 171 0 , 1 0 $1 , 0 $2 $1; #X connect 0 0 13 0; #X connect 0 0 13 1; #X connect 1 0 11 0; #X connect 2 0 4 1; #X connect 3 0 18 1; #X connect 4 0 18 0; #X connect 8 0 12 0; #X connect 9 0 2 0; #X connect 10 0 3 0; #X connect 12 0 4 0; #X connect 13 0 14 0; #X connect 13 0 14 1; #X connect 14 0 11 0; #X connect 15 0 16 0; #X connect 15 0 16 1; #X connect 16 0 17 0; #X connect 16 0 17 1; #X connect 17 0 1 1; #X connect 18 0 23 0; #X connect 18 0 22 0; #X connect 19 0 1 0; #X connect 22 0 15 0; #X connect 23 0 0 0; #X restore 186 307 pd qad~; #N canvas 0 22 450 300 graph3 0; #X array var 500 float 2; #X coords 0 1 500 -1 200 140 1; #X restore 552 468 graph; #X obj 209 518 tabwrite~ var; #X obj 289 403 random 6; #X obj 297 426 + 1; #X floatatom 304 449 5 0 0 0 - - -; #N canvas 0 0 450 300 var~ 0; #X obj 40 263 line~; #X msg 64 211 1; #X msg 32 213 0; #X obj 41 285 expr~ pow($v1 , $v2) * -1 + 1; #X obj 2 4 inlet trigger; #X obj 364 273 line~; #X msg 321 248 1; #X msg 364 233 0; #X obj 364 296 expr~ pow($v1 , $v2); #X obj 348 501 outlet~; #X obj 102 366 snapshot~; #X obj 40 432 +~; #X obj 40 384 *~; #X obj 347 409 *~; #X obj 150 6 inlet attack; #X obj 288 10 inlet release; #X obj 40 238 pack f $1; #X obj 364 253 pack f $2; #X obj 491 17 inlet curve; #X obj 491 274 sig~ $3; #X obj 232 264 sig~ $3; #X obj 21 110 del $1; #X obj 479 503 outlet switch; #X obj 288 33 max 0.1; #X obj 150 27 max 0.1; #X obj 206 122 1; #X obj 250 85 t b f; #X obj 250 127 + 1; #X obj 2 26 t b b b b; #X obj 214 168 0; #X obj 206 188 change; #X text 285 121 switch on/off; #X text 279 129 your parent-patch; #X obj 491 41 max 0.6; #X text 77 343 avoid clicks ?; #X obj 40 158 t b b b b; #X text 67 108 <-_+/-20ms?; #X obj 213 149 del; #X obj 250 108 + $2; #X obj 201 86 $1; #X obj 201 66 loadbang; #X obj 102 388 - 1; #X obj 102 408 * -1; #X connect 0 0 3 0; #X connect 1 0 0 0; #X connect 2 0 16 0; #X connect 3 0 12 0; #X connect 4 0 28 0; #X connect 5 0 8 0; #X connect 6 0 5 0; #X connect 7 0 17 0; #X connect 8 0 13 1; #X connect 10 0 11 1; #X connect 10 0 41 0; #X connect 11 0 13 0; #X connect 12 0 11 0; #X connect 13 0 9 0; #X connect 13 0 10 0; #X connect 14 0 24 0; #X connect 15 0 23 0; #X connect 16 0 0 0; #X connect 17 0 5 0; #X connect 18 0 33 0; #X connect 19 0 8 1; #X connect 20 0 3 1; #X connect 21 0 7 0; #X connect 23 0 17 1; #X connect 23 0 26 0; #X connect 24 0 16 1; #X connect 24 0 21 1; #X connect 24 0 38 0; #X connect 25 0 30 0; #X connect 26 0 38 0; #X connect 26 1 38 1; #X connect 27 0 37 1; #X connect 28 0 37 0; #X connect 28 1 21 0; #X connect 28 2 35 0; #X connect 28 3 25 0; #X connect 29 0 30 0; #X connect 30 0 22 0; #X connect 33 0 19 0; #X connect 33 0 20 0; #X connect 35 0 2 0; #X connect 35 1 6 0; #X connect 35 2 1 0; #X connect 35 3 10 0; #X connect 37 0 29 0; #X connect 38 0 27 0; #X connect 39 0 38 0; #X connect 40 0 39 0; #X connect 41 0 42 0; #X connect 42 0 12 1; #X restore 236 454 pd var~; #X msg 172 61 400; #X text 321 435 <-6 is most like curve from ead; #X connect 0 0 14 0; #X connect 1 0 0 0; #X connect 1 0 7 0; #X connect 1 0 14 0; #X connect 1 0 15 0; #X connect 1 0 18 0; #X connect 1 0 19 0; #X connect 1 0 25 0; #X connect 1 0 22 0; #X connect 1 0 21 0; #X connect 2 0 1 1; #X connect 3 0 0 1; #X connect 3 0 7 1; #X connect 3 0 19 1; #X connect 4 0 0 2; #X connect 4 0 7 2; #X connect 4 0 19 2; #X connect 5 0 1 0; #X connect 6 0 1 0; #X connect 7 0 15 0; #X connect 10 0 11 0; #X connect 10 0 12 0; #X connect 10 0 26 0; #X connect 10 0 13 0; #X connect 10 0 16 0; #X connect 11 0 3 0; #X connect 11 0 25 1; #X connect 12 0 4 0; #X connect 12 0 25 2; #X connect 16 0 6 0; #X connect 19 0 18 0; #X connect 22 0 23 0; #X connect 23 0 24 0; #X connect 23 0 25 3; #X connect 25 0 21 0; #X connect 26 0 2 0;
Hallo, moritz hat gesagt: // moritz wrote:
i have modified a little the vadsr~ from cvs from ben saylor to a var~. i like this one, because you are able to change the curve..
Cool, this could become an "all-about-curved-envelopes.pd" help patch. I would recommend to use vline~ however, because then you can time events with better accuracy. Also it is easier to patch, because it has a [del] built in. I modified [pd qad] a bit to show this in action.
Frank Barknecht _ ______footils.org_ __goto10.org__
On 23/06/2006, at 18.29, Frank Barknecht wrote:
Cool, this could become an "all-about-curved-envelopes.pd" help patch.
The "this" that are referred to is a patch that was assembled though
a discussion about building ead~ in vanilla Pd. The latest one was
names 'ead-vs-vad-vs-qad-vs-var-vline.pd' and can be found in the
archive:
http://lists.puredata.info/pipermail/pd-list/2006-06/039489.html
Or, was there being developed further? It would be cool to have in
docs of section of CVS? (hint).
Best, Steffen
On Apr 11, 2007, at 11:55 AM, Steffen wrote:
On 23/06/2006, at 18.29, Frank Barknecht wrote:
Cool, this could become an "all-about-curved-envelopes.pd" help
patch.The "this" that are referred to is a patch that was assembled though a discussion about building ead~ in vanilla Pd. The latest one was names 'ead-vs-vad-vs-qad-vs-var-vline.pd' and can be found in the archive: http://lists.puredata.info/pipermail/pd-list/2006-06/039489.html
Or, was there being developed further? It would be cool to have in docs of section of CVS? (hint).
There is already a 'doc' section of CVS.
all_about_curved_envelopes.pd would go well into pure-data/doc/pddp/
with the other all_about patches.
On the topic of curves, I've been checking in a bunch of curve
objects to the mapping library. I just realized that these would be
potentially useful here. This is what we've got so far:
breakpoint breakpoint_smooth circular_seat circular_sigmoid exponential_curve exponential_seat exponential_sigmoid elliptic_seat elliptic_sigmoid logistic_sigmoid sinusoid
.hc
Best, Steffen
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
The arc of history bends towards justice. - Dr. Martin Luther
King, Jr.
On 12/04/2007, at 5.44, Hans-Christoph Steiner wrote:
There is already a 'doc' section of CVS.
all_about_curved_envelopes.pd would go well into pure-data/doc/ pddp/ with the other all_about patches.
Yeah. I carefully checked it wasn't added prior to posting.
I haven't fund a good enough reason to have write access to the CVS
repo yet. Maybe nagging is good enough 8-)
On the topic of curves, I've been checking in a bunch of curve
objects to the mapping library. I just realized that these would
be potentially useful here.
Um, they are all nice objects for mapping the interval [0, 1] to [0,
1] with a bijective map - that maps 0 to 0 and 1 to 1. Indeed. But
envelopes are rather (this might be a sloppy home-brew definition?) a
non-injective map from [0,1] to [0,1] that maps {0,1} to 0.
So potential, yes, thanks. I'll see if i can't find time to look into
it. It's properly just involves changing the map's/expr's a bit.
However I would be surprised if most of the, in digital synthesis,
commonly just envelops don't float about already. Hence making a
fairly exhaustive all_about(_curved)_envelopes.pd would be grab to
the pocket from a few experienced users.
Well. I'll see what i can do with my novice skills.
On 13/04/2007, at 11.50, Steffen wrote:
Well. I'll see what i can do with my novice skills.
I've just played a bit with the before mentioned patch. And altered
it a bit. I've added a sound test and funk'd/cleaned it up a tad. And
saved the creb/ead~ envelope in the table such that it makes sense to
play with without that object.
Though it's trivial i thought it would be in order to share. Attached.
Best, Steffen.
i made an expr~ equation that makes an ead~ curve from an audio signal (such as phasor~, or vline~)
On Thu, 22 Jun 2006, Frank Barknecht wrote:
[inv] is simply:
[f ] | [1 $1( | [/ ]
or [expr 1/$f1], one could make it an abstraction as well.
[pow -1]
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
thanks, I deleted lots of mailing list e-mails a couple of days ago and I honestly didnt try searching the forum after seeing how difficult it was to search for ead in google...
i'm sure i'll get it up and running, but the version at netpd/creb.dll the only objects that didnt seem to work were the ead~ family...
cheers,
pete
derek holzer wrote:
[ead~] is part of Tom Schouten's Creb library. And it's not installed properly on my version of PD-extended on OSX, although Hans may have put it in a later one. I recall some problems building the creb lib from CVS, but it's too hot out to figure that out right now. You could also try building it from here:
http://zwizwa.fartit.com/pd/creb/
as padawan12 suggested in a suspiciously similar-titled thread on this list not too long ago (less than one month to be exact).
Happy hunting!
d.
hard off wrote:
maybe say which os you're on. i used to have a working version on osx, which i deleted when i refreshed my hard disk, but the only way i could get it going again was to install the new pd-extended.
The complete creb collection is included in the most recent test
releases of Pd-extended.
.hc
On Jun 21, 2006, at 11:14 AM, derek holzer wrote:
[ead~] is part of Tom Schouten's Creb library. And it's not
installed properly on my version of PD-extended on OSX, although
Hans may have put it in a later one. I recall some problems
building the creb lib from CVS, but it's too hot out to figure that
out right now. You could also try building it from here:http://zwizwa.fartit.com/pd/creb/
as padawan12 suggested in a suspiciously similar-titled thread on
this list not too long ago (less than one month to be exact).Happy hunting!
d.
hard off wrote:
maybe say which os you're on. i used to have a working version on osx, which i deleted when i refreshed my hard disk, but the only
way i could get it going again was to install the new pd-extended.-- derek holzer ::: http://www.umatic.nl ---Oblique Strategy # 173: "Voice your suspicions"
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
http://at.or.at/hans/