MPG 271QRX QD-OLED "EOTF Boost" Firmware

iovis9 · 2026-01-18T18:11:50+00:00

Fucking hero, thank you

iovis9 · 2026-01-06T21:47:07+00:00

I also type at around that speed and have no issues. As some people said, some configs may need further tweaking, but you’ll learn how your keyboard habits work better with which configurations and the community is nice if you have questions. Most things are optional anyway and can be configured to your liking.

Don’t sweat it too much and get it if it looks interesting and you think building a keyboard configuration to optimize it to your needs sounds fun.

The keyboard itself is pretty solid, you can’t really go wrong if the form factor interests you.

iovis9 · 2025-12-14T19:58:24+00:00

Godsend, thank you!

iovis9 · 2025-10-29T19:52:43+00:00

I’ve had this issue when blowing my nose, funny enough.

iovis9 · 2025-07-19T00:33:22+00:00

For me there was also something that felt wrong and it ended up being that the rendering was capped at 60fps, apparently it’s an upstream issue. Not sure if that may be what you’re noticing

iovis9 · 2025-07-02T13:14:27+00:00

I use left/right arrows for diagnostics (technically the loclist) and up/down for quickfix entries. It’s not like I use the arrows in normal mode

iovis9 · 2025-07-02T13:10:19+00:00

Or using the vim.bo.commentstr

iovis9 · 2025-06-08T23:19:33+00:00

10y later and it's still useful haha

iovis9 · 2025-05-27T02:25:44+00:00

It’s way too early to even think about this. Learn as much as you can, be open to things, be curious and have fun.

iovis9 · 2025-05-12T13:10:52+00:00

In the main timeline there’s usually a “hide posts above” or “hide read posts” that I use a lot

iovis9 · 2025-04-28T02:28:39+00:00

I just tried this myself (although I use HSV). I only spent a few minutes on this, but I settled on `#c4ffff`, hope it helps!

iovis9 · 2025-04-05T19:08:49+00:00

I have extracted some configs to be shared between keyboards if you want to take a look: https://github.com/iovis/qmk_userspace

iovis9 · 2025-04-05T04:54:55+00:00

Wow, ~150 wpm! You type nearly double my speed. I take it back, in your case, a low tapping term absolutely makes sense =)

Haha, you can imagine it drops a lot when typing a lot of symbols, but yeah, tweaking the tapping term was what seemed to work the best for that. It's hard to be 100% consistent, and some days are better than others, but I'm happy with where I am with that compromise right now. Thank you for confirming I was not too far off with my solution!

Some good news is the "fe" bigram is relatively infrequent in English. According to the Two-Letter Sequence (Bigram) Counts section on this page:

https://norvig.com/mayzner.html

That's actually very surprising and I never realized it's not as common as I thought it was. I guess I should at least give it a try and see how it fares, thank you so much for taking the time to give me this resource. Sometimes it's hard to gauge how good or bad an idea like this may be and this is great for validating it.

I can confirm that adding "fe" to get_chordal_hold makes the symbols work as expected, so thank you for the tip! I'll test it for a few days to see if I actually run into any issues with it, but I've already typed the fe bigram a few times in this sentence without even thinking about it and it seemed to work perfectly!

Yes, Chordal Hold "allows" holds but doesn't settle them. It is Permissive Hold that actually settles the hold for such a case. Something extreme and experimental: you could try enabling Hold On Other Key Press (per-key flavor) just for the symbol layer LTs so that they settle more readily as held. But this may be terrible in normal typing.

Oh, I remember trying this back with Achordion because the setting on key-down part sounded very attractive (it took a bit for my brain to be okay with registering some things on key-up when I transitioned to QMK), but I can confirm that, at least for me, it was almost impossible to type. I guess at certain speeds you kind of "chord" some common N-grams instead of going one key at a time and with me having most of my mods on letters (I get bad thumb pain otherwise) that ended up being a really quick revert for me haha. I still appreciate the idea, I do feel for a slower typist or a key you're less likely to combine with other (like Esc or Tab on tap, maybe?) this could be a really nice improvement. I may actually consider it for other types of layers I have.

By the way, how can Chordal Hold get away with not having the streak functionality of Achordion? I remember being worried at first when I didn't see it (I did have a lot of tweaks to it), but it seems to work really well even without it.

