From 5b079419865e36dc68df3610c47d72098b61bc27 Mon Sep 17 00:00:00 2001 From: Robbert van der Helm Date: Wed, 26 Feb 2020 18:09:42 +0100 Subject: [PATCH] Add missing TODOs and part of the protocol --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index b4a81f4d..ac4e165b 100644 --- a/README.md +++ b/README.md @@ -14,6 +14,9 @@ There are a few things that should be done before making this public, including: - Document what this has been tested on and what does or does not work. - Document wine32 support. - Swap out msgpack for bitsery and update the architecture section. +- Forward audio events. +- Forward host callback calls back to the native VST host. +- Forward the values from the Windows VST plugin's `AEffect` struct. - Add proper debugging support activated using an environment variable. - Write all stdout and stderr output from the plugin to a temporary file so it can be inspected when using a host such as Bitwig that hides this by @@ -113,3 +116,10 @@ follows: 6. The Wine VST host loads the Windows VST plugin and starts forwarding messages over the sockets described above. +7. After the Windows VST plugin has started loading we will forward all values + from the plugin's `AEffect` struct to the Linux native VST plugin. After this + point the plugin will stop blocking and has finished loading. + + TODO: Do plugins update their `AEffect` struct update itself after + initialization? For instance to change the number of parameters. Is there any + way to catch this other than checking for updates ourselves?