Auto configuring au/vst plugin parameters via Max4Live/js

    Nov 21 2020 | 7:28 pm
    Not sure if this is even possible since I'm not sure plugin parameters are available to the Live API until configured, but just wondering if anyone has any experience or tips on addressing plugins that don't have a default parameter/midi configuration from a max4live device/js?
    Obviously plugin parameters are easily listed when loaded directly into max, and most plugins have easily accessible parameter values that can be listed (via a parameters function in code), but it just seems I may be missing something when trying it from a max4live device that I am building. I want to make it compatible with as many plugins as possible, and am looking for a solution that doesn't involve hosting the plugin within the max device.
    I can think of a few long winded and unefficient possible solutions, but just thought I'd ask and see if anyone has any recommendations or can point me towards something.
    Thanks very much!

    • Nov 23 2020 | 4:40 pm
      you can modify the option.txt with "PluginAutoPopulateThreshold"
      so all parameters are available. This only works now with VST2. Then acces the the parameters with M4L.
      Like the device. Put the Cloner right the the vst and press "get"
    • Nov 24 2020 | 8:24 pm
      thanks DOUBLE_UG, we ended up going with route of hosting the plug-in inside max just for flexibility, as I know ableton caps the number of parameter ids (some plugins need 100s of ids to control all of it). ended up writing some js that gathers all of the plug-in parameters which was a lot easier to manage big plugins. If anyone wants the solution I can post it here