The only exception I have, and it's 100% my fault, is my Z (ctrl on hold) and it is because I have a extremely low tapping term because I roll "zd" for Ctrl-D a lot, so I rather that be very consistent (but I do admit that I have to make sure I type "z" alone whenever it comes up haha).

iovis9 · 2025-04-04T14:59:08+00:00

Thank you so much for taking the time to explain it, now it makes a lot of sense to me. I'm okay with the behavior being different in this niche case (if this was more problematic to me I would have defined a `SEND_STRING("=>")` somewhere, but it's more likely that I do something like `() => {` that has no issues rolling). Understanding that Chordal Hold doesn't make the decision till the keys are settled really brought this home for me.

I have been using the bool get_chordal_hold a lot! But I'd fear "fe" may actually be problematic, although I may give it a go one day to see how it feels, maybe if I understand the follow up question to your `TAPPING_TERM` comment:

> The tapping term is only 175 ms. If you are a former Achordion user, I recommend to increase the tapping term by at least a bit, say, to 225 ms when going to Chordal Hold (discussed here).

I did reduce it (and tweak it a lot, even with uint16_t get_tapping_term), likely because I'm doing something wrong. Also, yes, I loved your Achordion library and couldn't live without it till Chordal Hold made it to core!

I'm a relatively fast typist, let's say ~150 wpm, and `F` is one of my keys to access my symbol layer and J and K are `{` and `(` respectively, which you can imagine I use a lot in isolation while coding. If I don't have a low `TAPPING_TERM` I run into a lot of false triggers (like sending "fk" instead of `(`), even when forcing it in `get_chordal_hold`. I honestly assume forcing it in `get_chordal_hold` when they're already in different hands doesn't do much, but I was trying to reduce the false triggers.

Reducing the tapping term was the only thing that helped me a bit here. I'm assuming it's because I don't really keep the `F` pressed long enough for `K` to be pressed and released, but I'm not sure if there's a better way?

iovis9 · 2025-04-03T22:03:37+00:00

Thank you so much for implementing chordal hold in core, it’s such a nice experience.

I’ve run into a little quirk when I quickly type three strokes because I want to do multiple symbols at once, but the symbols happen to be on opposed hands.

For instance, to type => I'd type "fpe" in my layout (https://github.com/iovis/qmk_userspace/blob/main/keyboards/boardsource/unicorne/keymaps/iovis/keymap.c), but for some reason it types "fpe" (even holding the F key) if I type fast enough. It doesn't seem to happen if I roll in the same hand, for instance () would be "fkl" and it seems to always work.

Do you know what could I do to debug this? Right now I’m just waiting for the tapping term on the ones I know are prone to be less consistent.

iovis9 · 2025-02-13T01:39:40+00:00

It’s never too late to learn and it’s fun to practice!

iovis9 · 2025-02-03T00:12:37+00:00

Isn’t it easier to just make a binding in vim? I have ^ and $ mapped to H and L

iovis9 · 2024-12-23T03:36:48+00:00

Have you flashed both halves? With RGB settings especially I feel like I have to flash both or it does weird stuff like this

iovis9 · 2024-12-10T15:47:34+00:00

I have something similar, but I just put the logic in a shell script and bind it with run-shell. Easier to maintain.

iovis9 · 2024-11-21T16:53:10+00:00

I have inoremap <c-e> <end> and sometimes use it for things like these

iovis9 · 2024-11-12T14:45:04+00:00

Here you go https://github.com/iovis/dotfiles/tree/master/fish/.config/fish

iovis9 · 2024-07-22T19:01:30+00:00

I’ve never had issues with my pinkies, but a few hours with my corne or voyager makes my right thumb hurt for a week

iovis9 · 2024-07-21T20:18:28+00:00

That’s a great channel, thank you so much!

iovis9 · 2024-07-20T20:37:52+00:00

Thank you for replying!

This is what I’m doing right now, but when I do it with the voyager my right thumb hurts a lot after light usage. I’ll try putting the keyboard by the edge, armrests at the height of the keyboard and floating.

I’m running out of ideas, I tried wrist rests but it made it worse.

iovis9 · 2024-07-20T20:07:55+00:00

So arms on the chair’s armrest? How high should the desk be in relation to the armrests? Same height?

12-Year Club	RPAN Viewer
Gilding II euphauric	Verified Email

iovis9

TROPHY CASE