Ok… blowing of some steam here… Ableton Live sucks sometimes. Turns out that:
parameter.original_name is not guaranteed to stay the same (the Phaser-Flanger device changed its Mode parameter in the latest update, messing up my CC maps)
some devices have several parameters with exactly the same name (eg Collision with two Panorama parameters, one for Resonator 1 and one for Resonator 2 (making it impossible to distinguish them in the CC map).
@Martin In this patch (for the Hybrid Reverb for Ableton) I wrote a LUA function (algotype) that should show/hide certain controls (on page 1 and 8-12) when changing the ALGO TYPE control. This works when a I assign it to the function field of the ALGO TYPE control, but if I assign it to the formatter field (as I usually need to do for now to make sure also incoming value changes trigger the visibility settings), then the patch doesn’t work. The debugger gives me no clue. Any idea what might cause this?
this is my first time trying to solve this, but it doesn’t work.
there is a plugin in Ableton (Roli Studio Player) with midi cc mapping. scipt creates the .erp file in the dump folder. I import this file to e1.
I change the colors, layout, nothing else. I send the project to e1, it works. I download the project file, copy it to the Script “preloaded” directory.
I reopen the project in Ableton that contains the plugin, the script worked perfectly. I click on the plugin, I switch to “plugin device”, but unfortunately, the “view” I modified is not displayed, but the normal one “generated” by scipt.
what is the reason of this?
thx
I am looking at it. The problem is caused by the fact that changing of the Algo Type value results in visibility changes of controls on the same page. That may result in repaint of whole current page. When that happens the system enters an infinite loop of control - page repaints. When I remove the DAMPING and MODULATION controls, it works fine.
This is the topic we touched already. I am now looking at your earlier request → calling the Function on MIDI input. I guess that is what you actually need. Is that correct?