Thank you! I was just building my firmware for my own keyboard and was scrubbing my head on trying to use RGB matrix. Seeing real code in acttion actually helps a lot.
This is great, thank you for sharing. A while back I really wanted to add the same feature to my split keyboard, but couldn't find anything like this anywhere. The solutions I did find were huge and messy. I spent a long time scratching my head until I worked out a nice simple solution. But then with changing key layouts, I promptly forgot and lost it. So it's really nice to come across a solution. I still don't get why this isn't just an option in QMK by default. I've also thought it would be cool to add dedicated indicator lights, like most keyboards have for caps, numlock and shiftlock. I have Qwerty, Colemak, and the Japanese keyboards all as layers, so it would be handy. Maybe I'll do that on my next project.
This is the 5th video in a playlist where I build this macropad from scratch 3by2 Macropad ru-vid.com/group/PLdbIj_aeQsBbMI7IzhRsqTc7gNtt5SXVv if you watch them in order things are a bit clearer as I go over all the basics In the first videos on how keyboards are wired and how we install and compile firmware. If you got any questions feel free to ask, I also have a discord where people go in depth about questions for their builds if you get stuck somewhere
I really want to be able to change my RGB lighting when I change my layers but I have 0 code knowledge :((( I wonder if it's possible to get a super easy tutorial for us non-coders?
@@JanLunge I wanted to use a rotary encoder. SO a custom actions needs to be setup. Tried it with the MACRO but it is rather not perfect. I wanted to know Like this action is possible? case CDS_LEFT: if (record->event.pressed) { if (!cds_left_active) { register_code(KC_BTN1); // Press KC_BTN1 (down) tap_code(KC_MS_L); // Tap KC_MS_L cds_left_active = true; cds_left_timer = timer_read(); } else { if (timer_elapsed(cds_left_timer) < 400) { tap_code(KC_MS_L); // Tap KC_MS_L again cds_left_timer = timer_read(); } } } else { unregister_code(KC_BTN1); // Release KC_BTN1 (up) cds_right_active = false; } break;
Hello, I'm super noob in the world of programming. I'm trying to configure the LEDs of my Montex V.2, and your link was very useful, but I have a doubt! I used the code shown in the video to make an LED on my keyboard change color when I change the layer, but instead of 1 LED, I wanted 4 diferent LEDs to change color at the same time. How can I do it?
Hi. Don't you need to specify RGB_MATRIX_ENABLE=yes in your config.h along with a valid driver? The way this is being discussed here makes it seem like you were able to get your RBG lighting working just by copying in a snippet and recompiling. Definitely an interesting video but it would really be all that more useful if a direct link to the configuration was provided so your audience could see what's not seen in the video. The function you're referencing here doesn't exist in your entire github repo so I don't understand the response you gave below where you pointed to your repo?
Hey. All my source files are available here github.com/JanLunge/vial-qmk/tree/vial/keyboards/wlard/w3by2 The RGB_MATRIX_ENABLE=yes is located in the rules.mk I not quite sure which function you mean that can not be found. Only thing to note is vial has changed a few implementation details since I released this video so while the compiled firmware still works its possible that you run into issues with just reusing my code.
Hi Jan. Thanks for the videos they are so resoucful. I wonder if you could share raw QMK/VIA/VIAL files and directories cos I would realy like to add more buttons and encoders to your design. Thanx!
@@JanLunge for me the rgb works as an indicator and can change the color, but no animation (no breathing as shown in the clip), am I missing something?
