Drop ALT V1 Mechanical Keyboard Discussions | Drop

Free Standard Shipping in the US on orders over $99

Showing 1 of 1131 conversations about:

Drop ALT V1 Mechanical Keyboard

Mech Keys

FULL DISCUSSION

jzfgs

Sep 3, 2019

Hi all, I need some help from the expert QMKers among you:

I recently got a Massdrop Alt and I love it. I'm going to get a CTRL for my other desk. With that said, I'd like to do what I thought would be fairly simple, but does not seem so. I'd never used QMK or gone very in depth with coding of any kind until today.

I need help setting all RGBs to white by default. So I'd either either only have white, which the online tool allows, or have the default RGB configurations just start on white (or some other preset if it's easy to adjust) and allow me to cycle through them.

The reason I downloaded QMK to begin with was because I waned to set nkey rollover to "on" by default, which I was able to do in the config file. But now, \~3h later, I can't figure out how to change the LEDs whatsoever within QMK. Does anyone have any guidance as to how I could accomplish one/both of my desired RGB configurations?

I saw this (https://github.com/LastContinue/ctrl-info/wiki/FAQ-Lights) wiki that outlined a way to make these adjustments, but it appears that the led\_programs.c entry no longer exists so I can't make these changes. Thanks in advance everyone! EDIT: This is something I'd like to do on my CTRL when I get it, so if the process is different for that, could someone let me know/explain? I'll want to use the default non-scrolling rainbow LED pattern, and if I can still access the other default ones, great, but if not I'd be happy to just have that one LED profile with nkey rollover enabled by default. EDIT 2: For whatever reason, any firmware I compile within QMK gives me a ton of different scrolling/rainbow effects that I can cycle through instead of the default ones (solid colors, teal->salmon, etc) that are present when I download firmware from the Massdrop site. I'm not sure why or how to change this.

(Edited)

Sep 3, 2019

Vote

jzfgs

Sep 3, 2019

jzfgsHey just a quick update: I solved my problem! Basically, I was modifying the default keybind instead of the default_md keybind, so the RGB actions assigned to fn+QWE and ASD were set to cycle between a different set of RGB options. When I instead modified default_md with my keybinds, everything worked perfectly! I was able to use the led_matrix_programs file in \qmk_firmware\tmk_core\protocol\arm_atsam to rearrange the order of the stock RGB patterns so whichever pattern I want can boot. This was the same method as suggested in the link in my main post, but the file was in a different place. This is all on top of adding the #define FORCE_NKRO line to the config.h before compiling so I have NKRO (and 1ms/1000Hz polling) on boot. Hope my solution here can help someone else!

Sep 3, 2019

jzfgs

Sep 3, 2019

jzfgsAnother update: /u/lebrun on Reddit suggested I do this instead to accomplish my desired result. I'm going to try this later today; hopefully this helps someone who's trying to do the same thing I am! "Modifying the base file will cause conflicts when merging changes from upstream. A better way would be to set the default led patter in the matrix_init_user function of your keymap, like this: void matrix_init_user(void) { // Start with the leds_white animation. led_animation_id = 7; }; leds_white is element 7 on the led_setups array (led_matrix_programs) This way the keyboard will start with the color you want like with your changes, but since this will be located in your own keymap, it'll be easy to merge changes from the repo."

Sep 3, 2019

Vote