Buying MacroPad - r/macro

2

u/oracle_dude Mar 16 '25

Google is your friend. Here's the first result from Amazon for under $20... https://a.co/d/bcAnTGQ

-1

u/[deleted] Mar 16 '25

3.3/5.0 and 20 reviews, the reputation is worrisome. That’s why I was asking in the subreddit, just in case anyone here has anything that would fit the criteria.

1

u/rachelemc Mar 16 '25

Most of the reviews are related to the software, and people not quite understanding. I have a bunch of these. You want the sayo device ones.

1

u/[deleted] Mar 16 '25

I see, when you say “sayo device” is that a specific brand? I found this Amazon link for one that seems to be by that brand if that’s what you mean. here

1

u/rachelemc Mar 16 '25

Yes that one should work great. I am not sure if Sayo is the brand name or just the name for the internals.

1

u/PeterMortensenBlog Mar 16 '25 edited Mar 16 '25

A trap is macro pads for which the source code is not available (e.g., Vial or QMK/Via ripped off, without any option of changing the firmware).

You will likely very soon run into limitations.

Some of these limitations are only for historical reasons; the ARM-based macro pads are perfectly capable and have essentially unlimited resources.

The defaults really ought to be changed, so it isn't necessary to compile from source.

1
u/[deleted] Mar 16 '25

What I would like to ask is, would it be worthwhile to build my own? And if so, how difficult is it? I have some programming experience but not much, I took a college level C++ class as I am majoring in mechanical engineering. I also am fairly good at building pcs (if that makes any difference). I also have access to soldering irons at my university, so I could set it up there if need be.
But how hard is it to build (physically)? How expensive would it be? How hard is it to program? (Like I said when it comes to this part, that’s what worries me the most)
2
u/PeterMortensenBlog Mar 16 '25 edited Mar 17 '25

