view the rest of the comments
ErgoMechKeyboards
Ergonomic, split and other weird keyboards
Rules
Keep it ergo
Posts must be of/about keyboards that have a clear delineation between the left and right halves of the keyboard, column stagger, or both. This includes one-handed (one half doesn't exist, what clearer delineation is that!?)
i.e. no regular non-split¹ row-stagger and no non-split¹ ortholinear²
¹ split meaning a separation of the halves, whether fixed in place or entirely separate, both are fine.
² ortholinear meaning keys layed out in a grid
No Spam
No excessive posting/"shilling" for commercial purposes. Vendors are permitted to promote their products/services but keep it to a minimum and use the [vendor] flair. Posts that appear to be marketing without being transparent about it will be removed.
No Buy/Sell/Trade
This subreddit is not a marketplace, please post on r/mechmarket or other relevant marketplace.
Some useful links
- EMK wiki
- Split keyboard compare tool
- Compare keycap profiles Looking for another set of keycaps - check this site to compare the different keycap profiles https://www.keycaps.info/
- Keymap database A database with all kinds of keymap layouts - some of them fits ergo keyboards - get inspired https://keymapdb.com/
I love the Oryx configurator, but I do wish there was a way to configure layouts locally, without the web interface.
Run it locally? It's Foss right?
Oryx is not open source. Their firmware is a fork of QMK modified for Oryx; I don't think it's compatible with the QMK tools.
As far as I've been able to tell, if ZSA goes out of business and the Oryx configurator goes down, you're forever stuck with whatever configs you've already downloaded - your keyboard becomes, essentially, a dumb keyboard.
All of ZSA's stuff is QMK-compatible. Just load up a QMK config.
That's great to know, thanks! It's all a bit past my knowledge event horizon, but with the verbiage on their website it's hard to tell where they draw the line on closed/open source, and just how much their fork of QMK diverges. Is it 100% feature compatible, or are there ZSA features that can't be programmed with QMK? Like the glow features - that seems to be pretty common nowadays, but macros? All of the double-tap-hold, multiple function programmability? Are there features that are custom to the fork that are only programmable with Oryx? Their website seems to indicate that there are, and this is how they stay profitable.
I think it’s more likely that their firmware is a closer to subset of QMK, because it’s hard to represent everything you can do in code with a GUI.
Features like macros and double tap and hold were in QMK first.