i3wm compatibility issues and closing linvst processes after app close

[fourstepper]

Hello,

I've reported this bug to i3wm developers, but understandably they do not want to support a proprietary app (Bitwig) at all, so perhaps turning to you could yield some results, even though my setup might be quite esoteric

I have two bugs to report:

1) Closing plugin results in Bitwig audio engine crash under i3wm (not present for any native plugins or under GNOME - I have tested this both with JACK and PulseAudio backends.

Steps to repro: 1) Open any Windows VST plugin in Bitwig (tested FabFilter plugs and Addictive Drums 2) 2) Hit play (playback start just fine) 3) Close the plugin (either using the Bitwig GUI or the $mod+Shift+Q combination in I3wm 4) Playback should stop and isn't startable again (if not, repeat the process 2-3 times)

If you have some time, I would really appreciate if you looked into this :)

Furthermore, after Bitwig close (in both GNOME and i3) some processes keep running in the background

These are:

Z:\usr\bin\lin-vst-servertrack.exe.so C:\windows\system32\winedevice.exe C:\windows\system32\explorer.exe /usr/bin/wineserver

Let me know if there is anything else you might need to help you fix any of the above bugs. I will be very happy to help.

Thank you for your good work!

[osxmidi]

Hello,

I've reported this bug to i3wm developers, but understandably they do not want to support a proprietary app (Bitwig) at all, so perhaps turning to you could yield some results, even though my setup might be quite esoteric

I have two bugs to report:

1. Closing plugin results in Bitwig audio engine crash under i3wm (not present for any native plugins or under GNOME - I have tested this both with JACK and PulseAudio backends.

Steps to repro:

1. Open any Windows VST plugin in Bitwig (tested FabFilter plugs and Addictive Drums 2)

2. Hit play (playback start just fine)

3. Close the plugin (either using the Bitwig GUI or the $mod+Shift+Q combination in I3wm

4. Playback should stop and isn't startable again (if not, repeat the process 2-3 times)

If you have some time, I would really appreciate if you looked into this :)

Furthermore, after Bitwig close (in both GNOME and i3) some processes keep running in the background

These are:

Z:\usr\bin\lin-vst-servertrack.exe.so C:\windows\system32\winedevice.exe C:\windows\system32\explorer.exe /usr/bin/wineserver

Let me know if there is anything else you might need to help you fix any of the above bugs. I will be very happy to help.

Thank you for your good work!

Another user had a similar problem and we worked out a workaround https://github.com/osxmidi/LinVst/issues/138

It seems like the problem is that LinVst wrapped plugins need to be set to run as Individually in Bitwig's plugin settings.

But, the plugin needs to appear in Bitwigs plugin list before it can be set to run Individually.

LinVst was preventing that for some plugins due to some changes and now I've added a workaround that is in the LinVst Bitwig Makefiles.

Makefile-Bitwig for 64bit only vst's

Makefile-64-32bit-Bitwig for 64bit and 32bit vst's

Then the LinVst-Bitwig version will (hopefully) allow the plugins to appear so that they can be set to be run as Individually and then a reboot is probably needed, and after that the plugin should be (hopefully) ok, and the run Individually (and reboot) needs to be done for each newly added plugin.

For some reason Bitwig and Wine clash unless the plugins are set to run Individually in Bitwig's plugin settings.

The Bitwig/Wine clash results in errors like the ones you have posted.

There are some details here https://github.com/osxmidi/LinVst/blob/master/Bitwig/Notes

[fourstepper]

Thank you for your reply. I will test this all today and will report back. I've run the plugins "Together" until now and everything worked in other DEs except i3, which is why I am confused

[fourstepper]

Hi again, not a solution per se, but I have "fixed" this by switching to Sway on Wayland, where this problem is not present. Still weird, as I've run GNOME on X.