Many users have asked for improved default configuration files.
Here are two config files which offer a default keymap as follows. "_0" keys are the base layer, while "_1" keys are on alternate/function Layer 1.
Left_0: fn/Layer Key (while pressed, enables Middle_1 and Right_1 when Middle and Right keys are pressed)
Middle_0: Cmd+C (Mac), Ctrl+C (Win)
Right_0: Cmd+V (Mac), Ctrl+C (Win)
Left_1: <key does not exist on Layer 1>
Middle_1: RGB_TOG (toggles RGB on/off)
Right_1: RGB_MOD (cycles through RGB modes)
These are the two files, available for both Mac and Windows:
https://docs.drop.com/TheKeyV2MacroLightingMAC.hex https://docs.drop.com/TheKeyV2MacroLightingPC.hexThe flashing process will be the same as detailed in the existing documentation for The Key V1 ("Uploading the New Custom Configuration onto The Key" section).
Note that the provided configuration files here are '.hex' files. These are ready to flash to the controller, pre-compiled. You can alternatively follow the link above for configuring The Key V1, upload the '.json' file found there, and modify it to your liking if you want a more custom configuration. The files and instructions detailed in this post are intended to get people to a more desirable "baseline" configuration that many users desired out-of-the-box.
Please feel free to post here with any questions and I will do my best to assist with specific situations.
Roshinatorkbfirmware is EoL in that they are no longer updating, but it will remain active and available for the foreseeable future. It's on our radar though and we will have an alternate solution should kbfirmware ever go away.
keebdownunderWhen trying to flash the PC version, it fails with a memory error,
"Validating... ERROR
> 20384 invalid bytes in program region, 8160 outside region.
"
HoffmanMysterTried your default firmware, and I'm not happy with it because there is no RGB customizations at all. So, I improved it further by providing full control over all the LEDs.
Here are the layers and keymaps:
Left_0: Switch layer key (indicated by leftmost LED flashing white)
Middle_0: Ctrl+C (Windows), Cmd+C (MacOS)
Right_0: Ctrl+V (Windows), Cmd+V (MacOS)
Left_1: Switch layer key (indicated by LED under the left key flashing white)
Middle_1: Turn On/Off LEDs
Right_1: Change LEDs Animation Mode
Left_2: Switch layer key (indicated by LED under the middle key flashing white)
Middle_2: LED Brightness Down (on animation modes that support it)
Right_2: LED Brightness Up (on animation modes that support it)
Left_3: Switch layer key (indicated by LED under the right key flashing white)
Middle_3: Decrease LED Hue (on animation modes that support it)
Right_3: Increase LED Hue (on animation modes that support it)
Left_4: Switch layer key (indicated by rightmost LED flashing white)
Middle_4: Decrease LED Saturation
Right_4: Increase LED Saturation
I hope this firmware can give people a tour of all the LED modes available on this macropad.
Download Link:
Windows: https://drive.google.com/file/d/1J1DhLUzHylK5CDZyRrV3iCJCMagY1i1s/view?usp=sharingMacOS: https://drive.google.com/file/d/1BzdfG7ckKuNEaVdtqDS8wDr6DX359ZmP/view?usp=sharing
Github Source Code:
https://github.com/jason-wihardja/stackoverflow_the_key_v2_qmk_firmware/tree/thekey_v2/keyboards/massdrop/thekey_v2
The firmware I mentioned above are located under the rgb-control and rgb-control-macos keymaps. Enjoy!
jason.wihardjaOh, I'm definitely going to be flashing this and giving it a go. It's close to what I had in mind but somehow way better at the same time. The only thing I might try to do is change the code so that I have to press and hold the middle key down before it activates the layer toggle on the first key, so I can still use the first key as something like Ctrl+S, for instance. It would require adding another layer but, since QMK allows up to 16 layers and this thing is atmega32u4 based, there should be plenty of room to add that functionality. Thanks so much for this!
Edit: Uh, well, I was planning on trying to modify the code but it looks like your Github link gives a 404 error. Sad face.
Edit 2: Oh, it's an official keymap in the QMK repository now. No more sad face. Carry on.
jason.wihardjaHey, just a heads up that the default hue stepping doesn't work properly. If you cycle through the colors and come back to red, it's not red but some shade of pink. Cycle back through, it's a different shade of pink. I changed the hue step value from 10 to 8 and that resolved it.
jason.wihardjaThis file worked perfectly for me. I purchased the key macro v2, and as a result of downloading this file to the device, copy and paste functions of mac and led control were added. Thank you so much!
jason.wihardjaThanks for this! Love the customization. Much more intuitive. Imo, instead of the saturation or hue layer, a media layer would be a nice substitute.
v3frankieThe beauty of their keymap has been added to the official QMK default, you will be able to copy, edit, and make your own using their baseline keymap config. I was able to do this myself since the Hue layer didn't appeal to me either and made some changes with keeping the RGB LED layer indication.
You will just need to follow these steps: https://docs.qmk.fm/#/newbsYou will also need QMK MSYS: https://msys.qmk.fm/ which it will also point out in detail.
HoffmanMysterHello, The hex file works great! but can you publish the json file? I'm trying to understand the json file. I tried to build my own json file but i'm not sure how the layers work..
jason.wihardja@jason.wihardja could you please share the JSON file, so I could extend on your work? I want to have mac and PC makros on different layers in the same firmware, so I would be able to swap the key between mac and PC without flashing the firmware inbetween.
https://docs.drop.com/TheKeyV2MacroLightingPC.hex The flashing process will be the same as detailed in the existing documentation for The Key V1 ("Uploading the New Custom Configuration onto The Key" section). Note that the provided configuration files here are '.hex' files. These are ready to flash to the controller, pre-compiled. You can alternatively follow the link above for configuring The Key V1, upload the '.json' file found there, and modify it to your liking if you want a more custom configuration. The files and instructions detailed in this post are intended to get people to a more desirable "baseline" configuration that many users desired out-of-the-box. Please feel free to post here with any questions and I will do my best to assist with specific situations.