# "FL Studio" strikes again - VST2 doubling signal level - solved

**URL:** <https://iplug2.discourse.group/t/fl-studio-strikes-again-vst2-doubling-signal-level-solved/679>\
**Category:** Uncategorized\
**Created:** [21 July 2022 18:30 UTC](https://iplug2.discourse.group/t/fl-studio-strikes-again-vst2-doubling-signal-level-solved/679 "2022-07-21T18:30:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RexMartin2](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RexMartin2](https://iplug2.discourse.group/u/RexMartin2)\
**Post date:** [21 July 2022 18:30 UTC](https://iplug2.discourse.group/t/fl-studio-strikes-again-vst2-doubling-signal-level-solved/679/1 "2022-07-21T18:30:47Z")

</div>

More issues with FL Studio (the most troublesome DAW I have come across).

I just discovered that the VST **2** version of one of my plugins produces a 6dB (2x) gain increase when inserted on a track in FL Studio 20. The VST **3** version of the plugin does _not_ do this.

I have not seen this behavior in any other DAW.

I don’t have any idea what is causing this or how to fix it. Everything looks fine/correct when running in debugger. What could possibly be causing an exact level doubling like this? Any ideas?

---

<div class="post-metadata">

**Author:** ![RexMartin2](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RexMartin2](https://iplug2.discourse.group/u/RexMartin2)\
**Post date:** [22 July 2022 13:55 UTC](https://iplug2.discourse.group/t/fl-studio-strikes-again-vst2-doubling-signal-level-solved/679/2 "2022-07-22T13:55:04Z")

</div>

Found the problem here. This particular plugin provides 3 stereo output buses. It appears that FL Studio can’t handle that properly and is mixing all three output buses together onto the Main bus. The immediate solution is to turn off output buses 2 and 3 in the FL Studio plugin settings options OR use the VST3 version.

The VST3 version of the plugin shows up in FL Studio plugin options with bus 2 and 3 already turned off.

Will look into conditional code to “fix” this in the plugin but it appears to be caused by a bug in FL Studio.
