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 Luke,
I installed your script, adapted it to a controller I own, and as it is, it works flawlessly for me.
In your last post, you mention: “the device state of track 1 device 1 parameter 0 (device on/off) enables a midi value of 122 or 120”. I guess you mean the “Hi Kill” – “On/Off 8” button in your script? I don’t see another dedicated Reaction for this in your script. This also works great here.
Switch types “Momentary” & “Toggle” work as they should for me, although I always set the “Control Override” on “Default” unless I have a specific reason to change it.
So for instance, on your “Hi Kill” button;
– Momentary: the button is activated (white led) –> push once deactivates and turns yellow –> push once more and the button is activated again giving the white led again
– Toggle: “Hi Kill” is by default deactivated and is yellow –> push and do not release activates the “Hi Kill” (turns white) –> release and the button is deactivated (yellow) again
So then I checked your Controller script and saw that the “MIDI Message Settings” were the same on all of the pads and some buttons and knobs as well.
I think your problems could be solved once all the midi inputs on your controller script are set up with their respective midi type, channel and value. Here is a link to a video that starts at the critical moment for assigning the inputs: https://youtu.be/VOddX46Vtaw?t=370
Hope this solves some of your issues!
Greetings!
Hello Luke,
It is indeed strange behavior that the LEDs do work and then don’t. I also can’t understand why there is no log.txt file. That is a file that Ableton renders automatically. It is needed for troubleshooting. Do you know if you have a script like options.txt that prevents it from running? (https://help.ableton.com/hc/en-us/articles/209772865-Options-txt-file)
Some good news then; in order to get the track selector buttons working, you only have to change the ‘Control Override’ to ‘Absolute’. Like in the screenshot hereunder.
I’m having a similar problem (I think)…
I have a button on my keyboard that I’d like to keep lit in blue (mainly because it looks nicer than when it’s red!), but to allow me to turn a device on and off (an octave shifter in the first slot).
My script is doing what I want it to do, except that when it initialises, it changes the button colour to red.
I’m using a reaction to respond to the button being pressed (whatever value is sent), and one of the response actions is to send a 127 back to the button, so it turns blue and stays blue on subsequent presses.
But if I add another device, or switch tracks, it goes red again!
I’ve tried making it a momentary and a toggle button, and even a “knob” with a range of 127-127, but nothing seems to stop the script from resetting it to red (0) on initialisation, device selection and track selection (at least I think those are the events that are responsible).
Actually, going the wrong colour on initialisation was easy to fix with another reaction that forces the value to 127, but it looks like it would need similar reactions on device and track selection to fix those too, which is a lot of fixes for something that doesn’t feel like it ought to be happening in the first place.
Maybe what’s needed is the option per control to exclude it from the global feedback behaviour?
Sign up
User registration is currently not allowed.