mirror of https://github.com/robbert-vdh/yabridge.git synced 2026-05-07 03:50:11 +02:00

Files

T

Robbert van der Helm b3efcf4e06 Merge yabridge-group.exe and yabridge-host.exe

They were 95% the same, so this makes a lot more sense this way. When
group host processes were introduced yabridge only did VST2 bridging,
but we already have a plugin type argument anyways so might as well
reuse that for group hosts.

2022-04-16 23:26:24 +02:00

1.7 KiB

Raw Blame History

Roadmap

Yabridge's VST2 and VST3 bridging are feature complete and should work great, but there are still some other features that may be worth implementing. This page lists some of those.

Short-ish term

ARA support for VST3 plugins. The ARA SDK has recently been open source, so we can now finally start working on this.

Longer term

CLAP plugin bridging. Implementing this only makes sense once Windows-only CLAP plugins start appearing.
An easier updater through a new yabridgectl update command for distros that don't package yabridge.

For a major release

Replace the use of notify-send for notifications with using libdbus directly. Most systems will have both available by default, but some less common distros split notify-send from the rest of the libnotify package.
Consider adding an option for yabridgectl to set up VST2 plugins in ~/.vst. As discussed in a couple places already doing so would come with a number of downsides and potential pitfalls so this may not happen.

Somewhere in the future, possibly

REAPER's vendor specific VST2.4 and VST3 extensions.
Presonus' extensions to the VST3 interfaces. All of these extensions have been superseded by official VST3 interfaces in later versions of the VST3 SDK, so it's unlikely that there are many plugins that still rely on these older extensions.