I’m referring to System Settings → Keyboard → Key Repeat Delay. Specifically, my keyboard has a volume knоb instead of volume up and volume down buttons, so I want 0 delay for that but the normal 600 ms for all the other keys.
hi, welcome.
i don’t think those settings have any effect on volume (rotary actuator)…. at least they don’t on my razor huntsman V2.
that said, since kubuntu 24.04 there has been a noticeable delay before the volume (rotary actuator) catches hold and often times it catches going in the wrong direction (same occurs on the mouse wheel for zoom in certain apps)
i don’t expect this has anything do with key repeat settings, but rather a mis-communictaion between dbus and the app.
When I change the delay to be less (like 100 ms) it does work as I want it to, but then the setting is applied to all keys. I should have specified I am on Manjaro and this is my keyboard: pcpartpicker. com/product/jtkH99
It does read turning the volume as just volume up and volume down inputs.
as does mine using xev | grep key
keysym 0x1008ff11, XF86AudioLowerVolume
and
keysym 0x1008ff13, XF86AudioRaiseVolume
but there is no delay and it repeats with each “click” of the rotary control just like the scroll wheel on the mouse.
that keyboard looks as if it also has a rotary control which should provide discrete keyboard outputs for each part of it’s rotation.
Yes not sure, either way just looking for a way to not have kde add a delay, since it does the same delay for every key + the volume wheel. On windows there’s no delay but I believe there isn’t for standard volume keys either.
windows may have a proprietary driver that works with that keyboard.
if you need that driver, then you will need to run it under windows.
1 Like
Sad - I got an Ajazz, and the knob is notched, and acts like a key - so I set it (with modifiers) to do quite a few different jobs… including brightness, and adjusting video playback speed by a factor of 1.1 (whilst I set mpv speed keys [ and ] to adjust by √2 and 1/√2 to get TWO presses to halve or double the playback speed).
Anyway, to start the ball rolling, dig in here: https://openrazer.github.io/
Also, evremap is a tool you can use to mess about with input events - create an /etc/evremap/redragon…toml file and try that out.
This is assuming that your volume scroll wheel actually works the same way - you should test and paste the output as you rotate it… and tell us, is it notched or smooth?
one think i would suggest for ANY device that comes with windows software… go back into windows and use that software to RESET every key and feature of the device back to factory defaults before you try and use it in linux.
firmware changes to standard input devices will often render those features inoperable in linux because linux does not recognize the codes being emitted by the modified firmware.
resetting back to factory means the codes emitted will fall into the HID standard which linux expects.
When I run libinput debug-events, this is the output from me pressing the volume knоb as well as some other keys:
libinput debug-events ✔ 27s
-event1 DEVICE_ADDED Power Button seat0 default group1 cap:k
-event2 DEVICE_ADDED Video Bus seat0 default group2 cap:k
-event0 DEVICE_ADDED Power Button seat0 default group3 cap:k
-event13 DEVICE_ADDED MOSART Semi. 2.4G Speed Mouse seat0 default group4 cap:k
-event14 DEVICE_ADDED MOSART Semi. 2.4G Speed Mouse seat0 default group4 cap:p left scroll-nat
scroll-button
-event15 DEVICE_ADDED MOSART Semi. 2.4G Speed Mouse Consumer Control seat0 default group4 cap:kp s
croll-nat
-event16 DEVICE_ADDED MOSART Semi. 2.4G Speed Mouse System Control seat0 default group4 cap:k
-event3 DEVICE_ADDED BY Tech Gaming Keyboard seat0 default group5 cap:k
-event4 DEVICE_ADDED BY Tech Gaming Keyboard System Control seat0 default group5 cap:k
-event5 DEVICE_ADDED BY Tech Gaming Keyboard Consumer Control seat0 default group5 cap:kp scroll-
nat
-event6 DEVICE_ADDED BY Tech Gaming Keyboard seat0 default group5 cap:k
-event7 DEVICE_ADDED BY Tech Gaming Keyboard Mouse seat0 default group5 cap:p left scroll-nat
scroll-button
-event8 DEVICE_ADDED Razer Razer Viper V3 HyperSpeed seat0 default group6 cap:p left scroll-nat
scroll-button
-event9 DEVICE_ADDED Razer Razer Viper V3 HyperSpeed Keyboard seat0 default group6 cap:kp scroll-
nat
-event10 DEVICE_ADDED Razer Razer Viper V3 HyperSpeed Mouse seat0 default group6 cap:p left scroll
-nat scroll-button
-event12 DEVICE_ADDED Razer Razer Viper V3 HyperSpeed seat0 default group6 cap:k
-event256 DEVICE_ADDED Mouse passthrough seat0 default group7 cap:p left scroll-na
t scroll-button
-event257 DEVICE_ADDED Mouse passthrough (absolute) seat0 default group8 cap:p size 686x429m
m left scroll-nat calib
-event258 DEVICE_ADDED Keyboard passthrough seat0 default group9 cap:k
-event5 KEYBOARD_KEY +0.000s KEY_VOLUMEUP (115) pressed
event5 KEYBOARD_KEY +0.146s KEY_VOLUMEUP (115) released
event5 KEYBOARD_KEY +1.649s KEY_VOLUMEUP (115) pressed
event5 KEYBOARD_KEY +1.787s KEY_VOLUMEUP (115) released
event5 KEYBOARD_KEY +2.135s KEY_VOLUMEUP (115) pressed
event5 KEYBOARD_KEY +2.284s KEY_VOLUMEUP (115) released
event5 KEYBOARD_KEY +2.453s KEY_VOLUMEUP (115) pressed
event5 KEYBOARD_KEY +2.946s KEY_VOLUMEUP (115) released
event5 KEYBOARD_KEY +3.181s KEY_VOLUMEDOWN (114) pressed
event5 KEYBOARD_KEY +3.484s KEY_VOLUMEDOWN (114) released
event5 KEYBOARD_KEY +3.704s KEY_VOLUMEDOWN (114) pressed
event5 KEYBOARD_KEY +3.842s KEY_VOLUMEDOWN (114) released
event5 KEYBOARD_KEY +4.816s KEY_VOLUMEDOWN (114) pressed
event5 KEYBOARD_KEY +4.960s KEY_VOLUMEDOWN (114) released
event5 KEYBOARD_KEY +8.589s KEY_VOLUMEDOWN (114) pressed
event5 KEYBOARD_KEY +8.740s KEY_VOLUMEDOWN (114) released
event5 KEYBOARD_KEY +9.391s KEY_VOLUMEDOWN (114) pressed
event5 KEYBOARD_KEY +9.540s KEY_VOLUMEDOWN (114) released
event5 KEYBOARD_KEY +9.997s KEY_VOLUMEUP (115) pressed
event5 KEYBOARD_KEY +10.147s KEY_VOLUMEUP (115) released
event5 KEYBOARD_KEY +10.826s KEY_VOLUMEUP (115) pressed
event5 KEYBOARD_KEY +10.975s KEY_VOLUMEUP (115) released
event5 KEYBOARD_KEY +11.351s KEY_VOLUMEDOWN (114) pressed
event5 KEYBOARD_KEY +11.499s KEY_VOLUMEDOWN (114) released
event5 KEYBOARD_KEY +12.037s KEY_VOLUMEUP (115) pressed
event5 KEYBOARD_KEY +12.175s KEY_VOLUMEUP (115) released
event5 KEYBOARD_KEY +12.630s KEY_VOLUMEDOWN (114) pressed
event5 KEYBOARD_KEY +12.768s KEY_VOLUMEDOWN (114) released
event5 KEYBOARD_KEY +13.182s KEY_VOLUMEDOWN (114) pressed
event5 KEYBOARD_KEY +13.320s KEY_VOLUMEDOWN (114) released
event5 KEYBOARD_KEY +13.610s KEY_VOLUMEDOWN (114) pressed
event5 KEYBOARD_KEY +13.747s KEY_VOLUMEDOWN (114) released
-event3 KEYBOARD_KEY +17.562s *** (-1) pressed
event3 KEYBOARD_KEY +17.735s *** (-1) released
event3 KEYBOARD_KEY +19.087s *** (-1) pressed
a event3 KEYBOARD_KEY +19.280s *** (-1) released
event3 KEYBOARD_KEY +19.833s *** (-1) pressed
b event3 KEYBOARD_KEY +19.961s *** (-1) released
event3 KEYBOARD_KEY +20.191s *** (-1) pressed
c event3 KEYBOARD_KEY +20.322s *** (-1) released
event3 KEYBOARD_KEY +20.467s *** (-1) pressed
d event3 KEYBOARD_KEY +20.577s *** (-1) released
event3 KEYBOARD_KEY +20.703s *** (-1) pressed
e event3 KEYBOARD_KEY +20.803s *** (-1) released
event3 KEYBOARD_KEY +20.984s *** (-1) pressed
f event3 KEYBOARD_KEY +21.089s *** (-1) released
event3 KEYBOARD_KEY +21.907s *** (-1) pressed
event3 KEYBOARD_KEY +22.057s *** (-1) pressed
^C
I never used any windows software. What I meant is that I think windows specifically adds no delay to volume keys, unlike kde.
edit: this was in response to skyfishgoo’s comment
I will try evremap later when I get a chance
event25 KEYBOARD_KEY +4.000s KEY_VOLUMEUP (115) released
event25 KEYBOARD_KEY +4.350s KEY_VOLUMEUP (115) pressed
event25 KEYBOARD_KEY +4.350s KEY_VOLUMEUP (115) released
event25 KEYBOARD_KEY +4.749s KEY_VOLUMEUP (115) pressed
event25 KEYBOARD_KEY +4.751s KEY_VOLUMEUP (115) released
event25 KEYBOARD_KEY +5.450s KEY_VOLUMEDOWN (114) pressed
event25 KEYBOARD_KEY +5.450s KEY_VOLUMEDOWN (114) released
event25 KEYBOARD_KEY +5.800s KEY_VOLUMEDOWN (114) pressed
event25 KEYBOARD_KEY +5.800s KEY_VOLUMEDOWN (114) released
event25 KEYBOARD_KEY +6.250s KEY_VOLUMEDOWN (114) pressed
event25 KEYBOARD_KEY +6.250s KEY_VOLUMEDOWN (114) released
event25 KEYBOARD_KEY +7.700s KEY_VOLUMEUP (115) pressed
event25 KEYBOARD_KEY +7.700s KEY_VOLUMEUP (115) released
event25 KEYBOARD_KEY +8.450s KEY_VOLUMEUP (115) pressed
event25 KEYBOARD_KEY +8.450s KEY_VOLUMEUP (115) released
event25 KEYBOARD_KEY +10.100s KEY_VOLUMEUP (115) pressed
event25 KEYBOARD_KEY +10.100s KEY_VOLUMEUP (115) released
So pretty much identical, instant press/release signals from the keyboard - so there’s no issue with your volume control.
Doesn’t seem like evremap bypasses kde’s key delays, and has no way to add its own delay