here is the updated version of my DIY library. it is a collection of various useful audio modules for music production.

unfortunately my pd computer packed it in last week, so it is in a bit of a 90% completed state, but there should be enough stuff to play with until i get a chance to get in and get it all 100% done.

open 000-introduction.pd to get started.

http://www.pdpatchrepo.info/hurleur/DIY2.zip

Hey I got a question. in the compression patches I can kind of get my head around the amp factor section. But I don't get any of the att/rel section. Can anyone explain what that sgn~ (signum) is/does ? Secondly I can see the table is effected by the release but not really on the attack. I can hear the attack. The block size is 2. I'm guessing if the default block size is 64 samples then 2 means 128?? Or is it actually 2 ? This outputs a frequency between 0.019 and 57 into a VCF along withe the original amp factor. Any advice ?

that's a patch i nabbed from the net-pd library i think. actually it seems to work ok, but from what i have read, a block size of 2 might not actually work. yes block 2 does actually mean it should have a size of 2. some people said on the pd list that pd is hardcoded to limit blocksize above 32.

i don't really know what signum~ does, and i have never used it (except in cases like this where i have borrowed whole patches)

you could email roman who made that patch and ask him i guess. pretty sure his mail address is on the netpd site.

Ahh ok cheers.

[sgn~] is just a sign function. I've never been able to figure out Roman's compressor, but if you want to learn about simple limiters and compressors in Pd, try the ones from Johannes' pd-tutorial.com. I personally prefer using his limiter patch to make a classic compressor with makeup gain.

@hardoff said:

some people said on the pd list that pd is hardcoded to limit blocksize above 32.

I don't think that could be true, because if you check out help patch G04.control.blocksize.pd, where [pd delay-writer] has [block~ 1], you can go above 1378.12 Hz in the delay loop (whereas you can't with block size 32). But there do seem to be tuning problems when you get up in that range.

Also, here's a simple compressor adapted (ever so slightly) from Johannes' limiter.

http://www.pdpatchrepo.info/hurleur/simplecompressor.pd

Woa cheers ichabod. That website looks really useful.

I think ichabod's right. I've made comb filters with [block~ 1], and you can clearly hear the difference between a 1, 2, and 3 sample delay.

thank you hardoff, this is quite a body of work!

Very, very interesting, and mind boggling for a relative noob.

I'd been puzzling over how to achieve an intensely lush phaser...and here it is! But I have a long way to go before I have an idea HOW it got that way.

Thanks for uploading what is essentially a magnificent study-guide to pd!

thanks!
at least 10 things in there which i wanted to build and 100 more which are just awesome

looking at hardoffs profile it seems he is not active any more
i started to really like the diy2 package

maybe anyone here can answer me why the modulate .oOo...... does the line only for the set value and not for value, mul and add
i would have chosen the place for the line after the clip

i did change the syn-rain because for me it only produced white noise. i also added some sliders to it
you should try to run it at the samplerate specified in the patch because that's the rate i made my changes for. i later found out that the filters get a lot louder and change in the way they work on 44.1khz so maybe my result has some flaws, not intended in the original by obiwanabe (he is missing too, right?)
the amount slider has a REALLY slow reaction time
i changed the thunder a bit so that it will thunder only half as much when the slider is below 60% because i didn't like the constant thunder.. i could have made even 1/4th but didn't bother enough. AND it might get really loud. I've seen 120Db at max gain and thunder
its all a result of randomly changing values and stuff so there might be things which could be done better... do so and tell me/us!

then i did some freqshifters and some (those with the F, which means the 2 butterworth Q10 Filters) with reflection prevention (tm) which should be especially interesting in feedback loops
some frequencys might get through the prevention but should be attenuated.... a bit... don't remember my tests.. it should be at least -20db but might be -40db

any feedback critics questions and whatever is welcome

hope the community shares its stuff too

http://www.pdpatchrepo.info/hurleur/syn-rainS.pd

