Value to Color doesn't match project colours

v2 Custom framework Help and troubleshooting
1

Hi everyone. I’ve set up my new controller about 90% of the way but Im running into an issue where the colours dont match those of the project. This is happening mostly in the clip launching area where it’s showing a different colour than the one set to the clip.

Pressing the button seems to fix it and the issue seems to be random as well. Any tips?

2

An additional issue that im having is that on the clips that are set to scene launch the colour is always the same, it doesnt match the colour i’ve set to the scene. Is there any way to fix this?

3

And 1 additional thing I’ve just noticed is that whenever i play a clip the clip before stays green as if it was the one it was playing. Any tips?

4

Hi @burayemusic
Can you confirm that you are using the latest version of the script?

Its not currently supported but already on the feature request list for the next update.

And 1 additional thing I’ve just noticed is that whenever i play a clip the clip before stays green as if it was the one it was playing

Make sure to have all buttons set to value to color in Kilowhat, and to be using the lastest script. What is the name of your controller?

5

Hi Ale,

Thanks for replying here as well. Thanks for the heads up on the scene color! It will be very useful.

The name of my controller is NYRA, all the buttons are set to value to color in kilowhat and the script is set up correctly. (I didn’t alter anything regarding the colors).

6

Hi there, I’m having the same issue. I have a 15x8 session box (customized the controller for 15*10 but that’s not supported) and I cannot see whats going on on the controller. The LED feedback on the pads of my controller do not reflect the clip colours in the session box. When I scroll the session box the controller has LEDs going on and off randomly. It doesn’t even look like scrolling on the controller. This happened first while I was performing live and it made the whole controller useless. Issue now persists, especially when scrolling a lot/quickly, but even when being very careful not to overload the midi signal, the issue persists.

I tried without success:
-updating to firmware 0.24 (Kilowhat says: FW v: 0.24; HW v: 1.0; CONF v: 0.20), redowloading the script (2.2)
-reloading the controller configuration through kilowhat (ofc value to colour is set where I need it)
-rebootiung ableton sometimes worked for a bit, but the issue came back quickly
-deselecting/reselecting ableton midi settings incl. controller/script midi inputs/outputs
-a new midi cable
-bought a power supply for the controller
-reducing CPU usage on my computer/live set

I tested:
-A new small live set with a 4x8 session and like 3 clips seemed to work incl. scrolling
-reducing the number of LED feedback (value to colour) settings in the configuration (no glitch so far, but sacrifice in functionality)
-pushing the buttons individully updates the LEDs correctly most of the time, but this is not a solution as I’m randomly stopping and starting the wrong clips which interferes with the performance

Could it be that the midi signal to the controller is too busy and the controller cant receive/compute that much velocity information at once? How would it work for the live15 controller… mine is almost the same…

The name of my custom controller is |||||||||||||||

(Would also have been nice to be warned of the max 16*8 session box when building my controller as my intended functionality was quite obvious.) But otherwise everything else works great! Its just a shame that this LED issue makes the pads and heart part of my controller useless in most of my live sets. I hope it can be fixed!! grateful for any help!!

7

Hi @pascal.bauer and @burayemusic

To improve performance with large setups (like clip matrices in Ableton Live), we recommend the following steps:

1. Disable “Remember State” in Kilowhat

  • What it does: Automatically saves your controller’s state every 10 seconds and reloads it when powered on.
  • Why disable it: In live setups or with heavy data loads, this can overwhelm the controller, causing performance issues or erratic LED behavior.
  • How to disable it:
    Open your configuration in Kilowhat → Preferences → Controller Options → turn off “Remember State”.

2. Disable Parameter Controls in the Ableton Script

In the script file (around line 159), set the following parameters to False:

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
STRIP_PARAM6_CONTROLS_ENABLED = False
STRIP_PARAM7_CONTROLS_ENABLED = False
STRIP_PARAM8_CONTROLS_ENABLED = False

This disables device parameter controls and helps reduce MIDI traffic.
After making these changes, close and reopen Ableton.

We’re currently investigating how to make both features work smoothly together.

Let me know if this any of these help!

8

Hi thanks for the quick and clear response!! Unfortunately no improvement. I already had “Remember State” disabled. Disabling parameter controls as you’ve shown has also not improved the problem. I also restarted ableton and the controller after changing the script and LEDs are still lighting up randomly.

9

Can you please upload your script and your Kilowhat configuration?

I can see from the last configuration you sent to your controller from Kilowhat, that some buttons are not configured with the Value To Color feature (they are yellow), and they seem to send MIDI messages that are intended to be clip launchers (MIDI channel 2).

Maybe this is intentional, but I’d check it again.

10

YaeltexUniversal.zip (95.0 KB)

This was intentional. Its a group in my live set and fixed LEDs help me see that. I’ve attached what I’d like to have here:
||||||||||| Yaeltex Remote.ytx (490.3 KB)

And this is the reduced version with less value to colour, but it still glitches.
_______________.ytx (490.3 KB)