Well, there is potentially a not-so-elegant way to work around the limit, which is to create a Max for Live "wrapper", which loads the plugin into Max (with the "vst~" object), and then exposes all the parameters back out to Ableton. Max's VST loader isn't limited to the 128 limit, so you can access every parameter.peterswimm wrote:I dug into this and remembered whose problem this is. The problem is ubermap does not see the VST parameters for Dexed by default, so as a workaround I had to do the Live config thing where you click configure and click on each parameter in the UI to make it accessable to live (and push and ubermap). But dexed has 134 parameters so I had to leave some out. Even though ubermap will have infinity banks, there are a finite number of knobs live will let you assign. Not expecting there is anyway for ubermap to fix this, just a quirk to be mindful of for massive vsts that do not expose their vst params by default.I made the mistake of confusing Live's parameter limit with ubermaps! Back to the drawing board.
Someone has done it for Diva and Sylenth: www.xmonsta.com/product/diva-vst-xplugin/, but rather than having to create a separate wrapper for each plugin (although I imagine these are auto-generated in some way, as there are loads of parameters!), I was thinking it might be possible to use the JS support in Max for Live to create a generic wrapper M4L device, which can then load any plugin and expose all of its parameters back to Live. The downside here would be that you'd obviously have to load your plugins through a M4L device, which limits it to Suite users, and potentially introduces instability, but it would be great for some plugins so I'm going to give it a go anyway – if anyone is a Max expert, please get in touch, as I have no idea how to do anything
Real shame the limit hasn't been removed from Live yet – some plugins actually expose 1000s of parameters, yet Live can only see 128. Kinda ridiculous.