looking at hardoffs profile it seems he is not active any more
i started to really like the diy2 package

maybe anyone here can answer me why the modulate .oOo...... does the line only for the set value and not for value, mul and add
i would have chosen the place for the line after the clip

i did change the syn-rain because for me it only produced white noise. i also added some sliders to it
you should try to run it at the samplerate specified in the patch because that's the rate i made my changes for. i later found out that the filters get a lot louder and change in the way they work on 44.1khz so maybe my result has some flaws, not intended in the original by obiwanabe (he is missing too, right?)
the amount slider has a REALLY slow reaction time
i changed the thunder a bit so that it will thunder only half as much when the slider is below 60% because i didn't like the constant thunder.. i could have made even 1/4th but didn't bother enough. AND it might get really loud. I've seen 120Db at max gain and thunder
its all a result of randomly changing values and stuff so there might be things which could be done better... do so and tell me/us!

then i did some freqshifters and some (those with the F, which means the 2 butterworth Q10 Filters) with reflection prevention (tm) which should be especially interesting in feedback loops
some frequencys might get through the prevention but should be attenuated.... a bit... don't remember my tests.. it should be at least -20db but might be -40db

any feedback critics questions and whatever is welcome

hope the community shares its stuff too

http://www.pdpatchrepo.info/hurleur/syn-rainS.pd

looking at hardoffs profile it seems he is not active any more
i started to really like the diy2 package

maybe anyone here can answer me why the modulate .oOo...... does the line only for the set value and not for value, mul and add
i would have chosen the place for the line after the clip

i did change the syn-rain because for me it only produced white noise. i also added some sliders to it
you should try to run it at the samplerate specified in the patch because that's the rate i made my changes for. i later found out that the filters get a lot louder and change in the way they work on 44.1khz so maybe my result has some flaws, not intended in the original by obiwanabe (he is missing too, right?)
the amount slider has a REALLY slow reaction time
i changed the thunder a bit so that it will thunder only half as much when the slider is below 60% because i didn't like the constant thunder.. i could have made even 1/4th but didn't bother enough. AND it might get really loud. I've seen 120Db at max gain and thunder
its all a result of randomly changing values and stuff so there might be things which could be done better... do so and tell me/us!

then i did some freqshifters and some (those with the F, which means the 2 butterworth Q10 Filters) with reflection prevention (tm) which should be especially interesting in feedback loops
some frequencys might get through the prevention but should be attenuated.... a bit... don't remember my tests.. it should be at least -20db but might be -40db

any feedback critics questions and whatever is welcome

hope the community shares its stuff too

http://www.pdpatchrepo.info/hurleur/syn-rainS.pd

looking at hardoffs profile it seems he is not active any more
i started to really like the diy2 package

maybe anyone here can answer me why the modulate .oOo...... does the line only for the set value and not for value, mul and add
i would have chosen the place for the line after the clip

i did change the syn-rain because for me it only produced white noise. i also added some sliders to it
you should try to run it at the samplerate specified in the patch because that's the rate i made my changes for. i later found out that the filters get a lot louder and change in the way they work on 44.1khz so maybe my result has some flaws, not intended in the original by obiwanabe (he is missing too, right?)
the amount slider has a REALLY slow reaction time
i changed the thunder a bit so that it will thunder only half as much when the slider is below 60% because i didn't like the constant thunder.. i could have made even 1/4th but didn't bother enough. AND it might get really loud. I've seen 120Db at max gain and thunder
its all a result of randomly changing values and stuff so there might be things which could be done better... do so and tell me/us!

then i did some freqshifters and some (those with the F, which means the 2 butterworth Q10 Filters) with reflection prevention (tm) which should be especially interesting in feedback loops
some frequencys might get through the prevention but should be attenuated.... a bit... don't remember my tests.. it should be at least -20db but might be -40db

any feedback critics questions and whatever is welcome

hope the community shares its stuff too

http://www.pdpatchrepo.info/hurleur/syn-rainS.pd

