# LadderFilter artefacts

**URL:** <https://forum.juce.com/t/ladderfilter-artefacts/34262>\
**Category:** General JUCE discussion\
**Created:** [July 7, 2019, 10:11pm UTC](https://forum.juce.com/t/ladderfilter-artefacts/34262 "2019-07-07T22:11:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![martinrobinson-2](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/martinrobinson-2/32/630_2.png) [@martinrobinson-2](https://forum.juce.com/u/martinrobinson-2)\
**Post date:** [July 8, 2019, 7:34am UTC](https://forum.juce.com/t/ladderfilter-artefacts/34262/2 "2019-07-08T07:34:39Z")

</div>

Pretty sure it’s this classic pitfall:

> [@\#1 most common programming mistake that we see on the forum](https://forum.juce.com/t/1-most-common-programming-mistake-that-we-see-on-the-forum/26013):
>
> This post is here so that we have something we can link to when this same issue comes up, because the JUCE team is getting very bored of spending time replying again and again to the same damned problem! This isn’t a JUCE bug - there’s nothing we can do in our codebase that would stop people making it, which makes it painful for us to watch beginner after beginner come along and fall headfirst into the same trap! It’s also understandable that people will post a new topic when they hit it, beca…

---

_[View the full topic](https://forum.juce.com/t/ladderfilter-artefacts/34262)._
