Fix and improve your AI-made MPC plugin

Keep the project conversation when possible. Include the device, firmware, plugin version, exact actions, expected behavior, and actual result. Paste full errors instead of saying “it broke.”

For sound problems, describe the input and settings: “On a kick loop, Drive above halfway makes the right channel crackle.” Attach a recording or screenshot when your agent supports it.

Diagnose this in the current plugin project.
MPC model and firmware: [details]
Plugin version: [version]
Steps and settings: [exact actions]
Expected: [what I wanted]
Actual: [what happened]
Error or recording: [details]

Preserve the working version. Investigate before adding features. Reproduce the problem with SDK tools where possible, make a focused fix, and rerun checks. Tell me what to test on hardware.

Ask the agent to inspect the error and the actual SDK files in the workspace. If it is unclear whether setup or plugin code is responsible, have it try an unchanged example.

Read the full build error and SDK troubleshooting guide. Check whether this is setup or plugin code. Compare against the installed SDK headers and a working example. Fix the cause, rebuild, and run the simulator. Do not hide errors by disabling validation. Report anything still failing.

Check both external-plugin switches, the exact VST2 Plugins folder name, and the folder’s position at the drive root. A second nested download folder is easy to miss. Save and restart if it is not discovered.

Give the agent a screenshot of the directory structure and ask it to validate the packaged manifest and architecture. Do not rename binary or manifest files at random.

First confirm an instrument receives notes or an effect receives audio. Then report exact settings. Keep listening volume low while checking fixes.

Reproduce the audio problem using the host simulator and a rendered WAV. Check output, stability, parameter smoothing, and excessive levels. Preserve the musical goal. Run checks after the fix and give me the exact settings to retry on my MPC.

Identify the page, control, and knob that behave incorrectly. Have the agent compare the generated interface with the built parameter list. Restart after replacing a changed interface.

Validate ui.json and the generated skins. Compare the touchscreen and Q-Link mappings with the built parameter list. Fix the blank page or wrong control without changing plugin identity or existing parameter IDs. Rebuild the complete install folder and explain how to refresh it on the MPC.

Ask for one change at a time and compare at similar loudness. “Make Mix easier to use between dry and subtle” gives better direction than “make it better.” Keep a version you can return to.

If CPU is high, report the model, voice count, settings, and number of instances. Desktop performance cannot establish hardware performance. Ask for a simpler implementation and retest.

If an update forgets settings, give the agent an older saved test project and ask it to check state compatibility. Plugin identity and existing parameter IDs should remain stable.