From f6bee5efca7ba73468e2256734ba5f97b7b8b279 Mon Sep 17 00:00:00 2001 From: Robin Davies Date: Thu, 3 Mar 2022 00:08:50 -0500 Subject: [PATCH] Create WhichLv2PluginsAreSupported.md --- docs/WhichLv2PluginsAreSupported.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 docs/WhichLv2PluginsAreSupported.md diff --git a/docs/WhichLv2PluginsAreSupported.md b/docs/WhichLv2PluginsAreSupported.md new file mode 100644 index 0000000..86c914e --- /dev/null +++ b/docs/WhichLv2PluginsAreSupported.md @@ -0,0 +1,17 @@ +## Which LV2 Plugins does PiPedal support? + +PiPedal will automatically detect installed LV2 plugins and make them selectable from the web app interface, as long as they meet the +following conditions: + +- Must have mono or stereo audio inputs and outputs. + +- Must not be MIDI instruments or have CV (Control Voltage) inputs or outputs. + +- Must be remotely controllable (no hard dependency on GUI-only controls), which is true of the vast majority of LV2 plugins. + +If you install new LV2 plugins, you will have to restart the PiPedal web service (or reboot the machine) to get them to show up in the web interface. + + sudo pipedalconfig --restart + +Although most LV2 plugins provide GUI interfaces, when running on a LINUX desktop, the LV2 plugin standard is specifically designed to allow remote control +without using the provided desktop GUI interface. And all but a tiny minority of LV2 plugins (most of them analyzers, unfortunately) support this.