Pads led turns off by itself
Hi,
I have a small problem.
For some reason at some point some of my LEDs from my midi controller turns off.
How can I identify what the problem could be?
Hi aventham77,
This is in fact already possible 🙂
There are 3 places in CSS where you can define LED feedback depending on the specific situation.
- Global Controller: the controller’s default LED settings in the “Controller Templates”
- Global Script: the script’s global LED settings
- Specific Script: the individual mapping’s LED feedback
A comprehensive tutorial on this can be found at https://youtu.be/ssT2qUHsFa4
Thanks 303_
– I know you can customise the default LED feedback that occurs when you use a given control, and I’ve done so (I’ve disabled it, so I can control it from a reaction instead), but there are other LED feedback “behaviours” firing when my script initialises, and when I change the selected device or track, which are having an unwanted effect on the particular control I’m trying to configure. Ideally I’d like to be able to disable/override these just by configuring the control itself, but which I’ve so far have only managed to do so by adding a script initialisation reaction, and customising the LED feedback settings on all my track selectors and device selectors.
Hello aventham77,
Thank you for the correction, I think I see now, well partially.. 😉
Let me break it down so I am able to better understand your question, bear with me:
- You have ‘Reactions’ which fire LED feedback. (That’s why my last post was not of any help to you;-)
- When you select a track or device, LED feedback breaks. May I ask what exactly happens, they disappear or change to another color?
- Also when your script initializes, you get unwanted LED feedback. I don’t understand that part exactly, since initialization is only done once when opening an Ableton Live Set. This would mean that the LED feedback you scripted is not working correctly from the start? If so, when is the moment when the script does display the LED feedback correctly?
- “I’d like to be able to disable/override these just by configuring the control itself” That is not clear to me. What do you mean by ‘these’? Where do you like that functionality? Because like you said, you can override LED feedback by using a ‘Reaction’ (or in other use cases by the 3 methods described in my last post).
For what it might be worth to you or other users; in my case LED feedback breaks when selecting other devices. A workaround that solved that issue for me was; whenever I select a device, it goes to its own Mode where the specific device can be altered, LED feedback returns to normal then. For me, this works flawlessly, but I can imagine that workflow might not suit other people.
So in short, changing ‘Modes’ seems to restore the LED feedback, at least for me.
Hi Wim,
I have a button on my keyboard, which is designed to enable or disable an “output zone” (locally in the keyboard), but which also sends a midi cc (127 or 0 value) when toggled. I don’t need the local zone behaviour, so am repurposing this button to do something more useful in Ableton.
My reaction responds to any press of this button, and returns a 127 to it, to keep it in its “enabled” state. Indeed, ideally, the button would only be registered with my script as something that can send/receive a 127 value – I’d rather the script wasn’t “aware” that it can send/receive a 0 at all.
But despite my best efforts to avoid it, my script keeps sending 0 values back to the button (setting it to red/disabled) – when the script is initialised, and when I select modes, tracks or devices. So, for now, as a workaround I’ve had to customise led feedback in several places to override the unwanted behaviour.
It seems to me that the sending of these 0 values must be part of a general “control-resetting” routine, and if so, what would be ideal would be to have the option on each control as to whether or not it should be included in that routine.
It seems to me as if the way the essential CSS logic works at the moment is that every control is treated as “stateful” – per mode, track and device (at least, in my script with two defined modes that each have their own track and device selectors).
So whenever I select a different mode, track or device, the “state” of my control is reset/recalled; whereas what I”d prefer is for this particular control either to be treated as “stateless” (so mode/track/device selections do not have any effect on its value), or for its “default state” to be registered as 127, rather than 0.
Sign up
User registration is currently not allowed.