From ada0b003135077da293647d76a25638947316e8e Mon Sep 17 00:00:00 2001 From: Mikkeli Matlock Date: Fri, 19 Jun 2026 12:42:22 +0900 Subject: [PATCH] docs: note VST3 metadata display issue in FL as a known/deferred issue MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit CLAP shows name/vendor/type correctly in FL; VST3 still shows stale/missing metadata (suspected FL caching by the unchanged VST3_CLASS_ID). Deferred — use CLAP meanwhile; likely fix is regenerating the class ID and/or clearing FL's DB. Co-Authored-By: Claude Opus 4.8 --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 79c8f4b..a727781 100644 --- a/README.md +++ b/README.md @@ -163,6 +163,11 @@ Use the provided script (no need to remember the details): After deploying, in FL Studio: **Options → Manage plugins → tick "Rescan previously failed plugins" → Find installed plugins**, then search for **Codename 206**. (The rescan-failed step is essential — without it FL silently skips a plugin it has seen before.) + +> **Known issue (deferred):** the **CLAP** build shows its name/vendor/type correctly in FL, but +> the **VST3** still displays stale/missing metadata there. Suspected cause is FL caching the VST3 +> by its unchanged `VST3_CLASS_ID`. Likely fix is to regenerate that class ID (and/or clear FL's +> plugin DB); low priority for now — use the CLAP build meanwhile. ---