-
solipp
@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. -
solipp
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 reverbmany 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
Hi @Nullstrahler
"cd" stands for "change directory". "path/to/pd" is of course a placeholder. You have to replace it with the path to the directory you chose for the source files. Alternatively, you can use your file manager to open the directory, and then right-click -> "Open Terminal Here".you'll need the following dependencies to compile pure data, some of them might be already installed on your system. Install with apt:
sudo apt install build-essential automake autoconf libtool gettext
sudo apt install libasound2-dev libjack-jackd2-dev
Then follow the install instructions. In a nutshell:
./autogen.sh
./configure --enable-jack
this compiles pd with jack support. you can check the configure options with
./configure --helpmake
if make runs without errors, you can install with:
sudo make install
-
solipp
; pd-test obj 0 0 r bnag, obj 0 100 unsig~, connect 0 0 1 0; bnag bang
-
solipp
@differencetones you can just parse $0 as an argument to clone like this:
[clone myabstraction 16 $0]
To refer to $0-grain in the parent, use [tabread4~ $2-grain] inside your abstraction ($1 is the number of the clone instance) -
solipp
@bocanegra http://www.willpirkle.com/Downloads/AN-4VirtualAnalogFilters.2.0.pdf is a good read. I translated the TPT laddder filter to pd in the [pp.ladder~] object in audiolab (you can download it with deken). Here is a version with an outlet for each pole and the "analog clipper" from above : TPT-ladder.pd
Another solution is [bob~] of course : https://github.com/pure-data/pure-data/blob/master/extra/bob~/bob~.c -
solipp
little note: your filter does not resonate at the cutoff frequency.
top: how it should be, bottom: how it is
now, solve this
-
solipp
@nicnut you can do something like this:
Edit: of course, if you need to translate from signal to control rate, threshold~ is the solution.
Edit: better use -~: -
solipp
@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. -
solipp
there was a short conversation about this on the mailing list:
https://www.mail-archive.com/pd-list@iem.at/msg58775.htmlIn general, I think questions about potential bugs or the internal workings of pd are better asked on the mailing list or as an issue on github.