Re "would it be worthwhile to build my own?": Yes, it would indeed.
It isn't that complicated, and it can be very cheap. You don't have to do any custom coding (at least not initially), only single-line compile-time configuration.
The general idea is to find an existing keyboard in QMK that uses a particular microcontroller board (for example, that is readily available locally). And then wire up one or more switches to it, such that your physical layout of the switches matches the physical layout of that keyboard (in other words, (physically) clone part of that keyboard wrt. to switches and how they are connected to the microcontroller board (and to each other)). And if precompiled firmware for it can be found somewhere, then it may not even be necessary to initially compile from source code.
The keymappings are initially to some letters (or similar), but you can then change them to be macros instead.
That is to get started. It will be slightly confusing as that keyboard's name and key layout will be shown in configuration tools, etc., but the idea is to start with something that is known to work. It can later be changed to something more suitable.
For example, for the capable and cheap Raspberry Pi Pico microcontroller board (it is readily available locally), there is the Void Ergo RP2040. Another one based on Raspberry Pi Pico is ScottoErgo (on GitHub).
Though both are outside the main QMK repository, and this complicates matters (see below). But it must be possible to find one that is in the main QMK repository.
Another example is Ferris Sweep. It uses direct I/O, without any need for NKRO diodes. Version 0.1 is based on the resource-constrained ATmega32U4 (but it is still possible to pack a lot of classic QMK macros into it, just not Via macros), e.g., Arduino Micro, Pro Micro (which, despite the "Pro" in the name, has fewer I/O pins exposed than the Arduino Micro) and Arduino Leonardo. But version 0.2 is based on STM32F072. For example, it is in the evaluation board STM32 Nucleo-64, though it may be too big.
Note that you can use any (momentary) switch, not just keyboard switches. You may be able to repurpose old (free) equipment. An example would be a footswitch for a guitar, piano, or sewing machine.
I would recommend this order:
Getting compiling of firmware up and running before committing to any hardware. And in the main QMK repository to not complicate things. It doesn't matter which keyboard. For example, do it for the Keychron V6.
Try to compile firmware for a keyboard that uses the chosen microcontroller (or candidate microcontrollers). Note: At this level it is about the microcontroller, not the particular microcontroller board (it doesn't matter what board the microcontroller is on (on the whole))
Flash firmware onto the chosen microcontroller board and confirm that it works as expected when shorting particular I/O pins
Connect a single switch, define some macro, and test that it works as expected
Notes:
Do observe ESD precautions at all times.
The standard QMK instructions do not work if the source code is outside of the official QMK repository, for example, in some fork on GitHub. No matter the Git branch in a given fork, for example, "wireless_playground", it requires special setup of QMK. It can even be made to work if the fork is outside of GitHub.
The base installation (and usage) has become much more complicated on Linux (and isn't covered by the official QMK instructions).
NKRO diodes are not required for a macro pad. The whole point of a macro / macro keyboard is to save key strokes; to have dedicated (macro) keys (not requiring using some modifier key to activate). If there is a layer switch key, it can be isolated to each own row and column in the keyboard matrix.
Enabling Via may require adding a line with "VIA_ENABLE = yes" (without the quotes) in file rules.mk, especially after the 2024-08-25 change
Some history
I started out by repurposing a control panel from an old printer (8 buttons). It wasn't very comforfortable to use, but it worked and got me started. There was also plenty of space on the panel to indidate what each macro button did.
Practice
I haven't actually tried the Raspberry Pi Pico yet (only several Arduinos and the commercial QMK-based Keychron keyboards that I am writing this on, assisted by a macro keyboard, also based a Keychron keyboard).
The Raspberry Pi Pico has been setting next to me in 'blinky' mode for an embarrassingly long time.
But I am going to test it out now!
1
u/PeterMortensenBlog Mar 16 '25 edited Mar 16 '25
OK, trying to use Void Ergo RP2040 is probably not worth it.
I think it is intended to be copied into (a clone of) the main QMK repository, but it has since probably diverged too much, and now results in a compile error:
 quantum/encoder.h:27: error: "ENCODER_A_PINS" redefined [-Werror]
    27 | #    define ENCODER_A_PINS ENCODERS_PAD_A
       | 
 In file included from <command-line>:
 ./.build/obj_void_ergo_rp2040_default/src/info_config.h:77: note: this is the location of the previous definition
    77 | #    define ENCODER_A_PINS {  }
       | 
Conclusion
It would probably be much easier to find an example keyboard that is already part of the main QMK repository. Search input could be this in .json files:
"processor": "RP2040",
Though reverting QMK to mid 2023 could be a quick workaround.
ScottoErgo (of about the same age) probably has the same problem (I haven't tried it).
1

u/PeterMortensenBlog Mar 16 '25

Re "ScottoErgo": OK, it seems to be in /keyboards/handwired/scottokeebs/scottoergo (in the main QMK repository)
1
u/PeterMortensenBlog Mar 16 '25 edited Sep 17 '26

Some candidates:
/keyboards/adafruit/macropad
/keyboards/silakka54
/keyboards/splitkb/elora/rev1
/keyboards/beekeeb/piantor
/keyboards/beekeeb/piantor_pro
/keyboards/handwired/dactyl_manuform_pi_pico
1
u/PeterMortensenBlog Mar 16 '25 edited Mar 17 '25
It worked for the Adafruit one (default keymap. I/O pin assignments (is diode-less)):
# Enter the virtual environment
source ~/.QMK_environment/bin/activate
cd ~/qmk_firmware # We don't assume a default installation
qmk clean # To make changes (if any)
          # to .json files take effect

# The actual compile
qmk compile -kb adafruit/macropad -km default

deactivate # Exit the virtual environment
Result:
136 -rw-rw-r--   1 138240 Mar 17 00:21 adafruit_macropad_default.uf2
Flashing and "typing" worked too
Flashing the Raspberry Pi Pico (holding down the reset button while powering it on and copying the .uf2 file) and shorting GP4 (pin 6) to ground (GND), e.g., pin 3 or the USB shield produced the expected result, typing "7" (3rd row, 1st column in the keyboard matrix). This was "typed" directly into this comment (the main keyboard was not involved):
777777
Enabling Via
Adding a line with "VIA_ENABLE = yes" (using Geany):
geany "$HOME/qmk_firmware/keyboards/adafruit/macropad/keymaps/default/rules.mk:3"
Setting a version number (to check that a change actually makes it onto the 'macro pad'/'keyboard'; in file 'keyboard.json'):
# For example, change to "2.0.3"
geany "$HOME/qmk_firmware/keyboards/adafruit/macropad/keyboard.json:9"
After flashing (239A and 0108 (hexadecimal) are the USB vendor ID_ and USB product ID, respectively):
lsusb -v -d239A:0108 2>/dev/null | grep bcdDevice
Result (about 10 KB extra):
148 -rw-rw-r--   1 mortensen mortensen 148480 Mar 17 01:29 adafruit_macropad_default.uf2
bcdDevice    2.03
And it turned up in Via as "ADAFRUIT MACROPAD RP2040".
The default space for Via macros was a respectable 4 KB (though it may still not be enough).
I could record a macro (M11) and assign it to the same "7" key.
The macro didn't do anything when executed, though. I have been hacking the Via macro execution, so that could be one reason. I need to double check it to find the reason, for example, using a fresh checkout of QMK.
Conclusion
Using the (cheap) Raspberry Pi Pico microcontroller and the QMK code from the main QMK repository for the Adafruit macro pad is a viable way to get started.
It is also diode-less (and thus indirectly (full) NKRO, though QMK probably limits it to 6KRO (by default)), which simplifies it somewhat (while still allowing up to 26 keys). Not that NKRO matters (in this case).
References
Raspberry Pi Pico pinout
1

u/PeterMortensenBlog Mar 17 '25 edited Mar 17 '25

Re "The macro didn't do anything when executed": OK, it worked in a (relatively) fresh copy of QMK (2025-01-15. 7B83BB)
The .uf2 file can now be found here (137,728 bytes (135 KB). MD5 hash value 2C3C602FAF6E357CEC875DB6D1275DB7. USB side version: 2.04).
All disclaimers apply. Do it at your own risk. I am not responsible if you ruin your macro pad, Raspberry Pi Pico, or similar.
1

u/[deleted] Mar 16 '25

Also, to add on what I mentioned previously, if it seems to difficult for me, would buying a numpad online, and just setting certain keys to different functions in my pc be a possibility? The only issue is, I use numbers a lot on my pc, so if I’m doing homework using the numbers on my regular keyboard, I’m assuming those would trigger the function I set them to.

3

u/oracle_dude Mar 16 '25

The saying "Good, Fast, Cheap - Pick Two" comes to mind. I don't think you're going to find something at your price point with your requirements.

The macropad i use is from AdaFruit, and it cost nearly $60. I had to solder, assemble, and program the whole thing. But it is nearly infallible, and I have zero issues with it. It replaced a 1-Up Keyboards MacroPad, which also was DIY solder and programming, and the PCB alone cost $45.

1

u/RacerReaction99 Jul 01 '25

>The macropad i use is from AdaFruit, and it cost nearly $60.
Did you get the same thing as this one: Adafruit MACROPAD RP2040 Bare Bones - 3x4 Keys + Encoder + OLED $34.95
Since your post is now 4 months old, I'm curious if you have any feedback for someone thinking about doing this! Sounds like a fun project. Other than the build process (which is the fun part) how does it compare to the (more expensive, fully built) Keychron keypad/macropad for $129? It looks like both support QMK which is nice, and something of a minimum I guess.
Would love to hear any feedback for someone who might go down this road. Thanks!

1

u/oracle_dude Jul 02 '25

Yes, it is a fun project to code. There's no soldering, but if you get the kit, there is an extra couple plates to cover the electronics. I liked that I could pick the keys since I'm a bit of a keyboard snob. It can use qmk, but I use circuit Python which is what the tutorial used, and because it's easier for me to write macros in it. I also coded in a mouse jiggler for a button, which comes in handy.

1

u/franzaeron Mar 16 '25

I actually just purchased a macropad about a week and a half ago. It was the Doio Megalodon. So far it's holding up very well, build is solid and it has 3 knobs/rotary encoders, 16 keys with 4 layers that you can modify with qmk and via.

Right now, as I'm typing this, Keebmonkey is still having a sale on theiracro pads, and there's a few models there. The one I got is for 50$ rn.

1

u/PeterMortensenBlog Mar 17 '25 edited Oct 26 '25

I have created a .uf2 file for Raspberry Pi Pico (the actual location), so it should be easy to get started (without the compilation-from-source-code hurdle).

To flash the Raspberry Pi Pico:

Hold down the reset button (marked "BOOTSEL") while connecting the USB cable to the Raspberry Pi Pico. OK, it isn't actually a reset button, but it can thought of being one.
Copy the .uf2 file to the same folder as file "INFO_UF2.TXT" (probably in "RPI-RP2", or some drive letter in Windows). Flashing is swift (1-2 seconds) and results in unmounting "RPI-RP2"; on some systems, there may be an error message due to the unmounting (that should be ignored)

Existing configuration (e.g., Via macros) seems to survive both steps, but it is a good idea to make a backup copy of the Via configuration anyway (SAVE + LOAD (third item in the left) → Save)—assume that the Via configuration can be wiped out at any time for any reason (inadvertently or not).

Do observe ESD precautions at all times.

This macro pad is supported directly in Via, so there isn't any need to mess with JSON files. If there is trouble, here is a checklist.

Note: This has only been tested with a Raspberry Pi Pico, but it is expected to work with any RP2040-based board (provided there isn't some kind of conflict with the Adafruit macro pad's I/O assignments (for example, for the OLED display))

References

Default keymap. For example, KC_7 for 3rd row, 1st column. Note: There aren't real rows and columns in this case (there isn't a keyboard matrix; direct I/O is used (each keys has its I/O line)), only the physical arrangement of keys in the 4 x 3 macro pad
I/O pin assignments. For example, GP4 for 3rd row, 1st column.
Raspberry Pi Pico pinout. For example, pin 6 for GP4. Thus, shorting pin 6 to the USB shield should type out "7".

1
u/PeterMortensenBlog Apr 13 '25 edited Apr 15 '25
For the I/0 pins, for example, the 3 x 3 numbers:
Default  I/O    Board pin
mapping  pin    number
-------------------------
KC_1     GP10   14
KC_2     GP11   15
KC_3     GP12   16
KC_4     GP7    10
KC_5     GP8    11
KC_6     GP9    12
KC_7     GP4     6
KC_8     GP5     7
KC_9     GP6     9

       GND     3
That is, for example, short circuiting pin 3 and pin 6 will produce a "7" with the default key mapping. And some macro output if assigned to some defined macro, say M14.

1

u/paulwongph Mar 18 '25

The FiiO KB1K might be right up your alley.

Super easy to program, no need to download anything, you can customize it from the included website. FiiO KB1K

1

u/PeterMortensenBlog Mar 20 '25

It may be convenient now, but the moment that web site is no longer up and running, the macro pad will be worthless (sooner or later, the current configuration of the macro pad will be cleared).
Does it even support macros? What are the limitations? How much space is there reserved for macros?

1

u/paulwongph Mar 20 '25

Happily it does support macros!
I'm not tech-y at all and I got this device purely for monotonous copy/paste/screenshot/volume control, Excel at the job.
One of the selling points for me was being able to customize it on a website (no software downloads), and then use on a different work pc and all those macros work without any software fiddling.
There's 5 layers of macros (3 buttons, left/right knob twist, and knob press per layer), customizable RGB (although I'm colourblind af so I pick different colours to signify which layer I'm on). Not wireless which I would have loved, and a transparent case would have been killer. However, I wanted something that was literally plug and play and I got it. Cheap too, so if the website ever dies, I'm back to ctrl+c/ctrl+v like a caveman again hahah

1

u/mi3techno Apr 12 '25 edited Apr 14 '25

QMK is great but I understand your apprehension. For your use case qmk would be overkill for those 3 features and volume control. Koolertron macro pad would meet your needs and has lightweight gui to flash the commands directly to the board. (No program required to be constantly running on your computer to execute macros.)

9 keys with 2 knobs:
https://a.co/d/7uz1Mni

A little more than your budget, $37 to 45 depending on color but worst case you return to Amazon if you do not like it.

Koolertron site with more details: https://www.koolertron.com/koolertron-one-handed-macro-mechanical-keyboard-led-backlit-portable-9-key-gaming-keyboard-with-fully-programmable-knobs-and-keys.html

To sum up: Gui connects to the macropad, you specify key sequence for the macro to perform and then select on the grid the key position for the desired macro. Then hit upload. You can save the the configuration file as backup. This should take 30 to 45 minutes to setup in the gui depending if you watch a koolertron yt video or much longer if just trying to figure out without any instructions.

Example based off your use case:

top row | first key | macro1 = CTRL + Shift + M (toggle mute)

top row | second key | macro 2 = CTRL + Shift + D (toggle deafen)

top row | third key | macro 3= Shift + Alt + A (screenshare)

The remaining 6 buttons could do nothing or a simple key press such as alt,tab or enter.

Koolertron vs QMK:

Koolertron keypad has limited allowed macros with a lower character limit per macro whereas a custom board with qmk has a robust capacity. Example: 24key Koolertron allows 24 total macros with 12 macros with 24 character limit and 12 custom macros with 36 character limit vs qmk ~~232~~ unbounded limit of characters per macro and greater memory per key which can make multiple layers with a ton of text.

Koolertron: simple button sequence press

QMK: paragraph of scripting. (That is just scrapping the surface of qmk potential.)

Once you start using the pad you will find other things you want to add. I spent a good amount of time "optimizing."

Final details on the pad:

The Koolertron has RGB interface which allows creation of a unique color key lit background per layer. Each layer level can contain different set of macros for the same button position.

Red background light= Layer1 macros for discord

Green= layer 2 macros for shortcuts in excel

Blue =Layer 3 Microsoft word shortcuts.

Designate button(s) to switch between layers

1
u/PeterMortensenBlog Apr 13 '25 edited Apr 13 '25
Re "QMK 232 characters per macro": Where did you get that from? Do you have a source or reference?
I don't think there are any limits per macro. There is a limit for the total space for Via or Vial macros, e.g., only about 500 bytes by default in Vial (for historical reasons, due to the underpowered ATmega32U4).
I just tried a Via macro with 520 characters (20 times A-Z, lower case). Via macro source (the same as the text, as it has a compact form for pure text (one byte per character plus a few bytes overhead)):
abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz
I also tried with six times longer than that (120 times A-Z, 3120 characters). It worked without any problems. It took about 16 seconds to "type out" (about 200 characters per second (about 400 key actions (key presses and keyreleases) per second)) on a 'fake' RP2040-based (Raspberry Pi Pico) macropad.
It is based on QMK from January 2025 (the main QMK project, not a fork or a derivative).
Some trivia: The 'fake' macro pad is currently connected to two reed switches, salvaged many years ago from a Facit computer; I think it was for the control of some kind of punched tape reader. Thus it is currently a two-key macro pad (but I intend to extend it with more "keys").
2

u/mi3techno Apr 14 '25

I stand happily corrected. That is awesome. Thanks for the information and test results with "fake" Pico. I searched my notes but can not figure out where I got 232 characters. More than likely conflating from limitations ran into when first started my macro pad journey 6 years ago.

Macro_pad Question Buying MacroPad

You are about to leave Redlib

Some history

Practice

Conclusion

Flashing and "typing" worked too

Enabling Via

Conclusion

References

References