Ableton Live MIDI Remote Script / Control Surface

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).
1 Like

hmm that just sucks indeed.
Doesn’t look there are much options to mitigate this.

For Collision are both name and original name giving the same result?

Live.DeviceParameter.DeviceParameter.nameProperty Returns const access the name of this parameter, as visible in Livesautomation choosers.

Live.DeviceParameter.DeviceParameter.original_nameProperty Returns const access the original name of this parameter, unaffected ofany renamings.

I mean otherwise you could use it as a fallback.

Not sure just some idea. Ableton might continuously change and break things.

@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?

Hey!

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

Because adding to preloaded is not enough. The .epr and .ccmap must be added to Devices.py…Running the makedevices script does that for you.

1 Like


“makedevice” should be in which folder?

You found the right one (its indeed in the main folder); Problem is that it requires you to have python (version 3) installed.

I downloaded it. (python-3.11.2-macos11.pkg)
when i install will it automatically install to the correct folder?

I installed it. I found it in the usr/bin folder.

I ran “makedevice”.

.erp and .ccmap in the “preloaded” folder

unfortunately it still doesn’t work.

Ok not 100% sure but…
I think you have to run the makedevices script from the folder its in.
So make sure you are in the folder ‘ElectraOne’

I ran “makedevice” in the script directory.

Did the content of devices.py change?
Start the terminal and call the script from there.

$> python3 makedevices or ‘&> ./makedevices’

Do you see any error?

nothing happens
image

the other command indicates an error
image

try ’ python --version’ or ’ ‘python3 --version
if you get nothing then python is not in your path.

see: How to add Python to the PATH variable in Mac

python3 is in usr/bin

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?

the usr/bin is in the list

ok so python3 --version give you output?
Otherwise go to the ElectraOne folder.
run chmod +x makedevices ?

I am on windows so its hard to test.
Maybe a Mac user can assist.

this
image