# Update the entire Synth filter section

**URL:** <https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154>\
**Category:** Synth\
**Created:** [January 16, 2026, 7:15pm UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154 "2026-01-16T19:15:39Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![neurononeuro](https://backstage.polyend.com/user_avatar/backstage.polyend.com/neurononeuro/32/4971_2.png) [@neurononeuro](https://backstage.polyend.com/u/neurononeuro)\
**Post date:** [January 16, 2026, 7:15pm UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/1 "2026-01-16T19:15:39Z")

</div>

Polyend,

We just got the DIRT section added to the synth, and it is just spectacular with all of its various ways of modulating the sound. But, it’s only on the DIRT synth oscillators. It’s only got lowpass filters.

I’m listening to all the wonderful distortions it can create, and am wondering why it can’t be on the DWA engine? Or the WAVS, WTFM, GRAINS, etc.

I’m kind just wondering if a rewrite of the synth’s oscillator/filter section of the OS might be something to consider. Each synth has different filters available, and some would be great on other parts of the synth’s oscillator section - but we don’t have ‘em. We also don’t have the DIRT modulation system - freakin’ incredible sounds to be had there.

Each synth engine really should have access to all of these filter/modulation options, because the sound production would be even greater. The DWA synth, could totally use the saturation, redux, bit crush, sin/+sin, and rectify effects - all of them, really. The DIRT engine could use a bandpass or high-pass filter.

---

<div class="post-metadata">

**Author:** ![foymaster](https://backstage.polyend.com/letter_avatar_proxy/v4/letter/f/e495f1/32.png) [@foymaster](https://backstage.polyend.com/u/foymaster)\
**Post date:** [January 26, 2026, 6:09pm UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/2 "2026-01-26T18:09:40Z")

</div>

+1 for this!

---

<div class="post-metadata">

**Author:** ![briannhinton](https://backstage.polyend.com/letter_avatar_proxy/v4/letter/b/9fc29f/32.png) [@briannhinton](https://backstage.polyend.com/u/briannhinton)\
**Post date:** [January 26, 2026, 7:10pm UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/3 "2026-01-26T19:10:38Z")

</div>

I am of a different mind. My perspective is that each engine is intended to simulate a specific synth, or is a new concept. If everything had the same filters, modulation, etc. each engine ends up losing its focused character.

---

<div class="post-metadata">

**Author:** ![kensoliva](https://backstage.polyend.com/user_avatar/backstage.polyend.com/kensoliva/32/6059_2.png) [@kensoliva](https://backstage.polyend.com/u/kensoliva)\
**Post date:** [January 26, 2026, 7:32pm UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/4 "2026-01-26T19:32:40Z")

</div>

Has Polyend shared which specific synth(s) inspired each engine, where applicable? I’m not very knowledgeable about synthesizer history, so I would be curious to know and learn more about them.

---

<div class="post-metadata">

**Author:** ![Dann](https://backstage.polyend.com/user_avatar/backstage.polyend.com/dann/32/2287_2.png) [@Dann](https://backstage.polyend.com/u/Dann)\
**Post date:** [January 26, 2026, 11:40pm UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/5 "2026-01-26T23:40:25Z")

</div>

Hey there @kensoliva, welcome to backstage! Great to have you join us here 🙂

There are no specifics mentioned, but reading between the lines, I think you could break it down like this.

- ACD - Acid Mono synth. This would be in the realms of TB-303 and to an extent the SH-101.
- FAT - The mention of flavors of ladder filters leans us towards the Minimoog
- VAP - Poly Analog. Think Oberheim SEM system and Korg Polysix
- PHZ - I’d put my money on it being inspired by the Casio CZ line

The rest on the menu are pretty unique synths to Polyend as far as I am aware. WTFM, DWA and Dirt are really innovative synths. It’s pretty impressive if they were indeed cooked in the Polyend oven 🍞 🎹

---

<div class="post-metadata">

**Author:** ![Dann](https://backstage.polyend.com/user_avatar/backstage.polyend.com/dann/32/2287_2.png) [@Dann](https://backstage.polyend.com/u/Dann)\
**Post date:** [January 26, 2026, 11:57pm UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/6 "2026-01-26T23:57:27Z")

</div>

Saying the following as pure speculation as I have zero insider knowledge on the topic.

I don’t think we will see major developments of any of the previous synth engines for a couple of reasons;

- Backwards compatibility between older projects
- CPU limitations

Those are the 2 logical conclusions. The other concern I have is that each synth sounds quite unique to one another. Adding multiple features from other engines risks them sounding more and more the same.

Don’t get me wrong; I would personally love to see this as well, but I’m doubtful it will happen based on my points above.

---

<div class="post-metadata">

**Author:** ![neurononeuro](https://backstage.polyend.com/user_avatar/backstage.polyend.com/neurononeuro/32/4971_2.png) [@neurononeuro](https://backstage.polyend.com/u/neurononeuro)\
**Post date:** [January 27, 2026, 12:01am UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/7 "2026-01-27T00:01:29Z")

</div>

That is a relevant perspective! While I understand it, with the full filter/drive section, one could just match the oscillator section to the particular filter selection they wanted, and if they wanted something else, they could have that as well.

It would require a bit of learning what each osc/filter section is for (oscillator type/filter model, etc.), but would really open up the architecture to more options. That drive section, c’mon! It’s awesome and would sound excellent on all sources! 🙂

---

<div class="post-metadata">

**Author:** ![neurononeuro](https://backstage.polyend.com/user_avatar/backstage.polyend.com/neurononeuro/32/4971_2.png) [@neurononeuro](https://backstage.polyend.com/u/neurononeuro)\
**Post date:** [January 27, 2026, 12:07am UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/8 "2026-01-27T00:07:06Z")

</div>

As I mentioned to @briannhinton , I do understand this. I’d be willing to concede that the physical modeling synth, the DWA, the GRAIN, and the WAVS synth would be the ones that most benefit from having more filters/drive. They are pretty original synths, and don’t sound like anything else to me.

Also, the GRAIN synth would be even more excellent if the grains were capable of having their sample rate adjusted - like the Clouds algorithm. This would allow for longer grains and some really nice woven granular material - threads instead of grains.

---

<div class="post-metadata">

**Author:** ![Dann](https://backstage.polyend.com/user_avatar/backstage.polyend.com/dann/32/2287_2.png) [@Dann](https://backstage.polyend.com/u/Dann)\
**Post date:** [January 27, 2026, 12:08am UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/9 "2026-01-27T00:08:41Z")

</div>

> [@neurononeuro](#):
>
> That drive section, c’mon! It’s awesome and would sound excellent on all sources! 🙂

100% agree!

> [@neurononeuro](#):
>
> Also, the GRAIN synth would be even more excellent if the grains were capable of having their sample rate adjusted - like the Clouds algorithm

250% agree!!!

@Polyend, an idea for the next iteration of the Synth; All the different modules from all the different synths within a modular engine. That would be BADASS!!

---

<div class="post-metadata">

**Author:** ![neurononeuro](https://backstage.polyend.com/user_avatar/backstage.polyend.com/neurononeuro/32/4971_2.png) [@neurononeuro](https://backstage.polyend.com/u/neurononeuro)\
**Post date:** [January 27, 2026, 12:10am UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/10 "2026-01-27T00:10:52Z")

</div>

> [@Dann](#):
>
> @PolyendPolyendPolyendPolyend, an idea for the next iteration of the Synth; All the different modules from all the different synths within a modular engine. That would be BADASS!!

🤩

The grains could be sparse, and then they would be considered a ‘tapestry’ of sorts. Full phrases would be being sampled for the longer grains. Lofi and eerie!

---

<div class="post-metadata">

**Author:** ![kensoliva](https://backstage.polyend.com/user_avatar/backstage.polyend.com/kensoliva/32/6059_2.png) [@kensoliva](https://backstage.polyend.com/u/kensoliva)\
**Post date:** [January 27, 2026, 3:32am UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/11 "2026-01-27T03:32:59Z")

</div>

Thank you. That gives me some stuff to research which I think will help me better understand how I might approach those synth engines from a sound design perspective.

---

<div class="post-metadata">

**Author:** ![Lizard-of-Oz](https://backstage.polyend.com/user_avatar/backstage.polyend.com/lizard-of-oz/32/4267_2.png) [@Lizard-of-Oz](https://backstage.polyend.com/u/Lizard-of-Oz)\
**Post date:** [January 30, 2026, 11:02am UTC](https://backstage.polyend.com/t/update-the-entire-synth-filter-section/24154/12 "2026-01-30T11:02:40Z")

</div>

> [@neurononeuro](#):
>
> That drive section, c’mon! It’s awesome and would sound excellent on all sources! 🙂

There is already a feature request relevant to this discussion:

> [@Add some Grit: Overdrive/Distortortion/Bit- and Sample-Rate-Reduction](https://backstage.polyend.com/t/add-some-grit-overdrive-distortortion-bit-and-sample-rate-reduction/16291):
>
> What is the problem? All the Synth can distort is the phase, so it sounds relatively soft and smooth overall. As a user with a wide range of emotions, I’d like to add some grit to my sound, so that I can better express myself through my music. What should this feature achieve? Fuck up every sound easily, and a lot, too, if desired. Some considerations: Sample Rate Reduction and Bit Rate Reduction are simple effects, and are best placed before a filter, because then the filter can be used to …
