I have written a program for linux, that anybody who is interested in the PD code base might find
useful .. basically a 'C' function tracer. PD vanilla has more than 800 functions alone! It's often
difficult to comprehend as functions are often called indirectly for several reasons. It has a gui that's
written in tcl/tk as is PD, and the tracing does not need any special kernel mods (uses ptrace system call)
Start up (as in the README), and one can put objects, turn on DSP, click 'bangs' etc. and then stop the tracing and see what's been going on
While developing my basspitch~ external, I found problems which I put down to interference from harmonics from higher pitches. In any case, I decided to make a multi-speed sampler that could slow down the fft analysis of the source.
In for a penny, in for a pound, and so I tried to achieve acceptable sound alongside..
The synchronisation presented problems for a while, as the sound and analysis had different criteria.
It's coming on, though..
Any criticism welcome
I'm fairly new to PD, and I noticed that fidle~, sigmund~ & friends weren't able to deal with bass pitch.
As I'm a glutton for punishment , I decided to have a go .. seemed I needed to make an external, and even that was prety tight.
Anyway, here is the compiled linux version..
Anybody who enjoys graphs might like to fiddle with this one..
It demonstrates that a unit-impulse signal input to a filter, outputs the impulse-response..
..a brick-wall filter giving us the sinc function.
Only needs vanilla
I have a patch which will stream raw 16bit data into Pd from any program running on Linux.
For other Os, (such as Mac, Win), I have included the 'C' source code, so you're welcome to hack it.
There is a README in the zip file, which should get you started. Any questions?
I'm wondering why it is that the output from bp~ continues for some seconds after the input signal to it is removed..
[ at least, it does on my linux box with pd 0.43 ]
[ osc~ 440 ]
| / [100\
| / /
| / /
[ bp~ ]
[ env~ ]
After disconnecting the osc~, the number box shows a slow decline in rms amplitude.
What algorithm is being used? It seems to get more unstable as "Q" increases .. is that how it should be?
Would there be any other eqivalent filter that does NOT exhibit this behaviour?
I'm relatively new to PD, and am enjoying it
I notice that fft examples have been condensed into the audio examples in 0.43..
perhaps somebody can expliain to me how to use 'overlap' in the 'I02.Hann.window.pd' example
I understand that 'block 512' should be changed to 'block 512 4'
What else needs to change? The hanning window doesn't seem to look right?
Thanks .. I'd like to understand about 'windowing' more thoroughly.
Perhaps somebody could suggest a 'site ref' on this topic .. I've been googling for a while, and have still not got to the bottom of it.
Is this the sort of behaviour you were looking for?
..what I'm looking for is a document 'saying what "text file arguments" makes what in a given object'.
Haven't seen one.
I might misunderstand you, but if you click on the 'bang' message on that patch, and look at the console, you can see what arguments (message) produces what on the new canvas.
#X msg 191 213 rewind
..produces a message box (object) at x coord 191 y 213 with the 'class' rewind
Sorry if that's not what you meant