[BUG] Stereo state is reset to Mono after opening the plugin window

[whitespace-rebel]

Hello everyone,

while using the BYOD plugin I discovered a bug.
BYOD is resetting the Stereo/Mono state back to Mono everytime I reopen the BYOD window.
How to reproduce:

1. Set the plugin to work in stereo mode
2. Close plugin window
3. Reopen plugin window
4. Notice that the Stereo/Mono mode was reset to Mono

This bug is not present in the 1.0.0 version. So it is a regression.
This bug is present in 1.1.0 and newer.

My system:
Debian Gnu/Linux AMD64
AMD APU
Host: Renoise
Plugin: BYOD vst3

Best Regards

[dcallea]

This also happens with the Stereo Splitter/Merger Tools. When setting them to Mid/Side mode and closing and reopening the plugin, they will be in Left/Right mode again.

[jatinchowdhury18]

Screen.Recording.2025-03-02.at.12.57.49.PM.mov

Sorry it's taken me so long to get back to this! I did some testing today in Bitwig Studio with both the VST3 and CLAP plugin formats. At the moment, I haven't been able to re-create these issues.

Would it be possible to test with the latest nightly build to confirm if this issue is still happening in the most recent build? If there's any other info that you could share about re-producing the bug, that would be very useful as well.

I'm travelling at the moment, but I can test in Renoise on Windows when I get home. Unfortunately, I don't have a Linux+Renoise setup that I can test with.

[whitespace-rebel]

I tested the nightly version. It is affected by this bug, too.
I see you are using OSX. There is a demo version of Renoise for testing here:
https://www.renoise.com/download

It is really simple to install (at least on Linux; it's just a folder to extract).
Hopefully it is reproducible on OSX or Windows. If not it is probably specific to the Linux build.

[whitespace-rebel]

Hmm, the nightly version I tested was 1.3.1 but in the video you are using 2.0.0

[jatinchowdhury18]

Hmm, I haven't been able to re-produce the bug in Renoise on Windows either.

The version was showing as 2.0.0 just because I was using a local build, and had happened to change the version number so that I could test something else.