vanja/yabridge
1
0
Fork 0
mirror of https://github.com/robbert-vdh/yabridge.git synced 2026-05-10 04:30:12 +02:00
Code Issues Packages Projects Releases Wiki Activity

Rewrite the manual installation section

Browse Source 
There were still some mentions of the old symlink based installation
method there. Since this tends to be a source of issues, it's better to
just remove all mentions of it from the main readme.
This commit is contained in:
Robbert van der Helm
2020-12-29 23:24:00 +01:00
parent b94e8dde4d
commit ed7ff3db4a
1 changed files with 12 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+12 -20
View File
@@ -125,30 +125,22 @@ update yabridge if you are using the default copy-based installation method._
### Manual setup ### Manual setup
Setting up yabridge through yabridgectl is the recommended installation method Setting up yabridge through yabridgectl is the recommended installation method
as it makes updating easier and yabridgectl will check for some common mistakes as it makes setting up plugins and updating yabridge easier. Yabridgectl will
during the installation process. To manually set up yabridge for VST2 plugins, first also check for some common issues during the installation process so you can
download and extract yabridge's files like in the section above. The rest of get up and running faster. To manually set up yabridge for VST2 plugins, first
this section assumes that you have extracted the files to `~/.local/share` (such download and extract yabridge's files just like in the section above. Yabridge's
that `~/.local/share/yabridge/libyabridge-vst2.so` exists), and that you want to files have to be extracted to `~/.local/share`, such that
set up yabridge for the VST2 plugin called `~/.local/share/yabridge/libyabridge-vst2.so` exists. If you want to set up
`~/.wine/drive_c/Program Files/Steinberg/VstPlugins/plugin.dll`. yabridge for a VST2 plugin located at
`~/.wine/drive_c/Program Files/Steinberg/VstPlugins/plugin.dll`,
Depending on whether you want to use copy or symlink-based installation method, then you'll have to copy `~/.local/share/yabridge/libyabridge-vst2.so` to
you can then set up yabridge for that plugin by creating a copy or symlink of `~/.wine/drive_c/Program Files/Steinberg/VstPlugins/plugin.so`. This process has
`libyabridge-vst2.so` next to `plugin.dll` called `plugin.so`. For the example, to be repeated whenever you download a new version of yabridge.
you can use either:
```shell
# For the copy-based installation method
cp ~/.local/share/yabridge/libyabridge-vst2.so "$HOME/.wine/drive_c/Program Files/Steinberg/VstPlugins/plugin.so"
# For the symlink-based installation method
ln -sf ~/.local/share/yabridge/libyabridge-vst2.so "$HOME/.wine/drive_c/Program Files/Steinberg/VstPlugins/plugin.so"
```
Doing the same thing for VST3 plugins involves creating a [merged VST3 Doing the same thing for VST3 plugins involves creating a [merged VST3
bundle](https://steinbergmedia.github.io/vst3_doc/vstinterfaces/vst3loc.html#mergedbundles) bundle](https://steinbergmedia.github.io/vst3_doc/vstinterfaces/vst3loc.html#mergedbundles)
by hand with the Windows VST3 plugin symlinked in. Doing this without by hand with the Windows VST3 plugin symlinked in. Doing this without
yabridgectl is not supported since it's a very error prone process. yabridgectl is not supported since the process is very error prone.
### DAW setup ### DAW setup