asked Jul 02 '14 at 23:54 by monstrumMedia (51)

edited Jul 02 '14 at 23:56

I'm trying to load either a 32 or 64 bit .so plugin file in bitwig 1.0.10 on Ubuntu Studio 14.04, 64 bit. Linux paraHPDesktop 3.13.0-30-lowlatency #54-Ubuntu SMP PREEMPT Mon Jun 9 23:14:29 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

To begin with - I placed the 64 bit .so file in a folder I created in my user's home folder, open bitwig and tell it to look there for VST plugins. The .so has been chmod +x 777'd so i have full permissions to read, write and execute it. When I jump over to the browser in bitwig, click "VSTs" and double click the plugin file's name I get the following in the terminal console running bitwig studio:

64 bit plugin host reported errors: Pluginhost returned non zero exit code 127
Error messages:

CtrlrProcessor::ctor
/opt/bitwig-studio/bin/BitwigPluginHost64: symbol lookup error: //home/rob/VSTS/Ctrlr-VST-x86_64.so: undefined symbol: bfd_init

32 bit plugin host reported errors: Error executing command /opt/bitwig-studio/bin32/BitwigPluginHost32 info-file /tmp/vst-info3362755516305590944tmp /home/rob/VSTS/Ctrlr-VST-x86_64.so: Cannot run program "/opt/bitwig-studio/bin32/BitwigPluginHost32" (in directory "/opt/bitwig-studio/bin32"): error=2, No such file or directory
    at z.a(SourceFile:146)
    at z.b(SourceFile:201)
    at z.a(SourceFile:380)
    at cnU.b(SourceFile:135)
    ... 9 more

This does not make sense for a number of reasons unless I'm misunderstanding basic things here (entirely possible!) -First why is a 64 bit plugin trying to be opened/run within what seems like a 32 bit plugin host? -Second - that error is strange. I can cd into /opt/bitwig-studio/bin32 then do an ls and i see BitwigPluginHost32. It does exist. But if i try to ./BitwigPluginHost32 I again get the error "No such file or directory"...

Please help!

Heyho, getting the same here. Let's see, if we can fix this :)

  — (Jul 03 '14 at 14:19) riot ♦♦

Aah, first thing i noticed, that looks confusing here, but makes sense: BWS tries to launch this VST with the 64-bit host first, this gives an undefined symbol error (i'd say binutils are not correctly built in, here) After failing, it gives the 32 bit host a try - which completely fails out of obvious reasons..

  — (Jul 03 '14 at 14:27) riot ♦♦

ping still no success. With the most recent version of the plugin .so file running in the most recent 1.0.11 bitwig I get:

64 bit plugin host reported errors: Pluginhost returned non zero exit code 132

32 bit plugin host reported errors: Error executing command /opt/bitwig-studio/bin32/BitwigPluginHost32 info-file /tmp/vst-info6120732728304554922tmp /usr/lib/lxvst/libCtrlr-VST-x86_64.so: Cannot run program "/opt/bitwig-studio/bin32/BitwigPluginHost32" (in directory "/opt/bitwig-studio/bin32"): error=2, No such file or directory
  — (Aug 04 '14 at 00:36) monstrumMedia

Ok but I get the same error when I try to load the 32 bit version of the same plugin. Why is the system stating that BitwigPluginHost32 does not exist when it does exist?

link

answered Jul 03 '14 at 23:08 by monstrumMedia (51)

edited Jul 03 '14 at 23:13

I had same issues with some closed source plugins. You should check if the plugin(s) that are failing don't have any missing dependencies. You can check it by the commando 'ldd' ( ldd prints the shared libraries required by each program or shared library specified on the command line)

example:

$ ldd AF210.so output's

linux-vdso.so.1 (0x00007fff089fe000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f9cf039c000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f9cf0194000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f9ceff76000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f9cefc6b000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f9cef96a000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f9cef753000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9cef3aa000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f9cef18b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f9ceef86000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9cf09f7000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f9ceed82000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f9ceeb7c000)

If something is missing that the plugins requires then there would be a line with 'not found' in it.

example: libX11.so.6 => not found

If you would get this, then the file libX11.so.6 would be missing and it would be required to install it to make the plugin working. In this case it would be the package libx11-6 that has to be installed.

This was only an example. In reality the libx11 package is always installed, because it's a essential part of graphical interfaces on linux, unless you're running a server that not needs it ;-).

link

answered Nov 02 '14 at 16:07 by genlog (27)

I try really hard to make Bitwig working on Solus. I had the same problem when I've tried to load any VST. I was able to find my VST in Bitwig's browser, but Bitwig did not react when I doble clicked on that vst. There was no difference if it was 32 or 64bit vst. My solution: The problem gone when I've installed Steam ;). On Solus 1.2 Steam installed with bunch of libraries. I think that Bitwig just needed one of them ;). Good luck :3

@genlog Hmm.. On Solus 1.2 ldd command did not work ;).

link

answered Oct 22 '16 at 01:02 by Tramp (11)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×95
×89
×53
×26
×1

Asked: Jul 02 '14 at 23:54

Seen: 2,896 times

Last updated: Oct 26 '16 at 07:05