# Cubase Distortion plugin Oversampling

**URL:** <https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039>\
**Category:** Cubase\
**Created:** [May 9, 2026, 1:56am UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039 "2026-05-09T01:56:22Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![AeroV](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@AeroV](https://forums.steinberg.net/u/AeroV)\
**Post date:** [May 9, 2026, 1:56am UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/1 "2026-05-09T01:56:23Z")

</div>

Hi, I would like to know if anyone else can observe a very obvious loss of low end when enabling the Oversampling in the stock Distortion plugin ?

I’m not doing anything more than just toggling the Oversampling on.

Thank you.

---

<div class="post-metadata">

**Author:** ![AeroV](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@AeroV](https://forums.steinberg.net/u/AeroV)\
**Post date:** [May 10, 2026, 2:44am UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/2 "2026-05-10T02:44:53Z")

</div>

Sooo… no one cares ? lol

---

<div class="post-metadata">

**Author:** ![Michael\_Ill](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@Michael\_Ill](https://forums.steinberg.net/u/Michael_Ill)\
**Post date:** [May 10, 2026, 9:38am UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/3 "2026-05-10T09:38:00Z")

</div>

Yes, confirmed same issue here on Win11. Noticeable bass cut with oversampling on.  
Does not happen with other plugin like Distroyer.

Could you please add the ‘Issue’ tag to your thread.,  
thanks

---

<div class="post-metadata">

**Author:** ![Johnny\_Moneto](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/johnny_moneto/32/329861_2.png) [@Johnny\_Moneto](https://forums.steinberg.net/u/Johnny_Moneto)\
**Post date:** [May 10, 2026, 11:04am UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/4 "2026-05-10T11:04:41Z")

</div>

This is white noise at -3dBFS.  
Distortion without Oversampling, Tone set to 10.0:

 ![grafik](https://europe1.discourse-cdn.com/steinberg/original/4X/e/6/f/e6fee75f2208b1c85fa94f9599ec443343db07f0.jpeg)

Distortion with Oversampling, Tone set to 10.0:

 ![grafik](https://europe1.discourse-cdn.com/steinberg/original/4X/a/0/f/a0f028ee06b207c542d1618b8ce7b07184228c62.jpeg)

You can see the low-shelving and the hi-cut.

---

<div class="post-metadata">

**Author:** ![Johnny\_Moneto](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/johnny_moneto/32/329861_2.png) [@Johnny\_Moneto](https://forums.steinberg.net/u/Johnny_Moneto)\
**Post date:** [May 10, 2026, 11:19am UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/5 "2026-05-10T11:19:09Z")

</div>

All we can do here is to let other users know what is happening with this particular plugin.  
Steinberg cannot “fix” existing plugins as that would possibly alter the sound of existing projects. They can only ever add functionality to plugins. In this case they could chose to offer an alternative oversampling algorithm, additionally to the current one. Or maybe the non-oversampled version needs the lowshelf to be added.

---

<div class="post-metadata">

**Author:** ![diegoalejo15](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@diegoalejo15](https://forums.steinberg.net/u/diegoalejo15)\
**Post date:** [May 10, 2026, 12:16pm UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/6 "2026-05-10T12:16:00Z")

</div>

I never in my life used this plugin…there are at least a hundred better distortion plugins, as a workaround you could insert it in a FX track so you can blend with original signal and still have the low end.

---

<div class="post-metadata">

**Author:** ![AeroV](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@AeroV](https://forums.steinberg.net/u/AeroV)\
**Post date:** [May 10, 2026, 8:30pm UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/7 "2026-05-10T20:30:18Z")

</div>

I don’t think I know how to do that. Clicking around couldn’t find a way to edit the title or to add a tag. Any help welcome.

---

<div class="post-metadata">

**Author:** ![AeroV](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@AeroV](https://forums.steinberg.net/u/AeroV)\
**Post date:** [May 10, 2026, 8:30pm UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/8 "2026-05-10T20:30:56Z")

</div>

This is hilarious if true.

---

<div class="post-metadata">

**Author:** ![Johnny\_Moneto](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/johnny_moneto/32/329861_2.png) [@Johnny\_Moneto](https://forums.steinberg.net/u/Johnny_Moneto)\
**Post date:** [May 10, 2026, 9:40pm UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/10 "2026-05-10T21:40:39Z")

</div>

For the same reason Fabfilter releases Q2, Q3, Q4,  
Wave releases L1, L2, L3, L4

---

<div class="post-metadata">

**Author:** ![AeroV](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@AeroV](https://forums.steinberg.net/u/AeroV)\
**Post date:** [May 10, 2026, 10:00pm UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/11 "2026-05-10T22:00:14Z")

</div>

I don’t understand the parallel you’re making. Can you explain ?

---

<div class="post-metadata">

**Author:** ![Johnny\_Moneto](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/johnny_moneto/32/329861_2.png) [@Johnny\_Moneto](https://forums.steinberg.net/u/Johnny_Moneto)\
**Post date:** [May 10, 2026, 10:50pm UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/12 "2026-05-10T22:50:55Z")

</div>

All developers of plugins are facing the same problem: If there is a mistake in the sound of the plugin they cannot just fix it. Customers might have used the plugin as it is and changing the sound of the plugin changes the sound of any project the plugin was used in.  
That’s why developers create a “new” plugin, ie. the new plugin is not a replacement for the predecessor but an addition.

Steinberg went a slightly different way for their Cubase channel EQ. Instead of creating a whole new channel EQ the old algorithms are still selectable on each of the four bands (parametric 1, shelf 1). Each band allows you to chose whether you want to use the old EQ or the new EQ.

 ![grafik](https://europe1.discourse-cdn.com/steinberg/original/4X/b/7/f/b7f82319b10e1312da7cdf535e32d9e2d07654d6.png)

Something similiar could be done for Distortion.

---

<div class="post-metadata">

**Author:** ![AeroV](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@AeroV](https://forums.steinberg.net/u/AeroV)\
**Post date:** [May 10, 2026, 11:11pm UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/13 "2026-05-10T23:11:53Z")

</div>

This is absolutely irrelevant to the matter at hands. There’s a bug in a plugin. I’m mentioning it. Whether YOU use it or not doesn’t make a shred of a difference.

---

<div class="post-metadata">

**Author:** ![sam\_halabi](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/sam_halabi/32/263418_2.png) [@sam\_halabi](https://forums.steinberg.net/u/sam_halabi)\
**Post date:** [September 25, 2026, 5:10pm UTC](https://forums.steinberg.net/t/cubase-distortion-plugin-oversampling/1032039/14 "2026-09-25T17:10:45Z")

</div>

Issue Confirmed, it must be fixed !

Hope Steinberg team work on fixing this soon.
