From 5bcae68d77e3970e21c07e319b1137e100f3cdd2 Mon Sep 17 00:00:00 2001 From: Robbert van der Helm Date: Sun, 8 Nov 2020 00:27:30 +0100 Subject: [PATCH] Add an example for using a single plugin group Now that plugin groups are 100% stable this can be a valid approach. --- CHANGELOG.md | 4 ++-- README.md | 7 +++++++ 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index edd1c9c9..4aa94557 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -62,8 +62,8 @@ Versioning](https://semver.org/spec/v2.0.0.html). - Fixed a very long standing issue when using plugins groups where unloading a plugin could cause a crash. In practice this was only reproducible during the plugin scanning process when rapidly adding and removing a large number of - plugins in a single group. Now plugin groups no longer crash, even when - hosting over a hundred plugins in a single process. + plugins in a single group. Now you can host over a hundred plugins in a single + process without issues. - Fixed another edge case with plugin groups when simultaneously opening multiple plugins within the same group. The fallover behaviour that would cause all of those plugins to eventually connect to a single group host diff --git a/README.md b/README.md index 75c12b76..4daad138 100644 --- a/README.md +++ b/README.md @@ -282,6 +282,13 @@ All of the paths used here are relative to the `yabridge.toml` file. ```toml # ~/.wine/drive_c/Program Files/Steinberg/VstPlugins/yabridge.toml +# This would cause all plugins to be hosted within a single process. Doing so +# greatly reduces the loading time of individual plugins, with the caveat being +# that plugins are no longer sandboxed from eachother. +# +# ["*"] +# group = "all" + ["FabFilter Pro-Q 3.so"] group = "fabfilter"