Bitwig

Strangetown · Post by **Strangetown** » Wed Aug 06, 2014 9:04 pm

Ok, I've successfully (maybe?) built and installed it but using Bitwig 1.0.11 RC1 on scanning for new plugins gives the following output in the Airwave utiilty log:

Code: Select all

airwave-plugin : Starting Airwave master unit 0.5.0
1407358537.124304250        CamelSpace.so : Plugin binary: /home/nick/Music/Vst/CamelSpace.so
1407358537.124327088        CamelSpace.so : Host binary:   /opt/airwave/bin/airwave-host-64.exe
1407358537.125048339        CamelSpace.so : VST binary:    /home/nick/.wine/drive_c/Program Files/VSTPlugins/CamelSpace.dll
1407358537.125061539        CamelSpace.so : Main thread id: 0x7f3fe326b780
1407358537.125294041        CamelSpace.so : Child process started, pid=2922
1407358537.125402085        CamelSpace.so : Callback thread started
1407358537.125417799        CamelSpace.so : Waiting for child response...
1407358537.125488060        CamelSpace.so : WINELOADER is not set, using wine from the PATH
1407358540.125552803        CamelSpace.so : Child process is not responding
1407358540.127008574        CamelSpace.so : Unable to initialize master unit

the message is the same for all plugins including a couple that have been reported as working here. No plugins show up inside Bitwig. Any ideas folks?

psycha0s · Post by **psycha0s** » Thu Aug 07, 2014 7:29 am

What is your wine prefix, 32 bit or 64 bit? Can you try 32-bit VST plugin? I think something wrong with your wine.

Strangetown · Post by **Strangetown** » Thu Aug 07, 2014 10:56 am

It's 64 bit. I tried reinstalling wine including deleting the ~/.wine folder. Still same issue

psycha0s · Post by **psycha0s** » Thu Aug 07, 2014 12:00 pm

Strangetown, according to your log I can say, that for some reason wine part of the vst bridge is not started. Do you have a path to wine binary in your PATH environment variable? Please, post the output of the following commands here:

Code: Select all

echo $PATH

Code: Select all

whereis wine

Code: Select all

wine --version

Strangetown · Post by **Strangetown** » Thu Aug 07, 2014 12:59 pm

Code: Select all

echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games

Code: Select all

whereis wine
wine: /usr/bin/wine /usr/bin/X11/wine /usr/share/wine /usr/share/man/man1/wine.1.gz

Code: Select all

wine --version
wine-1.7.22

Looking at the above, I added /usr/bin/X11 and /usr/share to $PATH but still no joy

glokraw · Post by **glokraw** » Thu Aug 07, 2014 6:28 pm

Strangetown wrote:Ok, I've successfully (maybe?) built and installed it but using Bitwig 1.0.11 RC1 on scanning for new plugins gives the following output in the Airwave utiilty log:

Code: Select all

airwave-plugin : Starting Airwave master unit 0.5.0
1407358537.124304250        CamelSpace.so : Plugin binary: /home/nick/Music/Vst/CamelSpace.so
1407358537.124327088        CamelSpace.so : Host binary:   /opt/airwave/bin/airwave-host-64.exe
1407358537.125048339        CamelSpace.so : VST binary:    /home/nick/.wine/drive_c/Program Files/VSTPlugins/CamelSpace.dll
1407358537.125061539        CamelSpace.so : Main thread id: 0x7f3fe326b780
1407358537.125294041        CamelSpace.so : Child process started, pid=2922
1407358537.125402085        CamelSpace.so : Callback thread started
1407358537.125417799        CamelSpace.so : Waiting for child response...
1407358537.125488060        CamelSpace.so : WINELOADER is not set, using wine from the PATH
1407358540.125552803        CamelSpace.so : Child process is not responding
1407358540.127008574        CamelSpace.so : Unable to initialize master unit

the message is the same for all plugins including a couple that have been reported as working here. No plugins show up inside Bitwig. Any ideas folks?

Did you hack a Peavey Musebox, or what?

