Windows: Control key not recognised when remapped with SharpKeys

Help, Support & Bugs
#1

I use SharpKeys to swap the CapsLock key with LeftControl on my keyboard on Windows 10. This works fine in absolutely everything, including games, BUT not in the latest version of Renoise. Basically, none of the default Ctrl shortcuts work, and if I try to reassing a custom shortcut to them, neither my hardware CapsLock or hardware LeftControl keys are recognised.

It would be nice if this could be fixed. I am a programmer myself and I’m not even sure how it is possible that this remapping breaks Control handling in Renoise altogether. In my own GLFW based programs the remapping works just fine and completely transparently when I’m handling keycodes.

Thanks in advance guys!

#2

You can map caps to ctrl without any third party stuff:

# remap Caps-lock to be another left-ctrl
# run as admin
$hexified = "00,00,00,00,00,00,00,00,02,00,00,00,1d,00,3a,00,00,00,00,00".Split(',') | % { "0x$_"};
$kbLayout = 'HKLM:\System\CurrentControlSet\Control\Keyboard Layout';

New-ItemProperty -Path $kbLayout -Name "Scancode Map" -PropertyType Binary -Value ([byte[]]$hexified);
# To revert:
#Remove-ItemProperty -Path $kbLayout -Name "Scancode Map"

Write-Host "Now reboot";

maybe Renoise plays nicely with this (I haven’t tested).

#3

Thanks, SharpKeys is basically a GUI frontend for making such registry changes, so it does the same thing. So yeah, Renoise does not work with swapping Ctrl and CapsLock via the registry method, to be more exact.

2 Likes
#4

yes, it does not work here either; I have caps lock remapped to esc everywhere and when I’m renoising on windows I go ouch

2 Likes
#5

Damn.

#6

So, looks like 23 days have passed since my original post and no follow up from the devs… Do you guys know how reporting bugs is supposed to work here? I thought this is how you do it, just create a new thread in “Help, Support & Bugs” and that’s it.

Anyway, it would be good to get some official acknowledgement of this being a bug and some ETA on the fix (if it will be ever fixed), etc. Thanks! :slight_smile: