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

@liamorourke these are vanilla only (;

@solipp really? thanks

this is simply marvelous thanks so much

pushed an update to deken (v 0.3).

changes since the last version:

new objects:
pp.fft-freeze~ - a spectral freezer based on I08.pvoc.reverb.pd

pp.ladder~ - a "moog" 4th order ladder filter. I made this on out of curiosity about the "zero delay filter" design. I wouldn't recommend to use it though since we have [bob~] and cpu usage is pretty high! (except if you need a fast modulating resonant hp or bp filter for whatever reason).

pp.echo~ - an "analog" tape delay-ish delay echo effect.

pp.xycurve - draws a xy-bezier curve and reads from it. Useful for all kinds of musical gestures..

Many bugfixes and smaller changes. Be aware that some object might behave a little bit differently to the last version!

This is immense! Thanks a lot

NIcenadditions, solipp!
Could you also implement an Haas effekt?

@tungee Haas effect is already implemented in your brain, it's a psychoacoustic effect

I guess you want is a small delay between two output channels. You can do it with [pp.sdel~] samplewise delay.
something like this:

assuming you have the abstractions in your path, here is the patch:
interaural.pd

edit:
if you change the delay times over time you can get some nasty phasing effects depending on the position of your speakers. it works okay with headphones though.

Thank you very much Solipp.
Exactly what i asked for

wow this is really beautiful work!

Thank you solipp, look like a really interesting library.
I've got an error when I'll try to use it:
"audiolab: can't load library"

I thought because I'm using Pd 0.50.2 "vanilla", is it possible? Will it be available for this version?

@tabache seems like you have declared "audiolab" under File -> Preferences -> Startup.
You only need to do this for single binary libraries, e.g. zexy or GEM. Audiolab is a collection of abstractions. You can point pd to the right directory under File -> Preferences -> Path, or you can just copy the audiolab folder into your projects directory and use [declare -path ./audiolab] in your main patch.
It should still work with Pd 0.50.2, but in the future I'll incorporate any new features of pd whenever it makes sense.. you should stick with the latest version of pd, there are only benefits.

cheers!

new version up! (v 0.4)

two new objects:

pp.parameq~ - a parametric equalizer.
fancy! I guess I pushed pd-UI design to the limits with this one:

pp.butterkreuz3~ - a 3 band crossover filter with a relatively flat magnitude response. Allows you to create multiband (well, 3 band) effects.

...many fixes, changes, additions... (sorry, I'm too lazy to keep track)

Wow! Great additions!

In your audiolab plugin suite, there are a lot of nice filter implentations mostly in moog-ladder style. In case your are interested in implentation of an Oberheim-style filter:

https://github.com/ddiakopoulos/MoogLadders/blob/master/src/OberheimVariationModel.h

https://www.willpirkle.com/app-notes/

Best Reagrds

@solipp Thank you for contributing this library, I'm learning tons. I have some questions about fft-split~.

• It looks like you are simply passing the bins that are below the threshold frequency to the left inverse transform, and the rest to the right (with the omitted bins on each side muted), is that correct?
• If so, then why does the transition band sound continuous? i.e. when I output lowpass to the left and highpass to the right, as I sweep up it moves continuously from left to right around the threshold frequency.
• I struggled to make a test to see what phase distortions occur near the threshold frequency, and there don't appear to be any. Could that be true? (I'm not confident I tested properly)

@jameslo said:

• It looks like you are simply passing the bins that are below the threshold frequency to the left inverse transform, and the rest to the right (with the omitted bins on each side muted), is that correct?

yes, that's correct.

• If so, then why does the transition band sound continuous? i.e. when I output lowpass to the left and highpass to the right, as I sweep up it moves continuously from left to right around the threshold frequency.

that is the result of spectral smearing i guess https://en.wikipedia.org/wiki/Spectral_leakage
the slopes of the lowpass/highpass are not perfectly steep

• I struggled to make a test to see what phase distortions occur near the threshold frequency, and there don't appear to be any. Could that be true? (I'm not confident I tested properly)

there shouldn't be any phase distortion. essentially it's a linear phase FIR filter.

@tungee thanks for the links!
I made this pp.ladder~ filter to get an idea about the concept of "zero delay filters". So I kind of mapped it out as a pd patch to get an overview (not that i fully understand it now...)
However, it makes much more sense to create externals (instead of vanilla abstractions) of this filters. Pure data is really not efficient in processing patches with one sample dsp blocks.

@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.