I finally understood what is going on.
You mapped directly to ableton clips, right?
If you map to Mutes for example, this doesn’t happen.
But for clips, Ableton sends random velocity values for each clip state, and every Beat 1, it sends a Note with velocity 1 for every clip that is currently playing.
Our LEDs on Fixed mode only turn ON or OFF when receiving the configured MAX or MIN values respectively, but the other values are stored anyways, and even if they don’t have an immediate effect on feedback, when switching banks they do have an effect.
This is not desired, and could be seen as a bug, in cases where the software sends update values like this.
We will work on a workaround for this.
For you now, I can suggest a few options:
-
Use our Universal Remote Script instead of directly mapping clips. This way, using our Value To Color feature, you can customize the LED colors for each clip.
-
Use the Value to Color feature, instead of the Fixed mode for the LEDs of the clips. This way the updates when switching banks will be shown correctly, but you won’t be able to choose the LED colors. They will be pink as soon as you press a button, and before the clip starts, white when the clip starts, and red after the first clip cycle.
-
Try this firmware with the fix: ytx-v2-firmware-0-23-test-fixed-color-fix.bin (115.8 KB)
It is an UNRELEASED FIRMWARE, so you can test it, but make sure you don’t do this if you have important shows or performances coming up. If you can give it an extensive test, go ahead.
Let us know how it goes, which solution you choose, and if you have any other questions!
Cheers!