DPF

commit 99b5d507925f6ac9d3d4cc7796e5ece78af612e3
parent b934f54d50a358293b3783d64b012fcc30a57c55
Author: falkTX <falktx@falktx.com>
Date:   Wed, 29 Sep 2021 12:26:41 +0100

Cleanup FEATURES.md, still WIP

Signed-off-by: falkTX <falktx@falktx.com>

Diffstat:
M
FEATURES.md
 | 
28
++++++++++++++++++++--------

1 file changed, 20 insertions(+), 8 deletions(-)
diff --git a/FEATURES.md b/FEATURES.md
@@ -3,16 +3,28 @@
 This file describes the available features for each plugin format.  
 The limitations could be due to the plugin format itself or within DPF.
 
-| Format | Audio IO | Parameters | Parameter outputs | Programs | States | UI->DSP sendNote | CV ports | MIDI input | MIDI output | Port groups | Special notes |
-|--------|----------|------------|-------------------|----------|--------|------------------|----------|------------|-------------|-------------|---------------|
-| JACK/Standalone | Yes | Yes* | Yes* | Yes* | Yes | Yes | Yes | Yes | Yes | Yes* | Parameters have programs mapped to MIDI CC, there is no generic plugin editor; Port groups as JACK metadata |
-| LADSPA | Yes | Yes | Yes | No* | No | No | No | No | No | No | LADSPA only supports basic parameters and audio; Programs could be done via LRDF but not supported in DPF |
-| DSSI | Yes | Yes | Yes | Yes* | Yes* | Yes | No | Yes | No | No | DSSI only supports States via UI, no "full state" possible |
-| LV2 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Everything supported :) |
-| VST2 | Yes | Yes | No | No* | Yes | Yes | No | Yes | Yes | Yes* | VST2 program support requires saving state of all programs in memory, which is very expensive and thus not done in DPF; Parameter groups are supported, but not for audio ports (per VST2 spec limitations) |
-| VST3 | Yes | Yes | Yes? | Yes | Yes | Yes | NO* | Yes | Yes | No* | Not sure if parameter outputs work (aka "read-only" on VST3); CV ports do not support custom ranges, not implemented yet; Port groups not implemented yet |
+| Format | Param outs | Programs | States | UI sendNote | CV | MIDI in | MIDI out | Port groups |
+|--------|------------|----------|--------|-------------|----|---------|----------|-------------|
+| JACK   | Yes* | Yes* | Yes | Yes | Yes | Yes | Yes | Yes* |
+| LADSPA | Yes | No* | No | No | No | No | No | No |
+| DSSI   | Yes | Yes* | Yes* | Yes | No | Yes | No | No |
+| LV2    | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
+| VST2   | No   | No* | Yes | Yes | No | Yes | Yes | Yes* |
+| VST3   | Yes? | Yes | Yes | Yes | NO* | Yes | Yes | No* |
+
+Special notes:
+
+| Format | Notes |
+|--------|-------|
+| JACK   | Parameters have programs mapped to MIDI CC, there is no generic plugin editor; Port groups as JACK metadata |
+| LADSPA | LADSPA only supports basic parameters and audio;<br/> Programs could be done via LRDF but not supported in DPF |
+| DSSI   | DSSI only supports States via UI, no "full state" possible |
+| LV2    | Everything supported :) |
+| VST2   | VST2 program support requires saving state of all programs in memory, which is very expensive and thus not done in DPF;<br/> Parameter groups are supported, but not for audio ports (per VST2 spec limitations) |
+| VST3   | Not sure if parameter outputs work (aka "read-only" on VST3);<br/> CV ports do not support custom ranges, not implemented yet;<br/> Port groups not implemented yet |
 
 A few notes for things to add to the table:
+
  - Custom UI (embed, external, both or none)
  - Host/user-side UI resize
  - Parameter inputs change from plugin-side