# Linux Vst3 Reaper Bitwig **URL:** \ **Category:** Linux\ **Created:** [April 26, 2020, 4:52am UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022 "2020-04-26T04:52:25Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![JuceLinux123](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@JuceLinux123](https://forum.juce.com/u/JuceLinux123)\ **Post date:** [April 26, 2020, 4:52am UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/1 "2020-04-26T04:52:25Z")
Linux Juce Vst3 plugins seem to work ok with Linux Reaper but seem to have problems with Linux Bitwig. The Vst3 Window comes up on Bitwig but the Vst3 does not respond to mouse clicks. I tested updating the Window with some timer delayed text and it did update. Seeing that the Window text updated and that the Window does not respond to mouse clicks might suggest a focus/mouse problem. ---
**Author:** ![JuceLinux123](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@JuceLinux123](https://forum.juce.com/u/JuceLinux123)\ **Post date:** [April 26, 2020, 11:33am UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/2 "2020-04-26T11:33:43Z")
Affects plugins such as KlangFalter [https://github.com/HiFi-LoFi/KlangFalter](https://github.com/HiFi-LoFi/KlangFalter) and others. ---
**Author:** ![baconpaul](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/baconpaul/32/8403_2.png) [@baconpaul](https://forum.juce.com/u/baconpaul)\ **Post date:** [April 28, 2020, 5:27pm UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/4 "2020-04-28T17:27:31Z")
Heya! I had a similar problem with both surge (which isn’t a juce plugin and where I hand rolled the Linux vst3 event loop) and our juce plugin. I’ve been working with the bitwig team. The freeze I saw in both vst3s (which matches yours) is fixed in the dev version of bitwig I just ran and should be corrected in the upcoming 3.2 beta 4. They were happy for me to let you know this here in the forum too (I’m just an opensource programmer not a bitwig team member) If you look in your bitwig log you may see something like warning unregister unknown handler. The innards of the vst3 runloop are painful but bitwig team has fixed the thing that makes that log message. ---
**Author:** ![JuceLinux123](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@JuceLinux123](https://forum.juce.com/u/JuceLinux123)\ **Post date:** [April 29, 2020, 7:39am UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/5 "2020-04-29T07:39:51Z")
Thanks for the info. ---
**Author:** ![ed95](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ed95/32/7635_2.png) [@ed95](https://forum.juce.com/u/ed95)\ **Post date:** [April 29, 2020, 9:04am UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/6 "2020-04-29T09:04:59Z")
Interesting, thanks! I was testing this with JUCE-based VST3s and noticed that the event handler wasn’t being called for the X11 fd and it sounds like this should fix it. Do you know when this beta will be available? ---
**Author:** ![baconpaul](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/baconpaul/32/8403_2.png) [@baconpaul](https://forum.juce.com/u/baconpaul)\ **Post date:** [April 29, 2020, 11:49am UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/7 "2020-04-29T11:49:14Z")
Yeah that’s exactly what I saw in surge and then also in our juce plugin. The problem (short version) was that the VST3 api (as you know) as registerHandler( handler \*, fd ) and unregisterHandler( handler ), but bitwig was making one handler and then multiplexing internally, so if you did something that registered a new handler transiently (like initialize another xcb or something) it would unregister the same handler as for the main xcb loop. I also had some bugs in surge which had us confused for a bit but once i got those fixed with reaper and your (super duper useful) audiopluginhost we found it. I got the impression that 3.2 beta 4 will be out ‘shortly’ but I don’t have a date. So now the only thing left for me releasing vst3s of all our juce plugins automatically from our CI pipeline is [Building my VST3 with Linux and JUCE6 - couple of tiny things](https://forum.juce.com/t/building-my-vst3-with-linux-and-juce6-couple-of-tiny-things/39014/4) which I know @reuk is looking at. I am very excited! ---
**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\ **Post date:** [April 29, 2020, 12:18pm UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/8 "2020-04-29T12:18:24Z")
I added a fix for the Linux naming issue on the juce 6 branch, so VST3 plugins built with CMake on Linux should work as expected now. Please let me know if you run into any other issues. ---
**Author:** ![baconpaul](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/baconpaul/32/8403_2.png) [@baconpaul](https://forum.juce.com/u/baconpaul)\ **Post date:** [April 29, 2020, 2:06pm UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/9 "2020-04-29T14:06:20Z")
Hi @reuk Unfortunately I’m still seeing same. But it may be me! Here’s my commands ```auto git clone https://github.com/baconpaul/tuning-workbench-synth.git cd tuning-workbench-synth git checkout juce6 git submodule update --init --recursive cmake -Bbuild cmake --build build --config Release ``` That uses this mornings head of juce6 as a submodule ```auto paul@ubuntu:~/dev/cb/tuning-workbench-synth$ (cd lib/JUCE; git log | head -3) commit eeff1e61744114f9076882ceaafda30c9c684c53 Author: ed Date: Wed Apr 29 09:42:11 2020 +0100 ``` But when I look in the resulting VST3 the name of the resulting library in the package is still ‘.vst3’ not ‘.so’ ```auto paul@ubuntu:~/dev/cb/tuning-workbench-synth$ find build/tuning-workbench-synth_artefacts/TuningWorkbenchSynth.vst3/ -print build/tuning-workbench-synth_artefacts/TuningWorkbenchSynth.vst3/ build/tuning-workbench-synth_artefacts/TuningWorkbenchSynth.vst3/Contents build/tuning-workbench-synth_artefacts/TuningWorkbenchSynth.vst3/Contents/x86_64-linux build/tuning-workbench-synth_artefacts/TuningWorkbenchSynth.vst3/Contents/x86_64-linux/TuningWorkbenchSynth.vst3 ``` The last line is the problem. That file in Contents should be named .so. If I apply the patch in that other issue it gets fixed. But it may be me too. Am I doing something wrong? ---
**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\ **Post date:** [April 29, 2020, 2:16pm UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/10 "2020-04-29T14:16:03Z")
You’re absolutely right, sorry! I added a fix on a testing branch but it looks like it hasn’t made its way to develop yet. I’ll add it now. ---
**Author:** ![baconpaul](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/baconpaul/32/8403_2.png) [@baconpaul](https://forum.juce.com/u/baconpaul)\ **Post date:** [April 29, 2020, 2:24pm UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/11 "2020-04-29T14:24:21Z")
awesome. i’ll pull the juce6 branch and try again later on today or this evening! Thanks ---
**Author:** ![baconpaul](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/baconpaul/32/8403_2.png) [@baconpaul](https://forum.juce.com/u/baconpaul)\ **Post date:** [April 29, 2020, 5:59pm UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/12 "2020-04-29T17:59:06Z")
Everything worked great. Thank you! ---
**Author:** ![baconpaul](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/baconpaul/32/8403_2.png) [@baconpaul](https://forum.juce.com/u/baconpaul)\ **Post date:** [May 6, 2020, 9:30pm UTC](https://forum.juce.com/t/linux-vst3-reaper-bitwig/39022/13 "2020-05-06T21:30:51Z")
Bitwig 3.2 beta 4 came out and we confirmed that both surge (non juce) and tws (juce6) Linux vst3 work fine in it now