Bitwig

psycha0s · Post by **psycha0s** » Sat Jun 21, 2014 5:44 pm

It seems that you have -Werror option enabled in default CFLAGS/CPPFLAGS.

abique · Post by **abique** » Sat Jun 21, 2014 5:55 pm

http://pastebin.com/5pF9bFfX he does not use -Werror in CFLAGS/CPPFLAGS.

I wonder if wineg++ fails at link time, but says nothing?

kenoby · Post by **kenoby** » Sun Jun 29, 2014 2:20 pm

It must be the linker, cause when I deactivate linking step with "-c" option it compiles without errors.
Unfortunately, when I try to link manually after that I only get this very verbose and informative errormessage:
winegcc: winebuild failed

lokid · Post by **lokid** » Tue Jul 01, 2014 2:57 am

So I seem to be having some trouble actually getting the vsts to show up in Bitwig. Im running Manjaro Linux. Built wine-stable 1.6.2 from AUR. created a PKGBUILD and compiled the vst-bridge-maker and installed using pacman. I can successfully make bridges to plugins, however bitwig shows no sign that there are any plugins in the directory. When I reindex the directory, a couple of plugins seem to crash with a backtrace from wine (like FM8 and a supersaw synth called Stargate) which I can send the backtrace if its necessary, all the other plugins show nothing, and no sign that theyve been found by bitwig. Though if some plugins are crashing on indexing that speaks to me that at least something is happening. Any thoughts?

abique · Post by **abique** » Tue Jul 01, 2014 4:39 am

Hi lokid, in the browser panel, go to files, then ensure that there is a library location for your vst bridge files. Then you can load from this folder. They do not show in "Device & Presets".

lokid · Post by **lokid** » Wed Jul 02, 2014 7:07 am

Hi abique, thanks for your reply. In the files section I can see the vsts listed in the directory, however, (and this could very much be my newness to bitwig) how do I actually use them on a track? Im away from my pc at the moment so I cant try stuff until tomorrow, but I was able to sit down a few minutes earlier and try things out. I couldn't seem to do anything with the vsts listed in the files section. Nothing happens from any amount of clicking or dragging anywhere, no interface buttons to load them, and the right click menu doesn't seem to have any options to load it on a track either. Am I missing something here?

abique · Post by **abique** » Wed Jul 02, 2014 7:09 am

Drag'n drop one of them to a track, and wait until it appears (do not release the left mouse button). It takes some time for bitwig to load vst-bridge, especially the first one as it starts the wine server, ...

lokid · Post by **lokid** » Wed Jul 02, 2014 7:24 am

Thanks! I'll check it out...

lokid · Post by **lokid** » Wed Jul 02, 2014 9:04 pm

Okay so I was able to try it out, and dragging the vst.so file from the files section of bitwig doesnt seem to do anything. I went ahead and downloaded Synth1 to try that since a lot of people have indicated success. Dragging Synth1 VST.so from the bitwig file browser out to a track just has a cursor with the small red circle w/slash indicating cannot be placed here. I also double checked with htop and ps -e | grep wine and am finding no instances of wine or wineserver getting started during this process.

It seems if the device view for a track is closed and I double-click on the file Synth1 VST.so it will open the device view, but still otherwise the behavior is the same. No loading of wine, no ability to drop the VST on the track...

lokid · Post by **lokid** » Thu Jul 03, 2014 5:39 am

So here is a little more information I was able to pull together. I ran bitwig-studio and logged the terminal output while trying to load the Synth1 vst. Here is the output.

http://pastebin.com/8e1hYFYD

Hopefully this is helpful. Im not sure where else to ask questions about this.

psycha0s · Post by **psycha0s** » Thu Jul 03, 2014 12:20 pm

lokid, did you built vst bridge in release configuration? Try to build debug version (./configure --debug). IIRC, abique told, that release build does not work.

Penzilla · Post by **Penzilla** » Thu Jul 03, 2014 6:45 pm

F*CK YEAH!!!

THANK YOU! THANK YOU! THANK YOU!

Finally! Whew!

lokid · Post by **lokid** » Fri Jul 04, 2014 1:43 am

So Ive tried both methods compiling without --debug and with --debug and the behavior seems to be the same. I can try to take a look at the output from bitwig to see if its any different. Is there any debugging output that would be handy? and where might I look for that?

I did notice, however, on recompiling now that I had wine 1.6.2 installed that I got the error:

Code: Select all

/usr/bin/ld: cannot find -lwinecrt0
collect2: error: ld returned 1 exit status
winegcc: g++ failed
Makefile:8: recipe for target 'vst-bridge-host-32.exe' failed
make[1]: *** [vst-bridge-host-32.exe] Error 2
make[1]: Leaving directory '/home/michael/Build/vst-bridge/src/vst-bridge-build/host'
Makefile:2: recipe for target 'all' failed
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

it seems that it compiles fine with wine 1.7.20 installed, but the first post mentions that doesnt work. I seem to get the same behavior in Bitwig with either version.

abique · Post by **abique** » Fri Jul 04, 2014 6:30 pm

lokid, I'll be on IRC this week-end, join us at #vst-bridge@freenode.

lokid · Post by **lokid** » Fri Jul 04, 2014 10:04 pm

Thank you! I will be leaving on a trip for a week leaving sunday, so if I get a reasonable amount of freetime tomorrow I will stop in. However, otherwise it will have to wait for now. I just want to add an overall Thank You for the help that you and others have given so far. I am quite excited about the possibility that this software represents even if its not working for me yet

Bitwig

KVR Audio

Windows VST on Linux, FINALY!