my "audiolab" abstraction library is now available on deken. You'll need Pd-0.50 or later to run this.
Please report any bugs on github: https://github.com/solipd/AudioLab

here is a picture to draw you in (:

Edit:
list of objects:

Soundfle processing
pp.sfplayer~ ... variable-speed soundfile player
pp.grainer~ ... granular sampler
pp.fft-stretch~ ... pvoc time stretching & pitch shifting

Spatialization
pp.pan~ ... constant power stereo panning
pp.midside~ ... mid-side panning
pp. spat8~ ... 8-channel distance based amplitude panning
pp.doppler~ ... doppler effect, damping & amplitude modulation
pp.dopplerxy~ ... xy doppler effect

Effects
pp.freqshift~ ... ssb frequency shifter
pp.pitchshift~ ... pitch shifter
pp.eqfilter~ ... eq-filter (lowpass, highpass, resonant, bandpass, notch, peaking, lowshelf, highshelf or allpass)
pp.vcfilter~ ... signal controlled filter (lowpass, highpass, resonant)
pp.clop~ ... experimental comb-lop-filter
pp.ladder~ ... moogish filter
pp.dynamics~ ... compressor / expander
pp.env~ ... simple envelope follower
pp.graindelay~ ... granular delay
pp.rev~ ... fdn-reverberator based on rev3~
pp.twisted-delays~ ... multipurpose twisted delay-thing
pp.shepphaser~ ... shepard tone-like phaser effect
pp.echo~ ... "analog" delay

Spectral processing
pp.fft-block~ ... audio block delay
pp.fft-split~ ... spectral splitter
pp.fft-gate~ ... spectral gate
pp.fft-pitchshift~ ... pvoc based pitchshifter
pp.fft-timbre~ ... spectral bin-reordering
pp.fft-partconv~ ... partitioned low latency convolution
pp.fft-freeze~ ... spectral freezer

Misc.
pp.in~ .... mic. input
pp.out~ ... stereo output & soundfile recorder
pp.out-8~ ... 8 channel output & soundfile recorder
pp.sdel~ ... samplewise delay
pp.lfnoise~ ... low frequency noise generator
pp.spectrum~ ... spectrum analyser
pp.xycurve

@solipp I was wondering if fft-split~ could be used as an upsampled anti-aliasing filter but I'm not getting the results I expected. Things seem to change radically depending on the oversampling factor. What am I misunderstanding?
fft-split~ as antialias filter.pd

EDIT: NEVERMIND
It appears that Pd doesn't perform the 4X overlapped FFT windowing as expected if the FFT's block size is smaller than 4X the block size of the enclosing patch. When I change fft-split~'s block size to 4096, things are fine. But let me know if I've given the wrong reason.

@jameslo nja, i think you gave the wrong reason
if you run pd at samplerate 44100 and you upsample by 16, the samplerate of the patch is 705 600. Devide this by fft-split~'s default blocksize 1024 and you get a bin resolution of 705600/1024 ~ 689 hz.
This is like running fft-split~ with a blocksize of 64 at normal samplerate (44100/64 ~ 689). You can try, [pp.fft-split 64 4] will give you the same strange result (I'm not even sure why fft patches start to act weird when you run them with block sizes >256, maybe it actually is related to overlap...)
With block size 4096 you get 705600/4096 ~ 172hz resolution, but you probably want 705600/16384 ~ 43hz witch relates to 44100/1024 ~ 43hz.

Maybe someone can help me here. I LOVE the parameq~ object, BUT it resets every time I close and reopen my patch.
I've tried saving the patch after setting the parameq~ object, and I've also tried saving the parameq~ object once I've adjusted the EQ settings, but every time I reopen it has completely reset again. What am I missing here???

@Dizzy-Dizzy Before saving and closing your patch, you have to send manually a [save $1( message to right inlet of all pp.objects of interest (where $1 is replaced by a "preset"number of your choice).
When you re-open the patch, you have to send a [recall $1( message to the same inlets.

Amazing, thanks got it working! Always learning something new...

I'd like to use pp.fft-partconv~ on a long impulse response but I get the message "pp.fft-partconv-st~: IR length exceeds buffer". Do either of the creation arguments control the buffer length? Sorry for my laziness.

edit: OMG I am so lazy, what is my problem? It took 30 mins to find the answer, here's how:

• use text editor to search pp.fft-part*.* for the error message

• find subpatch that prints the message

• look at the condition that makes it print

• trace backwards on some of the receives that could make the condition true, e.g. $0-nparts

• notice that one factor in $0-nparts is $0-max-blocksize. Gee, that happens to resemble the name of one of the creation arguments.

• try it. Bingo!

@solipp said:

https://github.com/solipd/AudioLab

this is such a great collection, thank you for sharing with all of us

i'm fairly new to Pd, was wondering how difficult it might be to create a 7.1 preset in the spat8 patch? (ie Front L, C, R. Side L R. Rear L R, and sub?)

I tried just moving the speakers into position which worked but when I save and re-open it reverts to octophonic.

Any guidance will be greatly appreciated, thank you.

Sorry for not posting for some ... 2 years. Just a reminder that this project is still alive and slowly but surely evolving.
I pushed an update to deken today, v0.61. New stuff since version 0.4 include:

pp.fft-profile~ - esoteric spectral denoiser/vocoder
pp.loop.rec~ pp.loop.play~ - a pair of abstractions to record and play loops, but also useful for pitch shifting/reverse delays
pp.grainrev~ - a granular reverb, very cool
pp.phiverb~ - a good sounding reverb

many bugfixes and some new examples.

Make sure to use the latest version of pd (pd-0.55 at the time of posting).
In plugdata most objects should work but needs more testing.

@jewelzcotard sorry for the late reply, anyway if you moved the speakers in the gui, you can save with msg [save 1( to the rightmost inlet of pp.spat8~ and save the patch. A msg [recall 1( to the same inlet will load your settings.

Happy patching and make some noise!

@solipp said:

pp.phiverb~

what can you tell us about this new object? Where is the model from, what is it based on? I'm interested in reverb design

thanks

@porres
It is based on this talk by Geraint Luff:

However, the basic structure is the same as in rev3~, early reflections are fed into a 16-channel fdn. Delay times are selected from a table of prime numbers. The "secret" lies in the mixdown of the 16 fdn channels to stereo. It was more or less trial and error, adding and subtracting the signals and listening what sounds good.

nice, thanks