Thanks , I have been looking for a midi controlled adsr in pure data. It is very important that the release section is triggered at the end of each midi note. Thanks again.
there is already one adrs envelope example explained perfectly in the pd browser done by the actual writer of the program.....you just bought a mac isn't it??
can you or someone explain the message box [1 $2, $4 $3 $2] and the [0 $2] because, really, thanks a lot for the video but it'd be awesome to know how that message box works. :)
great video, very helpful, but the definition is not so high - so it's hard to see what's inside the messages between the variables, particularly for the decay - is it right to assume that it's: sustain value ($4) in decay + attack ($3+$2)? so that message contains (1 $2, $4 $3+$2)
Mh... checklist for the app: OSC - enabled Host - same IP-adress as your PC/MAC Port (outgoing) - same number as in the "udpreceive"-object Wifi - ON! (same as your PC/MAC) checklist for PC/MAC: firewall settings - allow pd to receive messages Wifi - ON! In pd you can check incoming OSC messages with the "print"-object connected to the "unpackOSC"-object. The messages will be printed in the parent window.
@juanesr92 Sounds like you don't got the mrpeach library. A red dashed box means pd doesn't know this object. Another way to import a library is to make an object and call it "import mrpeach". But this works just for this file. Good luck.
Why do you use a message + variables into the vline ~ , the pack object is enough to make a list ?
ntof?? atof?? stof?? whats word?? or letters
Not work for me ((((((((
this helped me a lot. thank you!
Thanks , I have been looking for a midi controlled adsr in pure data. It is very important that the release section is triggered at the end of each midi note. Thanks again.
awesome! the simplest most direct instruction for an ADSR ever.
there is already one adrs envelope example explained perfectly in the pd browser done by the actual writer of the program.....you just bought a mac isn't it??
why use those $2, $4 etc? and not $1 for example?
$1 is for triggering the envelope (see 4:00)
The dollar signs numbers are simply referring to the pack inlets, in this case pitch, attack, decay and sustain, but it could be anything....
Is the sustain value $4 an arbitrary value or does it need to be $4 to work? why can't it be 3 or 0.8 etc
can you or someone explain the message box [1 $2, $4 $3 $2] and the [0 $2] because, really, thanks a lot for the video but it'd be awesome to know how that message box works. :)
Hi, what if i want to use the bang button instead of the midi input? I have the oscilators setting the frequency played
great video, very helpful, but the definition is not so high - so it's hard to see what's inside the messages between the variables, particularly for the decay - is it right to assume that it's: sustain value ($4) in decay + attack ($3+$2)? so that message contains (1 $2, $4 $3+$2)
Great, thankyou man
Thanks !!!
Great video, thanks!
Thanks!
Finally! This has been a great help thank you!
Fantastic tutorial. Cheers
Thank you! For some reason this has been a mystery for me (untill now) from 2009.
incredible video. Thank you so much
Thanks a lot!
thanks a lot... just what I was looking for :)
This was really helpful. Thank you!
Mh... checklist for the app: OSC - enabled Host - same IP-adress as your PC/MAC Port (outgoing) - same number as in the "udpreceive"-object Wifi - ON! (same as your PC/MAC) checklist for PC/MAC: firewall settings - allow pd to receive messages Wifi - ON! In pd you can check incoming OSC messages with the "print"-object connected to the "unpackOSC"-object. The messages will be printed in the parent window.
@juanesr92 Sounds like you don't got the mrpeach library. A red dashed box means pd doesn't know this object. Another way to import a library is to make an object and call it "import mrpeach". But this works just for this file. Good luck.