I was not reading this for a few weeks. However I read the mailing list and the answers here and I'm a bit shocked that there are some "magical" numbers limiting the filters. It's even more weird that that numbers are not documented anywhere. Why is the [lop~] not limited?

Something practical to find a workaround:
Edit: Okay I found the patch from Katja Vetter in the Mailing list. That one is working.
I would like to use a sawtooth or square oscillator (many harmonics) in combination with a highpass filter to create a simple timbre effect. Using the limited [hip~] does not quite down the sound at all. So is it possible to build a "working" [hip~] alternative using PD-Vanilla only? Patch any one?

Thanks in advance!

Thanks for the confirmation.

Bugged PD-Extended Version: 0.43.4
Working PD-Vanilla Version: 0.45.4

I will report this bug to the PD-Extended Devs.

FYI: http://sourceforge.net/p/pure-data/bugs/1187/

Hello again,

I tested this case using some independent computers with different configurations and one mac.

First windows pc: Bandpass and highpass does not work.
Second windows pc: works fine
Third windows pc: Does not work
Mac: Works fine

Update:
I sorted out, what was going wrong: Using the zipball of PureData Vanilla does not produce failures on any of the tested systems. So it seems like a bug in the PureData-Extended Installation.

Heya folks,

Iam using puredata vanilla to develope a mobile app with libpd. I dont use any externals from PD Extended,

Playing with the [lop~] [bp~] and [hip~] filter I recognized some strange behaviour. The lowpass is working well. But the highpass filter does not work for me. Filtering a [pink~] signal with [hip~ 20000] does not filter the signal like i would expect. Look at the following images illustrating the problem. Iam using a patch with 4 serial highpass filter with the same input frequency. Until 6000Hz everything is fine, but then things do not work as anticipated. Using a [noise~] instead of [pink~] makes the filter even more impractical.
Maybe Im totally wrong and thats the normal way it should work?

The Test Patch: hip-test.pd

0Hz Filter:
6000Hz Filter:
20000Hz Filter

Thanks in advance!

Edit: I have been playing around with the [bp~] filter and noticed some strange behaviour, too. Until 13kHz everything is working as expected. However cut-off frequencies above this value are not working anymore and the cut-off will still stay at 13kHz. The [vcf~] is working fine and it does what it is meant to do.

Thats's perfectly working. Thanks!

One more question: What is the difference to the [edge~] object? Doesn't they do the same?

Heya,

I'm new to the pd forums and I have a question:

I'm using [edge~] to register zero crossings of a [osc~] and to trigger bangs dynamically.
Because I want to use that patch with libpd, I was wondering, if there is any way to get this working just using vanilla pd elements?

Thanks in Advance: 42