Package Details: yabridge 1.4.1-1

Git Clone URL: (read-only, click to copy)
Package Base: yabridge
Description: Yet Another VST bridge, run Windows VST2 plugins under Linux
Upstream URL:
Licenses: GPL3
Submitter: robbert-vdh
Maintainer: robbert-vdh
Last Packager: robbert-vdh
Votes: 2
Popularity: 0.65
First Submitted: 2020-05-03 14:35
Last Updated: 2020-07-27 14:40

Latest Comments

capoeira commented on 2020-07-18 18:42

Understood. thanks

robbert-vdh commented on 2020-07-18 17:36


Yabridgectl is a new (and entirely optional) feature for yabridge 1.3.0. You can read more about it in the readme, but the gist is that it can automate the setup process for you while simultaneously diagnosing and preventing a few common issues. Since it's not a hard requirement for using yabridge, it's available separately separately through the yabridgectl-git package. I forgot to add an optdepend for it, thanks for reminding me!

capoeira commented on 2020-07-18 16:09

"If you are upgrading from a previous version of yabridge and you are using the copy-based installation method, then don't forget to run 'yabridgectl sync' to update those copies."

terminal doesn't know about yabridgectl

capoeira commented on 2020-07-14 10:50

I'll do

robbert-vdh commented on 2020-07-14 10:40

Feel free to create a bug report on the issue tracker! From my experience plugins that do not work are either missing dependencies (e.g. some MSVC++ runtime), or they rely on something that has not yet been (fully) implemented by Wine. A recent example I can think of is MeldaProduction's MConvolutionMB. That plugin has run fine under Wine for ages, but the plugin segfaults with Wine Staging 5.12, so I had to downgrade to Wine Staging 5.11 to get the plugin to work again.

capoeira commented on 2020-07-14 10:29

are you interested in feedback for specific plugins? ERA 4 Bundle is crashing in my case

robbert-vdh commented on 2020-07-13 18:22

Yes, I guess you could consider the yabridge-git package to be an alpha version. At the moment they're functionally identical. And that's great to hear! I started working on yabridge because the alternatives just didn't work with some plugins and were missing support for some VST2.4 features, so it's nice to hear that yabridge also helped others run some more plugins!

capoeira commented on 2020-07-13 17:38

I see, so the git one would be a "beta"? Is this your code? got 2 plugins to work which would just crash linvst. very nice

robbert-vdh commented on 2020-07-13 10:10

Hi capoeira,

This package builds the latest tagged release (i.e. yabridge 1.2.1 at the moment), while the yabridge-git package always builds from the HEAD of the master branch. There's also the yabridge-bin package which just downloads and repackages the precompiled binaries from the releases section on GitHub. You can read more about these naming conventions on the Arch wiki.

capoeira commented on 2020-07-13 09:36

what's the diference between this one and this?