@jyg someone reported a similar issue with the deken installation on a Windows OS on github. I can not reproduce this on Linux and i don't know what could be causing it, so my suspicion was that it is somehow related to Windows security permissions. Are you using Windows? Does this happen with other libraries as well? Unfortunately, there is not much i can do about it, but i'll test as soon as i have access to a Windows machine.
For now, if you want to stay up to date you can download from github and set the path manually in pd settings.

Edit: just saw that you created another issue about this on github. I'll close it because it is not related to the development of this library, but we can continue the conversation here.

@jamcultur thanks! You can save any of these objects with a message [save 1( to the rightmost inlet. Then use [recall 1( to retrieve your parameter settings. You can save up to 21 presets this way. This is also documented in the help files and in Examples/01-basics.pd

you can find the paf~ external in one of the pieces that Miller shares with the Pure Data Repertory Project (in /externs/paf~/):
https://msp.ucsd.edu/pdrp/latest/manoury-enecho.tgz

@Moothart i never used [abl-link~], so i don't know how it behaves exactly. You can try something like this maybe

or use the set method for change (check the helpfile)

@Moothart in this case you can use [change]

you can also [del 0] or just [del] like this:

however, this will force any bang to come last in the trigger order. If you rely on trigger in this part in your patch you'd need another [del] to correct it:

Version 0.70 is now available on deken.

I added some simple but convenient objects:

pp.amp~ a simple signal multiplier
pp.adsr~ adsr/adr envelope generator
pp.xfade~ signal crossfader
pp.shiftlfo~ a LFO that can generate irregular rhythmic patterns

pp.dynamics~ now has an option to enable feedback compression

Some parameter sliders are now colored light orange in the GUI. This indicates that the slider does not cover the full range of the parameter and is intended to encourage experimenting with values that are above or below the range of the slider.

fixed some minor bugs.

Happy patching!

@qhr33k Thanks!

about this sidechain thing; yes you would need to feed the compressor an audio signal and use the sidechain output to let's say duck the tail of a reverb (that's just an example, you can do whatever you want with this). In this case you would multiply the 100% wet reverb with the signal from the sidechain outlet of the compressor like this:

sidechain_compression.pd

The presets are more or less didactic, you can use them as a starting point and then change the parameters until they fit your needs. In the case above you'd use the "compress" preset. I think what confuses you is the preset "Env.follow(sidechain)". This one is an envelope follower, the comment (sidechain) hints that the envelope is the signal from the sidechain outlet. Hope that makes sense?

@ddw_music

I feel a bit like the "spray everywhere" solution would require more object copy/paste -- mine just has "; next symbol instr1" where the other needs a [t], a [s], a [r], and an [f].

well, you can wrap it into a subpatch and copy/paste that : )
Essentially both methods are not complicated, they just have to be implemented in a low level language as @oid pointed out.

reading this thread, what i understand so far is this is about calling some function, store its output and retrieve it at a given point... Something like this in pd? do i miss something?
`