Package and share your MPC plugin

Play the plugin, move its controls, and save and reopen a project on your MPC. Record the model, firmware, release version, and any issues. Built for two architectures is different from tested on two devices.

An early release can be experimental. Say what remains untested and which settings are CPU-heavy. Do not let the AI turn a successful compile into a claim of broad hardware testing.

Keep your source project and last working build. Read the generated installation notes before sharing.

Prepare version 0.1.0 for sharing on PluginBooth. Rebuild, validate, run the host-simulator checks, and use the official SDK packaging workflow.

Give me the release ZIP path and draft listing text: name, short tagline, musical purpose, controls, installation, minimum firmware, build architectures, license information, limitations, and release notes.

My actual hardware tests: [model, firmware, checks, and problems]. Keep these separate from automated tests and build targets. Do not invent demos, test results, compatibility, or licensing permissions. Tell me what is missing.

Record a short demo. For an effect, include dry and processed audio at similar loudness. For an instrument, play a few notes and change its useful controls. A clear recording is enough.

Add a screenshot or cover and one sentence about its purpose. “A dark synced delay for dub-style drum throws” helps someone decide whether to try it.

Use Share your plugin below to open Creator Studio. Sign in or register if needed, then save a draft before adding the release. Verify your email before submitting.

• Add the name, tagline, category, and description using the available sharing option.
• Describe minimum firmware, supported builds, and actual hardware tests separately. Add source and support links when available.
• Upload the packaged ZIP with a version and changelog. Add screenshots and a demo if you have them.
• Review the checklist and submit. The site will tell you whether the plugin is published or awaiting review.

The SDK is MIT-licensed; other code, sounds, artwork, and impulse responses may carry different terms. Ask the agent to identify what it included and required notices. AI generation does not establish permission to distribute someone else’s material.

Keep plugin identity and existing parameter IDs stable in updates. Add release notes and reopen an older project before sharing. Ask users reporting problems for their model, firmware, release version, and steps to reproduce.