🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

Workaround/ Bugfix/ Feature for QuNeo LED feedback

Submitted by maxmoll717 on Tue, 08/08/2023 - 20:23
Control Surface Studio User


I'm not sure if this is the right category because it touches multiple areas but maybe you can help me with the following problem:

I want my QuNeo controller to show the "Default" LED feedback for functions like mute or play on the buttons which I use for controlling them. The QuNeo has set input MIDI CCs and notes for the LEDs which cannot be changed, these include some notes which I regularly use, like C1. Notes which are used for controls are deactivated for playing, so I don't want to use them that way. I set very low notes on my controller for parameter control which I don't need for playing, but as far as I can see, CSS currently only has the option to choose one of the items from the controller template for LED which are always the CCs/notes which are set for parameter control so they are not the ones the QuNeo expects.
There seems to be no way to enter the CC/note for LEDs manually in the program so I tried a workaround with dummy LED elements in the template with the notes set for the QuNeo but they seem to be bugged as the script can't be created with them in it (there is a different thread on this in the forums as well). When I use dummy buttons instead I have the same problem with the deactivated notes although the dummy buttons are not linked to any control mapping except the LED which is just output to the controller.

So my questions are if someone can tell me if there is a different solution to my problem or maybe if I can edit the final script somehow so Live doesn't disable the notes which are not used for parameter control anymore?

Feel free to ask me questions if my problem isn't clear. I could also share the script if that helps.

Thanks a lot in advance!

Topic Category: 

2 Responses


Control Surface Studio User

Hi Max,

I don't have any experience with the QuNeo, but it seems a very interesting controller with multiple CC's and Note per pad!

I had a look at the manual and on page 12, it says that the default channels for remotely controlling the LEDs can be changed in the editor. It seems that depending on the modes, it uses channels 1, 2 or 3 to send midi data to the LEDs.
So if you were to put those default channels on another channel (that you don't use for playing), you will have all your notes free for playing.
So I would try to:

  • Change midi channels for controlling the LEDs in the QuNeo editor.
  • Change the midi channels to the corresponding channels in your CSS controller template.
  • If you didn't already, have a look at the Remotify videos (especially https://youtu.be/ssT2qUHsFa4).

I think you should be able to make it work like that.

Control Surface Studio User

Hi Wim,

I forgot to look in here for a while, but thank you so much for your reply!
I just tried it out and it worked perfectly! I now wonder how I didn't come up with it myself, but I guess sometimes it just takes the outside perspective! ;P
With that in mind I was also able to fix some unwanted LED behavior of pads by changing their remote input channel to a completely unused one (I didn't know where the remote messages came from before),

Yeah, the QuNeo is a very versatile controller and now it works just as I want it to!

For anyone else with this device, here is my LED-trick summarized if you want to use different notes on the buttons than the LED control ones and keep the notes required for LED control free for use:
1.) Create dummy buttons in your template with the values for the LED control but on a different MIDI-channel
2) Change the LED control MIDI-Channel in the QuNeo-Editor for the desired buttons
3) Use the corresponding dummy buttons in the LED feedback dropdown

Maybe someone will find this helpful!

Best regards