
A new polezero calculator
An JavaScript remake of the old Javabased polezero placement applet—visit that page for tips on polezero locations for standard biquads. The main additions are input fields for precision polezero placement, and an option to display the response with a log frequency scale.
The basic idea is that poles blow, zeros suck. Think of poles as controlling a frequencydependent feedback or resonance—the impulse response of a pole inside the unit circle decays, while one outside is like runaway feedback (think of a mic feeding back into a loudspeaker). A pole on the unit circle gives a sustained oscillation (but watch out for numerical errors—keep your poles inside the unit circle, typically). Zeros absorb a particular frequency; when on the unit circle, they absorb the corresponding frequency completely.
So, poles push the frequency response up around their corresponding frequency, and zeros pull down around theirs. Keep in mind that the frequency response graph is normalized, just as the filter coefficients are. So, while a pole pushes up the response, it appears as though all other frequencies are being pushed down instead. Of course, normalization is important in practical application, but be aware of it when visualizing how poles and zeros interact.
I found a very nice web app showing interactive filter design with direct visualization in frequency domain and zdomain ( poles and zeros ) :
http://www.micromodeler.com/dsp/
This is intended for embedded dsp applications, but it’s still a incredibly useful pedagogical material.
Nice! Thanks
Hi there,
Very nice applet.
Any chance you could add the phase graph too? i.e.: atan(Im(H)/Re(H)). I’d like to get a better intuitive idea of how that works.
(And then, for a future version, could we manually select the number of poles & zeros? Add support for allpass filters… :o)
Many thanks,
Richard.
Hi Richard. I’ve thought many times about some of these features, and as you noted, one leads to another, and the only sound solution would be to go into the business of a making a commercial filter design software package, and I’d be heading far off track from what I’m trying to do…
The phase plot is the most obvious, but in the end we’ve got a second order filter, for which you can look up the unexciting phase characteristics elsewhere, and they are simply an accepted byproduct of this type of filter. (That is, the parametric EQs in your analog mixing console and their digital equivalents in your DAW do the same thing—do you demand to see their phase response before purchasing? No, because you accept what that type of filter gives you.) Now, it would be very helpful as you add some of the other things you mentioned—more poles and zeros, all pass filter…then you’re back in the business of making a filter design package. 😉
Nigel
This tool seems to be getting the signs for b1 and b2 the wrong way round, although that depends on how you write your equation;
In your other material you write y[n] = …. – b1 * y[n1] – b2 * y[n2]
In that case the signs are wrong, or rather, inconsistent with how you write the direct forms.
Thank you for catching that, Anthony. While I was at it, I improved the log tick value scaling. I also took the opportunity to restore continuous update on slider movement (broken when Safari and Chrome fixed their errors in HTML5 interpretation).
Clearest description I’ve ever read of poles and zeroes in the real world. Excellent!
To get a more complete example it would be great is the cut off frequency would be part of the parameters. It would also be very nice if the frequency on the 3dB point of the graph would be readable in some way.
Nevertheless, thanks for the great explaination!
Good idea, Matthijs. I’ll keep that in mind for the next time I have a chance to improve things.
Here “a” coefficients represents numerator, right? In most sources b is a numerator.
Hi Eugene—asked and answered a few times in comments on the site, but since you bring it up, I’ll put together a short article explaining the choice. Short version: In the internet age, I don’t doubt that binthenumerator has become most common. But I’m not going to edit articles going back to 2003, so yes, a in the numerator here 😉