Live15 remote learn

General
1

Just unboxed the Live15 - what a beast :slight_smile:

The script works great, just need to override some settings - so I need to enable ‘remote’ in ableton midi settings. This however causes the pads to no longer represent the midi clips (colors) in the liveset. ‘Remote’ seemingly interferes with the script?

Looking at the script I’ve found that disabling a few components (mixer, device, device_navigation) while keeping the session grid enabled should let me MIDI-map the controls inside the script without needing Remote on, so clip colors stay intact.

Please let me know if this is the best way forward, thanks. Maybe I’m missing something obvious that wont require me to edit the script?

BR

Henjo

2

Hey @henjolo!

Welcome to the forum :slight_smile: the Live15 Remote Script is build with the YURS (Yaeltex Universal Remote Script), which has some workarounds to co-exist with a regular mapping.

Check this post to learn more about the YURS YURS: Yaeltex Universal Remote Script for Ableton Live

Instead of disabling components in the script files, what I would recommend as the best way to leave some controls “free to map” is to change their MIDI channel to one of the “free MIDI channels” of the YURS (channels 12, 13, 14, 15).

You can do this in Kilowhat. :police_car_light: BEWARE, in order to start from your current Live15 configuration, make sure to select the “CTRL” option once the pop up window appears. If you select “DEFAULT”, it will load the factory default, which is not compatible with the script.

So what you would do is to change the MIDI channel of the controls you want to remove from the script to one of the free ones.

3

Hello Matteo,

Thanks for your quick reply. I tried this; I went into kilowhat and then to the ‘analog’ section since I want to remap the knobs and faders. I batch selected all the ones on channel 1 and set them to channel 12. Then i set all those on channel 2 to channel 13. Pushed it to the machine and opened ableton.

Now the device no longer controls things. And the clips pads are lighting up randomly. Ive been trying to connect to kilowhat, it wont connect. It connected once some 10 minutes ago and i was unable to do anything there. It was somehow continuously triggering random midi. Meaning i couldnt stay on a control to edit it, every second other controls were launched changing which params are exposed to edit.

Seems I need a hard reset but i cant get into kilowhat and I dont have a clean setup file to reset to.

4

Make sure to simplify and avoid any MIDI routing noise by closing Ableton and unplugging other MIDI devices.

Are you in Mac or PC?

I’ve sent you your controllers Script compatible configuration file via email :wink:

5

Thank you. I’ll try to get the script on the device. I’m on Mac.

8

Fixed it!

changed map.py to:

SELECTED_STRIP_PARAMETER_CONTROLS_ENABLED = False
TRACK_STRIP_PARAMETER_CONTROLS_ENABLED = False
STRIP_PARAM1_CONTROLS_ENABLED = False
STRIP_PARAM2_CONTROLS_ENABLED = False
STRIP_PARAM3_CONTROLS_ENABLED = False
STRIP_PARAM4_CONTROLS_ENABLED = False
STRIP_PARAM5_CONTROLS_ENABLED = False # already False
STRIP_PARAM6_CONTROLS_ENABLED = False # already False
STRIP_PARAM7_CONTROLS_ENABLED = False # already False
STRIP_PARAM8_CONTROLS_ENABLED = False # already False

from post Value to Color doesn't match project colours - #7 by francoytx fixed it.

then remapped the sends / returns to channel 12/13 and all is still working :slight_smile:

1 Like
9

All right! Time to have fun now :stuck_out_tongue:

Cheers

1 Like