Ableton VST parameters not showing: why, and how to fix it

The short answer: Ableton Live shows every parameter of a plug-in with 64 or fewer parameters. Above 64, the device panel starts empty, and only the parameters you add with Configure appear. Live's API sees the same panel. So any tool that works through Live, Maestra included, can move only the parameters in that panel.

Maestra works inside that limit and tells you where it is. It can list every parameter name the plug-in exposes to Live, including the ones outside the panel. It reads and sets the configured ones by name. When you ask for one that is not configured, it says so and shows the way to add it. This guide covers VST plug-ins such as Serum and Pro-Q.

Why Live shows only some plug-in parameters

A large synth or EQ can have hundreds of parameters. Live does not put all of them in the device panel. Ableton's manual states the rule: for plug-ins with up to 64 modifiable parameters, the panel represents all of them. Above that, the panel starts empty.

The panel is also what Live exposes to control surfaces, automation and scripts. A parameter outside it cannot be automated, mapped or set from outside the plug-in window until it is added.

What Configure does in Live

Configure is Live's way of choosing which parameters go in the panel. The Live 12 manual describes several ways to add one, including:

• Turn on Configure in the device's title bar, then click or move a control in the plug-in window. For some plug-ins you need to actually change the value.
• Adjust a control in the plug-in window while MIDI, Key or Macro Map mode is on.
• Record automation from the plug-in window. The parameter is added when recording stops.

The configuration is saved per instance, with the Set. A rack keeps both the configuration and the plug-in's state. Save as Default Configuration keeps the parameter list, without its values, for new instances of that plug-in.

No Live release up to 12.4.6, the latest release on 28 September 2026, has an API or key command that opens Configure. Configure itself stays a click in Live.

Step one: ask what you can control

Ask "what can I control on Serum?" Maestra reads every parameter name the plug-in exposes, straight from Live. It marks which ones are configured and counts the generic slots, such as "CC1 Chan 1". This is a read. It changes nothing.

You can narrow it: "which filter parameters does Pro-Q 4 have?" Maestra filters the names by the words you used, instead of paging through a long list.

You can use the name you would say. A plug-in that loads as "Serum_x64" answers to "Serum".

Step two: set a parameter by name

Ask for the change in plain words: "set Serum's Fil Cutoff to 40%" or "lower the output gain on Pro-Q by 2 dB".

Maestra passes the value in the control's own unit and lets Live convert it. Two details matter:

• On a control that shows no unit, just a bare number, a percentage sets the knob position. The reply says it was a knob position.
• On a control that shows dB, Hz or ms, give the value in that unit. A percentage on a dB, Hz or seconds control is refused without a change, and the reply names the forms that control accepts.

After every write, Maestra reads the value back from Live. The reply reports what the read-back confirmed.

When the parameter is not configured

If the parameter is outside Live's panel, the write comes back as not configured. Nothing changed. Maestra leaves every other knob alone, including ones with a similar name.

What happens next depends on the plug-in format.

VST2 plug-ins on Windows

Maestra can link the parameter for you. It saves the set first, then swaps in a rack that holds the same plug-in with its saved state, with the parameters you need linked. It applies your change in the same step. The link path is verified on Windows; on a Mac you add parameters with Configure.

What the swap keeps and what it replaces:

• Automation, macros and rack variations on the old plug-in do not carry over. When a swap would lose those, Maestra asks first.
• MIDI and key mappings on the old plug-in go with it.
• Only the parameters you ask for are linked. A panel holds at most 128. Asking for another parameter later links again and keeps the earlier links.
• Maestra saves the set once more after the swap. If the reply does not say the set is saved, save it yourself.

The save is a setting: Let Maestra save the set before linking plug-in controls in Settings › Agent › Agent controls. With it off, Maestra leaves linking to you and gives you Live's Configure steps instead.

VST3 plug-ins

For VST3, the link covers only parameters the saved set already has configured. A VST3 parameter that has never been configured is added with Configure in Live.

Configuring by hand

When a parameter needs Configure, Maestra gives you Live's own steps:

1. Open the device's panel.
2. Click Configure in its title bar.
3. Move the control in the plug-in window.
4. Click Configure again.

Maestra then rescans the session. The new parameter appears, and you can ask for the change again.

Summary

Live shows every parameter of a plug-in with 64 or fewer, and only the configured ones above that, and its API sees the same panel. Maestra lists every parameter name the plug-in exposes, sets configured ones by name in their own units and reads each change back. For a VST2 plug-in on Windows it can link a missing parameter itself; everywhere else, Configure adds it in four steps. To try it on your own plug-ins, start on the Get started page.

Sources: Ableton, Live 12 manual, using plug-ins, accessed 28 September 2026. Ableton, Live 12 manual, working with instruments and effects, accessed 28 September 2026. Ableton, Live 12 release notes, accessed 28 September 2026.