PDA

View Full Version : Bessel filter implementation

Tale
03-21-2011, 02:51 AM
Hi,

I have added a low-pass Bessel filter (besselfilter.h) implementation using matched Z-transform to my WDL repository (http://www.taletn.com/WDL.git). I have extracted this implementation from from the source code of mkfilter (http://www-users.cs.york.ac.uk/~fisher/mkfilter).

I have divided the implementation into three classes: one for calculating coefficients (WDL_BesselFilterCoeffs), one for the actual filter (WDL_BesselFilterStage), and a third class combining both (WDL_BesselFilter).

Here are a couple of (pseudo) code examples of its use:

Example #1:
// 8th order anti-alias filter
#define WDL_BESSEL_FILTER_ORDER 8
#include "besselfilter.h"

int oversampling = 8;

WDL_BesselFilterCoeffs bessel;
WDL_BesselFilterStage filter;

bessel.Calc(0.5 / (double)oversampling);
filter.Reset();

for (int i = 0; i < nFrames; ++i)
{
filter.Process(inputs[0][i], bessel.Coeffs());
outputs[0][i] = filter.Output();
}

Example #2:
#include "besselfilter.h"

int order = 4;
int oversampling = 8;

WDL_BesselFilterStage filter[2];
filter[0].Reset();
filter[1].Reset();

WDL_BesselFilterCoeffs coeffs;
coeffs.Calc(0.5 / (double)oversampling, order);

for (int i = 0; i < nFrames; ++i)
{
filter[0].Process(inputs[0][i], &coeffs);
filter[1].Process(filter[0].Output(), &coeffs);
outputs[0][i] = filter[1].Output();
}

Example #3:
#include "besselfilter.h"

int order = 8;
int oversampling = 8;

WDL_BesselFilter bessel;
bessel.Calc(0.5 / (double)oversampling, order);
bessel.Reset();

for (int i = 0; i < nFrames; ++i)
{
bessel.Process(inputs[0][i]);
outputs[0][i] = bessel.Output();
}

junioreq
03-21-2011, 03:01 AM
Tale this is Great! But the first thing that popped out was the oversampling.. Could this be "modded" to work on its own oversampling without the filter? Seems oversampling for distortions etc is just way over my head at the moment. Thanks for the class though, its so nice to have these things built in and ready for use.

~Rob.

olilarkin
03-21-2011, 04:55 AM
wow, thanks for this tale!

rob - the filter is part of the oversampling - you need to filter out frequencies above the nyquist when up or down sampling

Tale
03-26-2011, 03:22 PM
I tried to include besselfilter.h in an Xcode project today, but my MacBook wouldn't build it because _hypot is supposed to be called hypot (although Microsoft seems to disagree). Anyway, this has now been fixed (see my Git repository (http://www.taletn.com/WDL.git)).

Tale
09-18-2011, 06:38 AM
I have added the option to zero denormals in the output of the Bessel filter. I have also added an example using this filter for oversampling:

mAntiAlias.Calc(0.5 / (double)mOversampling);

...

double sample = <input sample>;
double output;

for (int j = 0; j < mOversampling; ++j)
{
// Upsample
if (j > 0) sample = 0.;
mUpsample.Process(sample, mAntiAlias.Coeffs());
sample = (double)mOversampling * mUpsample.Output();

...

// Downsample
mDownsample.Process(sample, mAntiAlias.Coeffs());
if (j == 0) output = mDownsample.Output();
}

<output sample> = output;

The complete (working) example can be found in WDL/IPlug/Example/Distortion in my WDL Git repository.

olilarkin
10-20-2011, 01:42 AM
Do you get a dc offset/clicks when you change the drive amount in your example?

Tale
10-20-2011, 04:55 AM
Do you get a dc offset/clicks when you change the drive amount in your example?
Yes. Adding a small DC offset and then removing it again is part of the distortion algorithm. I remove the DC offset again by sending the downsampled signal through a high-pass filter, which causes the clicks. I guess it would be better to simply substract the distorted DC offset:

// Distortion
if (WDL_DENORMAL_OR_ZERO_DOUBLE_AGGRESSIVE(&sample))
sample = mSilence;
else
sample = mGain * fast_tanh(mDC + mDrive * sample);

sample -= mSilence;

Of course this can be further optimized, and the high-pass filter can then be removed altogether. It will still use a tiny bit more CPU than the original version, but there will be no more clicks.

EDIT: I have updated the distortion example in my Git repository (currently on the "next" branch).

Mich
11-06-2011, 04:30 AM
I tried to include besselfilter.h in an Xcode project today, but my MacBook wouldn't build it because _hypot is supposed to be called hypot (although Microsoft seems to disagree).

It is supposed to be called hypot() according to the ANSI C99 standard (http://pubs.opengroup.org/onlinepubs/007908799/xsh/hypot.html).
But Microsoft is somewhat confused about it.

onqel
07-24-2012, 02:55 AM
I tried this on one of my high gain ampsims, it can't compete with my original polyphase approach unfortunately (for 2X/4X oversampling), aliasing all over the place.. I tried order up to 10

Tale
07-24-2012, 06:48 AM
Yeah, polyphase should surely give you better quality, but the Bessel filter is probably less CPU costly (I hope so anyway). I use 6 consecutive 4th order Bessel filters with 64x oversampling to suppress aliases on naive waveforms, with virtually no audible aliasing. Then again, polyphase might also work just as well in my specific case, but I haven't been able to really wrap my head around it yet.

random_id
11-30-2012, 07:44 AM
Thank you for your oversampling Distortion sample. I am trying to implement oversampling in my own plugin and I have two questions (due to my extremely small math/dsp brain).

1. When changing oversampling from 4X, 8X, 16X, etc., should you also change the WDL_BESSEL_FILTER_ORDER? In your example, you have this set to 8, and oversampling set to 8X. I think this determines the filter order and would not be related to the oversampling.

2. You mention DC offset. Is this inherent to the oversampling process? I know that you solved it in your example by subtracting out a similar value.

Thanks

Tale
11-30-2012, 08:18 AM
1. When changing oversampling from 4X, 8X, 16X, etc., should you also change the WDL_BESSEL_FILTER_ORDER? In your example, you have this set to 8, and oversampling set to 8X. I think this determines the filter order and would not be related to the oversampling.
The filter order and oversampling are not related. In my example both the oversampling and the filter order happen to be 8, but you could just as well use a filter order of 8 with 16x oversampling (or whatever other combination suits your purpose).

2. You mention DC offset. Is this inherent to the oversampling process? I know that you solved it in your example by subtracting out a similar value.
The DC offset is part of the distortion algorithm, not the oversampling process.

random_id
11-30-2012, 08:40 AM
Thanks for responding to my ignorance.