菜单
Test VST3 plugin UIs (.vst3 bundles) using Steinberg's EditorHost without a full DAW. Use when user says "test the plugin UI", "open in editorhost", "show the .vst3 editor", or wants to visually inspect the VST3 editor. For functional validation use validate-vst3 instead.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | validate-vst3-editorhost |
| description | Test VST3 plugin UIs (.vst3 bundles) using Steinberg's EditorHost without a full DAW. Use when user says "test the plugin UI", "open in editorhost", "show the .vst3 editor", or wants to visually inspect the VST3 editor. For functional validation use validate-vst3 instead. |
| compatibility | macOS, Windows, Linux. Built from VST3 SDK source. |
| metadata | {"author":"Oli Larkin","version":"0.0.1"} |
Minimal VST3 host for testing plugin UIs without a full DAW.
editorhost accepts a direct path to a .vst3 bundle.
| Platform | User Location | System Location |
|---|---|---|
| macOS | ~/Library/Audio/Plug-Ins/VST3/ | /Library/Audio/Plug-Ins/VST3/ |
| Windows | %LOCALAPPDATA%\Programs\Common\VST3\ | C:\Program Files\Common Files\VST3\ |
| Linux | ~/.vst3/ | /usr/lib/vst3/ or /usr/local/lib/vst3/ |
editorhost /path/to/plugin.vst3--secondWindowvalidator tests first# Basic usage - load plugin and show UI
editorhost /path/to/plugin.vst3
# With component handler (tests host callbacks)
editorhost --componentHandler /path/to/plugin.vst3
# Open second window (tests multiple editor instances)
editorhost --secondWindow /path/to/plugin.vst3
# Specify a particular effect class by UID
editorhost --uid "ABCD1234..." /path/to/plugin.vst3
| Platform | Typical Path |
|---|---|
| macOS | <vst3sdk>/build/bin/Release/editorhost.app/Contents/MacOS/editorhost |
| Windows | <vst3sdk>\build\bin\Release\editorhost.exe |
| Linux | <vst3sdk>/build/bin/Release/editorhost |
Clone the VST3 SDK if you don't have it, then build:
cd <vst3sdk>
cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
cmake --build build --target editorhost
Linux: Requires X11 and GTK3 development libraries:
# Debian/Ubuntu
sudo apt install libx11-dev libgtkmm-3.0-dev libxcb-util-dev libxcb-cursor-dev libxcb-keysyms1-dev libxcb-xkb-dev
# Fedora
sudo dnf install libX11-devel gtkmm3.0-devel xcb-util-devel xcb-util-cursor-devel xcb-util-keysyms-devel libxkbcommon-x11-devel
validator tests firsthasEditor() returns false)createEditor() is returning a valid viewecho $DISPLAY)defaultEditorSize() returns valid dimensions--secondWindow to see if the issue is with first-time setupCheck macOS code signature, hardened runtime, entitlements, and notarization of audio plugin bundles (.vst3, .component, .clap, .app/.appex). Use when user says "check code signing", "check codesign", "check signature", "verify signing", "check notarization", "why won't plugin load", "hardened runtime", "check entitlements", or a plugin fails to load in a signed DAW.
Validate AudioUnit v2/v3 plugins (.component bundles and .appex app extensions) using Apple's auval tool. Use when user says "validate AU", "run auval", "test AudioUnit", "check the .component", "check the .appex", "validate AUv3", or needs to check AudioUnit compatibility. For .vst3 use validate-vst3; for .clap use validate-clap.
Validate CLAP plugins (.clap files) using clap-validator. Use when user says "validate CLAP", "run clap-validator", "test the .clap", or "test CLAP plugin". Does NOT validate .vst3 or .component — use the appropriate validators.
Validate VST3 (.vst3) and AudioUnit (.component) plugins with pluginval at configurable strictness levels. Use when user says "run pluginval", "validate plugin", or wants comprehensive cross-format testing. Does NOT support .clap files. For multi-bus VST3 plugins that crash, use validate-vst3 instead.
Validate VST3 plugins (.vst3 bundles) using Steinberg's official validator tool. Use when user says "run VST3 validator", "validate VST3", "test the .vst3", or needs Steinberg-specific test suites. Prefer this over pluginval for multi-bus VST3 plugins.