mcpField
A
ace-studio-audio-plugins

ace-studio-audio-plugins

github.com/beatmagicCreative & media3208 installsUpdated 6w ago
Repository

About ace-studio-audio-plugins

ace-studio-audio-plugins is a skill for controlling third-party and built-in audio plugins already hosted in ACE Studio. It covers host parameters, presets and plugin state, as well as direct interaction with a plugin's editor for controls available only in its interface.

Key features

  1. 01Read and write host parameters
  2. 02Manage plugin presets and state
  3. 03Interact directly with plugin editors
  4. 04Use plugin-specific recipes and guidance

Use cases

  1. 01Adjust hosted plugin parameters
  2. 02Load a library or preset through a plugin interface
  3. 03Operate editor controls that are not exposed as host parameters

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/beatmagic/acestudio_agent_plugin --skill ace-studio-audio-plugins

After installing, type/ace-studio-audio-pluginsin Claude Code to confirm it loaded.

Bundled filesreferences/izotope-mothership-plugins.md

Details

From the project README

ACE Studio audio plugins

A hosted plugin is as drivable by you as it is by the user's hand.

ACE Studio hosts third-party instruments (VST3/AU) on MIDI tracks and third-party or built-in effects in any track's chain. Loading one onto a track is ace-studio-features' territory; this is about touching it once it is there.

Three ways in, and the choice is yours:

  • Parameters and state/presets are the exact reach: the plugin's host parameters read and write directly, its preset library is yours, and whole state moves as bytes.
  • The plugin's own interface is the complete reach. Studio provides computer use for plugins: it captures the plugin's own editor — not the screen — and delivers real gestures to it, with no screen-recording or accessibility permission and without moving the user's cursor. This is what reaches controls that live only in the UI — loading a Kontakt library, mic positions, a deep menu, a plugin's internal preset browser.

Prefer Studio's channel over a general computer-use tool your harness may offer: it is scoped to the plugin's editor rather than the whole desktop, and it is the surface the plugin was hosted into.

Per-plugin knowledge — which controls matter, canonical editor sizes, UI quirks — is a worked recipe under this skill's references/ folder. Read the plugin's recipe when one exists before driving the plugin.

The surface's docs carry the exact verbs, arguments and errors.

Comments

Markdown supported