Sorry, I'm not used to seeing .so extensions on Camel software,
and not knowing anything about how Airwave works, thought you might have
gotten frisky with the Peavey linux setup, that inclides some Camel apps.
Cheers

Strangetown · Post by **Strangetown** » Thu Aug 07, 2014 6:57 pm

No, it's just one of Camel audio's fx plugins. The .so file is a link to the actual plugin (Windows .dll) which Airwave acts as a bridge to. But alas it's not yet working on my setup, most likely to do with wine.

psycha0s · Post by **psycha0s** » Thu Aug 07, 2014 7:37 pm

Following message indicates, that airwave-host wine process is started (this is the first thing, that airwave-host does):

Code: Select all

Starting Airwave slave unit 0.5.0

If this message is not present in the logs, then more likely, that something went wrong with wine.
Try to run /opt/airwave/bin/airwave-host-64.exe manually in the terminal while airwave-utility is running and look the log messages. You should get the following:

Code: Select all

airwave-host : Starting Airwave slave unit 0.5.0
airwave-host : Wrong number of arguments: 1

Strangetown · Post by **Strangetown** » Fri Aug 08, 2014 11:20 am

Yup that is exactly what I'm getting

Qualitymix · Post by **Qualitymix** » Fri Aug 08, 2014 1:20 pm

Hey guys. Finally got this built on 64-bit Debian.
Question... is this bridge only meant for Bitwig? Carla and Ardour 3 both aren't seeing the new .so files.

psycha0s · Post by **psycha0s** » Fri Aug 08, 2014 2:20 pm

Qualitymix, I do my tests mainly with Bitwig and a bit with Renoise. No other VST hosts were tested.

mrofo · Post by **mrofo** » Sat Aug 09, 2014 9:48 am

I apologize ahead of time for this seemingly useless post...but I'm also experiencing the same issue as Strangetown. I merely wanted to raise awareness that this issue is not unique to Strangetown's setup. I am attempting to run Steven Slate Drums 64bit VST in Bitwing on Fedora 20 x86_64.

I appreciate all of the help you've been shelling out to everyone in this thread so far, phantom-one and StudioDave. I've been following the thread and you don't know it but you've been indirectly helping me out!

I'm stoked out of my mind at the prospect of getting SSD to run in Bitwig on Linux. Thanks for providing me a means through which to do that!

psycha0s · Post by **psycha0s** » Sat Aug 09, 2014 11:29 am

mrofo, do you also have the same log messages, as Strangetown? A few messages from airwave-host should exist, at least the following one:

Starting Airwave slave unit 0.5.0

.
Please, remove all your existing links through airwave-utility, then create a new one, while Bitwig is running in the background. And paste output from "Log messages" tab here.

psycha0s · Post by **psycha0s** » Sat Aug 09, 2014 11:42 am

I'm going to install Ubuntu 14.04 in VirtualBox and try to reproduce this issue.

psycha0s · Post by **psycha0s** » Sat Aug 09, 2014 1:09 pm

Strangetown, mrofo, I think I found the problem. It seems, that you haven't enabled POSIX shared memory, which used by the bridge. To enable shared memory, add the following line to the /etc/fstab:

Code: Select all

tmpfs /dev/shm tmpfs defaults 0 0

Then run this command in the terminal:

Code: Select all

sudo mount /dev/shm

And then you can try to create the link for your VST dll again. If this does not help, will think further.

PS: And here is the commands for Ubuntu x86_64, which I used before building Airwave (maybe it could help someone):

Code: Select all

sudo apt-get install git cmake gcc-multilib g++multilib libx11-dev libx11-dev:i386 qt4-default libmagic-dev
sudo add-apt-repository ppa:ubuntu-wine/ppa
sudo apt-get update
sudo apt-get install wine1.7 wine1.7-dev

Please note, I'm not Ubuntu user, so maybe someone will correct me. After installation of these dependences, you can use my instruction from this thread to build Airwave.

Bitwig

KVR Audio

Airwave - yet another WINE VST bridge for Linux (April 12 update)