All your LV2 and LADSPA goodness and more.

Moderators: MattKingUSA, khz

Post Reply
User avatar
Established Member
Posts: 2468
Joined: Mon Jun 02, 2008 2:30 pm


Post by funkmuscle »

Wow!!! Just finished messing around with this vst-bridge from


I was able to bridge 2 vsts I've had issues with in the past due to me not wanting to install Jack32 on my Arch64. (I downloaded the tarball)

You can also find binary tarball at ... 0.1.tar.gz

A company called Two Notes made a guitar/bass pedal that's strictly for cab/pwr amp IR files and they also offered a free demo of their vst version. I wanted to try it before buying but of course can't load vst as all the vst apps for linux keeps asking for jack32.

Here comes vst-bridge.. This converter or whatever is does to the .dll to.so and Carla found the 2 .so files and loaded them.. Oh yeah, the other vst was LeCab2 from
http://lepouplugins.blogspot.ca/2010/12 ... ndows.html

the only problem was the xruns mostly with the TwoNotes Torpedo CAB but the LeCab2 has a latency controller so adjusting kinda, I repeat, kinda fixed it.

here is what vst-bridge does or will do and how it works:

Code: Select all

This is a bridge to run Windows VST plugins (both 32 and 64 bits) with
Linux VST hosts.

= How to use it? =

Let's suppose that you have installed vst-bridge in ~/local/ and
you have a windows VST installed in ~/.wine/drive_c/VST/Synth1/Synth1.dll

First you have to create a directory for your bridges:
 $ mkdir ~/.vst-bridges

Then you can create your first bridge:
 $ ~/local/bin/vst-bridge-maker ~/.wine/drive_c/VST/Synth1/Synth1.dll ~/.vst-bridges/Synth1.so

Now edit ~/.bashrc and add $HOME/.vst-bridges/ to VST_PATH. Mine looks like:
export VST_PATH=/usr/lib/vst/:$HOME/.vst-bridges/

Then you can start your favorite DAW, ask him to scan plugins again and enjoy!

= Architecture =

A typical installation looks like:

vst-bridge.so is a Linux VST plugin which has space reserved for the windows
plugin path.

vst-bridge-maker creates a dedicated <plugin>.so for a single Windows VST
plugin by copying vst-bridge-plugin-tpl.so and updating the path to the
Windows VST and the path to the corresponding host (32 bits or 64 bits).

vst-bridge-host-(32|64).exe hosts a Windows VST and communicates with <plugin>.so.

<plugin>.so spawns a new wine process vst-bridge-host-(32|64).exe and
passes the path to the Windows VST plugin.

= Protocol =

The communication is done through socket(AF_UNIX, SOCK_SEQPACKET, 0).

 - request : tag, cmd, data
 - tag: 4 bytes
 - cmd: 4 bytes
 - data: n bytes

= Roadmap =

 - optimize I/O (reduce the number of bytes transfered)
 - make a scanner

= Extra info =


User avatar
Established Member
Posts: 1728
Joined: Wed Dec 09, 2009 5:26 pm
Location: Beverwijk, The Netherlands

Re: vst-bridge

Post by autostatic »

Post Reply