looking at hardoffs profile it seems he is not active any more
i started to really like the diy2 package

maybe anyone here can answer me why the modulate .oOo...... does the line only for the set value and not for value, mul and add
i would have chosen the place for the line after the clip

i did change the syn-rain because for me it only produced white noise. i also added some sliders to it
you should try to run it at the samplerate specified in the patch because that's the rate i made my changes for. i later found out that the filters get a lot louder and change in the way they work on 44.1khz so maybe my result has some flaws, not intended in the original by obiwanabe (he is missing too, right?)
the amount slider has a REALLY slow reaction time
i changed the thunder a bit so that it will thunder only half as much when the slider is below 60% because i didn't like the constant thunder.. i could have made even 1/4th but didn't bother enough. AND it might get really loud. I've seen 120Db at max gain and thunder
its all a result of randomly changing values and stuff so there might be things which could be done better... do so and tell me/us!

then i did some freqshifters and some (those with the F, which means the 2 butterworth Q10 Filters) with reflection prevention (tm) which should be especially interesting in feedback loops
some frequencys might get through the prevention but should be attenuated.... a bit... don't remember my tests.. it should be at least -20db but might be -40db

any feedback critics questions and whatever is welcome

hope the community shares its stuff too

http://www.pdpatchrepo.info/hurleur/syn-rainS.pd

Hardoff has transformed into mod, so he will answer soon i guess

yeah, sorry about the name change. i'm hardoff.

>>maybe anyone here can answer me why the modulate .oOo...... does the line only for the set value and not for value, mul and add
i would have chosen the place for the line after the clip<<

i think my original way of thinking was that the inlets could be used with step sequencers and stuff, and it may be useful to have the values settable instantly. in hindsight, i never really need that function, so line after the clip would probably be more useful. will keep that in mind with the next update of the collection (i have been working on it a bit lately, there are quite a few new bits, and it's now all vanilla pd!)

cheers for the new abstractions!!! will have a play with them and get them in the next update too (DIY3)

well the value can be changed by a sequencer as well. also the 20ms line is almost instant. but i can see where this could lead to some artefacts e.g. delread~

another suggestion: why not make a lib sub-folder. where you can store such things like modulate. or a scale log which then could work with arguments. currently i guess it would be annoying to change all modulates.

thanks.... now i cant wait for DIY3

>>another suggestion: why not make a lib sub-folder. where you can store such things like modulate. or a scale log which then could work with arguments. <<

that's how i originally did it, but i just wanted to make it so that the modules would just 'work' even if they were removed from the library. i guess i was kind of successful in that regard, because i have spotted some of my drums and stuff inside other people's projects. the only abstraction they need is the 808_state for state saving, but they will work fine without that anyway.

>>currently i guess it would be annoying to change all modulates.<<

i sometimes have a lot of free time the other day i went through the whole library and replaced all the [loadbang] objects with a subpatch to allow for loadbang on dynamic creation. this meant changing around 100 patches and resaving them.

i will do DIY3 soon then. it is not 'finished', and i have some worries that it is not at all backwards compatible with DIY2, but at the end of the day i am a musician more than a programmer, so the function is what matters.

diy3 'upgrades' include:

a built in sound editor, so you can record loops and sounds and edit them within pd and then export them to .wav files.

some more 'synth' like modules and effects units (tape echo, etc)

inbuilt diy-clock module that ties everything together for sequencing, and then of course some sequencer modules.

vanilla pd compatibility (this unfortunately meant removing some really useful things like the 7 and 13 band EQ's, but they could always be imported from DIY2)

well if people take your instruments they can also take the necessary libs... its not that they have to get them at some unknown place in the internet.
but it would make your work easier... time you could spent on better things

looks like the next version will be even greater but don't rush it
seems like a great bunch of work

but couldn't you have found another solution for the vanilla compatibility?
something like mark those abstractions or put them in a sub-folder "non vanilla" or something?

but don't forget its your library so only your opinion matters

butt_counter == 5