Ableton Forum

I recently posted the following to Ableton and Cycling '74 Support about the Live's Object Model API.

I am using "Max for Live" to try and control my Ableton projects with AI through the nice https://producer-pal.org/ Live Device, or any other way the Live Object Model is providing. I've hit a limitation in the LOM that I'd like to raise as a feature request.

A Device's "parameters" list only contains automatable parameters — per the docs at https://docs.cycling74.com/apiref/lom/device/.
For VST3/AU plugins, a parameter only becomes automatable after the user manually adds it via the device's "Configure" mode. Until then the plugin's parameters are entirely invisible to the LOM.

This blocks programmatic/AI control in two ways:

• No discovery, there's no API to list the parameters a plugin actually offers, so code/AI can't even learn what exists in order to suggest or select them.

• Manual, per-instance setup. Configure must be done by hand for every device instance and requires already knowing the plugin's layout.

Two complementary API additions on the Device class would solve this:

• A read-only discovery API listing all parameters a plugin reports (name, id, and range/units where available), regardless of current automatability, metadata the host already receives.

• A programmatic "configure" API to add/remove specific parameters from the automatable set, equivalent to the Configure UI.

As I understand, and as per the response of Cycling '74, the "automatable only" rule and the Configure mechanism live in Ableton Live itself.

Thanks!

https://help.ableton.com/hc/en-us/artic ... s-txt-file

options.txt

PluginAutoPopulateThreshold

Line to add to Options.txt file: -_PluginAutoPopulateThreshold=64

Auto-populates the plug-in parameter list if a plug-in has a number of less or equal than X parameters.

Default = 64
Min = 1
Max = 128

Yes I have seen that and enabled 128.
It does not work reliably (other mentions in this forum)

I am not sure whether it is because it only support VST2 and not VST3, or if it is because when a plugin has more than 128 parameters it just does not load anything, but any ways it is not suitable.

Also, how would those parameters be decided when a plugin has more than the arbitrary max of 128?
First 128 in alphabetical order?

In my feature request there is a systematic way to solve this

Thanks