X1 MK3 cue buttons
Hi folks,
Am I missing something or are the X1MK3 Hotcue buttons very dim with no control to increase the brightness? When they're assigned to stems, they shine bright for on as you'd expect but for Hotcues, they are just dim until you press them which isn't great.
Comments
-
I agree. The lighting should be inverted to take care of this problem.
1 -
I also noticed the same behaviour on the S2 MK3. Seems like an easy fix. What's the best way to get this on NI's radar?
0 -
There is a whole list of easy fixes, and i addressed many of them. They are busy with more substantial stuff and you can basically forget about the easy stuff, it grieves me to say.
I may or may not get around to fixing this myself. When i do, you will find the fix in the community performance mod linked to in my signature. Have a look. There already are a lot of easy fixes done.
You are referring both to X1MK3 and S2MK3. Do you have both devices? Either way, the inversion fix is exactly the same code, so when i do it for the X1, remind me to show you how to do it for the S2 yourself.
Edit: S2, S3 and S4 don't really have a lowlight problem, the pad LED's are big enough. There the problem is to differentiate between ON/OFF states. And some colours are brighter than others for which nothing can be done.
1 -
Thank you. That's amazing.
I checked you mod. Awesome job. So many useful fixes! Especially, the long press sync to check tempo without activating sync.
I do have the S2 and the S4 MK3 as well. On the S2, it is inverted like it is on the X1 MK3. Hotcues light up brighter when pressed and are dim to indicate a Hotcue is stored.
I don't know where the code is for the LEDs for either. I can see that in the CSI qml files, the code is about the functionality of the buttons, encoders and jogs but not the output of the LEDs. Does this sit somewhere else?
0 -
It's buried in the trigger functions for hotcues. NI has used a custom module without plain code and limited functionality adjustment, like the new double-click functions with a fixed delay before trigger. Both of those can be replicated with other commands and functions that allow for custom details. Many of the performancemod functions are just such custom jobs.
1 -
I find the whole new button layout to be very unreadable, the MK two was perfect. The lights were bright with having the other way around with just a little bit of light on a black button is very limiting. Not sure what they were thinking. The LED is already there so why not open it up.
1 -
I tend to agree. The use case for the X1 is a modular controller for Traktor functions alongside a setup which does not have the ability to control Traktor. When playing in a club with a djm and cdjs, I often spend more time doing a double take to spot my hotcues on the X1MK3 than I should. The MK2 is a more comfortable add on in that respect. Also, the MK2 can do 8 cues with the Flux button option. I regularly use more than 4 for juggling, cutting music and live mashups or remixes. Ultimately, it's easier to spot them on the laptop screen when using the MK3, which is something I want to avoid.
The other thing I think would be helpful is to be able to select a screen view which shows the tempo instead of the time alongside the rest of the information. Then it would be an ultimate companion for quick mixing.
0
Categories
- All Categories
- 19 Welcome
- 1.3K Hangout
- 59 NI News
- 706 Tech Talks
- 3.6K Native Access
- 15.2K Komplete
- 1.8K Komplete General
- 4K Komplete Kontrol
- 5.2K Kontakt
- 1.5K Reaktor
- 354 Battery 4
- 783 Guitar Rig & FX
- 403 Massive X & Synths
- 1.1K Other Software & Hardware
- 5.2K Maschine
- 6.7K Traktor
- 6.7K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators