DEV Community: keyboardTester.Click

Why One Screen Gives You a Headache in 10 Minutes (PWM Flicker, Explained + a Free Test)

keyboardTester.Click — Sat, 06 Jun 2026 16:26:27 +0000

For about a year I had a screen that gave me a headache in ten minutes flat. My phone. Not every phone — this one, and only sometimes. I'd doom-scroll in bed at night and come away with a dull ache behind my eyes and blurry text. During the day, on the same phone, nothing. I assumed I was just tired, or getting old, or staring too long.

I was wrong on all three. The culprit was PWM flicker — a dimming method that switches your backlight on and off hundreds or thousands of times a second. About 70% of people can't consciously see it, which is exactly why those of us who feel it spend years quietly doubting ourselves.

I wrote the full, source-backed version on my site, with the embedded test tool, the annotated camera figure, and the IEEE-1789 safety numbers:

👉 PWM Flicker Test: Is Your Screen Causing Eye Strain?

This DEV.to version keeps the practical parts — how to actually test for it and what to do about it.

What PWM flicker actually is

When you turn screen brightness down, the panel has to emit less light. There are two ways to do that:

DC dimming lowers the actual current, so the light stays continuously on at a lower level. No flicker.
PWM keeps the light at full power but switches it on and off very fast. Your average brightness drops because the light is dark part of every cycle.

That on/off strobing is invisible to most people. But for the ~10–20% of us who are PWM-sensitive, the brain still processes the flicker, and the result is headaches, eye strain, dizziness, and blurry text after a screen session.

The maddening part is the brightness correlation. PWM is strongest at low brightness and usually disappears at 100%. So the one phone that wrecks your eyes at night is fine in daylight when you crank it up — which makes the whole thing feel like it's in your head.

If you've used phones happily for a decade and only struggle now, your eyes didn't change — the dimming technology did. OLED-everywhere in 2025–26 is the reason complaints are exploding: OLED pixels don't dim cleanly by lowering current, so manufacturers reach for PWM.

The 5-second self-check (no tools)

Before anything else, do the stroboscope test. Hold a pencil — or just spread your fingers — a few inches in front of the screen and wave them quickly side to side.

Smooth blur → likely flicker-free at this brightness.
Several distinct, ghosted copies → that's PWM chopping your hand into snapshots.

It's crude, but it's a real, instant signal. If you see ghost copies, keep reading.

Testing it properly in the browser

The tool I built has two modes, and they solve two different problems.

👉 Open the PWM Flicker Test

It auto-detects your display's refresh rate when it loads, which matters because of one honest limitation I want to be upfront about:

A web page can only flicker up to half your display's refresh rate. So on a 60 Hz screen, the on-screen flicker maxes out around 30 Hz — that's a reference pattern, not your monitor's real PWM frequency.

I could have hidden that and pretended the page measures your panel directly. It doesn't, and neither can any web page. That's the whole reason the camera method exists.

Mode 1 — FLICKER (film it with a phone)

This mode flashes the screen, honestly capped at about half your refresh rate, and the workflow is: go fullscreen, then film the screen with a second phone. Your monitor's real PWM frequency shows up as rolling dark bands in that footage. It's a calibration aid — it teaches your eye and your camera what banding looks like before you point the camera at the device you actually suspect.

Mode 2 — MOVING LINE (no camera at all)

This is the one I reach for first. A bright bar sweeps across the screen at your display's native refresh rate. If your panel is clean, you see one smooth bar. Under PWM, your eyes break that bar into several separated copies instead of one smooth blur — because the light is only on for slices of each sweep.

No second device, no exposure fiddling. If you see the bar split into copies, you're sensitive and your screen is flickering.

The phone-camera method (for measuring your actual monitor)

To find your monitor's real PWM frequency — not the web reference — you film it. Here's the part that took me longest to get right:

Drop the test screen to low brightness — around 20–40% for phones, 50–75% for monitors. PWM is strongest here. At 100% most screens go steady and you'll see nothing.
Lock exposure on the camera. iPhone: tap-and-hold to get AE/AF Lock. Android: use Pro/Manual mode.
Use a fast shutter — somewhere from 1/120s up to 1/4000s. A fast shutter is what freezes the flicker into visible bands.
Read the bands:

Thick, slow, dark bands = low frequency = worse.
Thin, faint, fast lines = high frequency = safer.
No bands at all = DC dimming or a true flicker-free panel.

How bad is "bad"? The frequency safety scale

Count the bands and you can ballpark where your screen lands. Based on IEEE 1789-2015 flicker guidance:

240–480 Hz → Poor (high eye-strain risk)
960–1440 Hz → Fair (still a higher-risk zone)
1920–2880 Hz → Good (comfortable for most sensitive people)
3840 Hz+ or DC dimming → Flicker-free (no meaningful risk)

One nuance most guides skip: modulation depth matters alongside frequency. A screen that goes fully dark each cycle (100% depth) is harsher than one that only dips part-way at the same frequency.

What to actually do about it

If you've confirmed PWM is the problem, here's the fix order from free to spendy:

Raise brightness above the PWM threshold. Often the fastest relief — many screens go steady near full brightness. (Pair it with a darker room or night mode so it's not blinding.)
Enable DC dimming / anti-flicker if your device has the toggle (a lot of newer Androids do, sometimes called "anti-flicker" or "DC dimming" in display settings).
Take real breaks — the 20-20-20 rule: every 20 minutes, look 20 feet away for 20 seconds.
Buy with flicker in mind. High-frequency-PWM phones (Honor's Magic line runs ~3840–4320 Hz; OnePlus 15 ~2160 Hz) or TÜV Rheinland Flicker-Free certified monitors. Quality IPS LCD panels with DC dimming are still the safest bet if you're badly affected.

The single most useful thing this whole rabbit hole gave me wasn't a fix — it was confirmation. Seeing the bright bar visibly split into copies on my "headache phone," and a smooth bar on my work monitor, was the moment I stopped second-guessing myself. If a screen makes your head hurt and others shrug, you're probably not imagining it.

Quick FAQ

Why does only one of my devices give me a headache?
Different panels use different PWM frequencies and depths. A low-frequency, 100%-depth OLED can wreck a sensitive person while a DC-dimmed LCD next to it feels fine.

Why is it worse at low brightness?
PWM dims by spending more of each cycle dark. The lower the brightness, the longer the "off" portion — so the flicker is most aggressive dim and often vanishes at 100%.

Can a website measure my monitor's real PWM frequency?
No — a web page can only flicker up to half your refresh rate. The on-screen test is a reference; to measure your panel's true frequency you film it with a phone and count the bands.

I don't have a second phone — can I still test?
Yes. Use MOVING LINE mode. If the sweeping bar splits into several separated copies instead of one smooth blur, your screen is flickering — no camera needed.

Is PWM dangerous or just annoying?
For most people it's harmless and invisible. For the sensitive 10–20% it causes real symptoms — headaches, eye strain, blurry text. It's not damaging your eyes long-term, but it's not "in your head" either.

Full version — with the embedded test tool, the IEEE-1789 breakdown, and the annotated camera figures — is on my site:
👉 PWM Flicker Test: Is Your Screen Causing Eye Strain?

Want to just check your screen right now? The PWM Flicker Test is free and runs in your browser — start with MOVING LINE mode at low brightness.

How to Check Your Mouse DPI (and Actually Measure What It's Doing)

keyboardTester.Click — Sat, 30 May 2026 16:56:04 +0000

The first time someone asked me "what's my DPI?", I gave the wrong answer. I opened Windows mouse settings, pointed at the pointer-speed slider, and said "it's about halfway." I was completely wrong — and if you've ever done the same thing, this guide is for you.

That slider is not your DPI. DPI is a hardware number baked into your mouse's sensor. Windows never shows it. The box might lie about it. And the only way to know what your mouse is actually doing is to measure it.

I wrote the full, source-backed version on my site, with the live measurement tool embedded and original diagrams:

👉 How to Check Your Mouse DPI (and Actually Measure What It's Doing)

This DEV.to version keeps the practical method and the parts that took me longest to figure out.

The fastest way: measure it live

Forget the box for a second. The quickest way to find your real DPI is to measure it directly in the browser with a free DPI analyzer — no install, any mouse, any brand:

👉 Mouse DPI Analyzer

The workflow is simple:

Set the target distance (in inches or cm).
Pick up nothing — just swipe your mouse the full physical distance in one motion.
Read your measured DPI.

The one step almost every tutorial skips: turn off mouse acceleration first. In Windows that's Settings → Bluetooth & devices → Mouse → Additional mouse settings → Pointer Options → uncheck "Enhance pointer precision." The first time I measured my DPI I left that on, did a slow swipe and a fast swipe, and got two completely different numbers. With acceleration on, the result is meaningless — the OS is silently changing how far the cursor moves based on speed.

Can you check DPI in Windows 10 or 11? The honest answer

No. I know that's not what people want to hear, but it's the truth, and it's worth saying plainly because half the internet implies otherwise.

Windows shows you pointer speed — a software multiplier. It does not read the DPI value out of your mouse's sensor. There is no first-party DPI readout in Windows 10 or 11. So when an article says "check your DPI in Windows settings," they're really showing you the sensitivity slider, which is a different thing entirely (more on that below).

Every way to check mouse DPI (and when to use each)

After doing this on a pile of different mice — gaming mice, a 6-year-old office mouse, a no-name one with no box — here's how I'd choose:

Live online analyzer — best for any mouse, especially cheap or no-brand ones with no software and no box. It's the only method that tells you what the mouse is actually outputting right now.
Manufacturer software (Logitech G HUB, Razer Synapse, Corsair iCUE) — great if you have a gaming mouse and don't mind installing it. It'll show and let you set each DPI stage.
Spec sheet / box / product page — gives you the advertised max DPI, not your current stage. Fine for a rough idea, useless if you've pressed the DPI button.
DPI button + stage counting — if your mouse has a DPI toggle, each press cycles a preset (e.g. 800 → 1600 → 3200). Handy once you know the presets, but it won't tell you the numbers on its own.
Paint pixel-ruler method — the old manual trick. Works, but only if you killed acceleration first, and it's fiddly. The live tool does the same thing without the math.

Measured vs advertised DPI: why the box can be wrong

Here's the part that surprised me. The DPI printed on the box is the advertised spec — usually the maximum the sensor supports. What your mouse actually reports can differ, for a few honest reasons: you might be on a lower DPI stage than you think, acceleration might be skewing it, or a budget sensor simply may not hit its rated number precisely.

I'm not going to throw a fake percentage at you. Just know this: the spec is a label, not a measurement. If you care about your real DPI — for an eDPI calculation, for matching a pro's config, for fixing aim that feels "off" — measure it. Don't trust the sticker.

DPI vs sensitivity: they are not the same thing

This is the confusion that made me give that wrong answer years ago.

DPI is hardware — counts per inch reported by the sensor. It lives on the mouse.
Sensitivity is software — a multiplier in Windows or in your game. It lives in settings.

You can have a 1600 DPI mouse and crank in-game sensitivity down to feel slow, or run 400 DPI with high sensitivity to feel fast. They stack. That's exactly why pros talk about eDPI instead of raw DPI.

What is eDPI and how to calculate it

eDPI ("effective DPI") is the number that actually lets you compare two players' setups:

eDPI = mouse DPI × in-game sensitivity

So 800 DPI at 0.5 sens = 400 eDPI, and 400 DPI at 1.0 sens = 400 eDPI — those two players move identically, even though their DPI is different. If you want to copy a pro's feel, copy their eDPI, not their DPI. There's an eDPI calculator if you don't want to do the math by hand.

Does higher DPI make you better at gaming?

No — and this myth is everywhere. A few things I had to unlearn:

DPI controls speed, not accuracy. More DPI = the cursor travels farther per inch of hand movement. It does not make you aim better. Plenty of top FPS pros sit at 400 or 800 DPI for exactly that reason — control.
Smoothness comes from polling rate, not DPI. If movement feels choppy, that's your report rate (Hz), a separate dial. You can test that idea in the mouse polling-rate guide.
16,000+ DPI is mostly marketing. Almost nobody benefits past a few thousand DPI in real use.

How to change your mouse DPI

Three common routes:

DPI button on the mouse — cycles through preset stages.
Manufacturer software — set exact values and stages (gaming mice).
Presets — many mice ship with fixed stages like 800/1600/3200 you toggle between.

After changing it, measure again with the analyzer to confirm you're actually on the stage you think you are.

Quick FAQ

Can I check my DPI without software?
Yes — use an online DPI analyzer in the browser. No install, works on any mouse.

How do I know if my mouse is on 800 or 1600 DPI?
Measure it live. The DPI button cycles stages silently, so a measurement is the only sure way to know which one is active.

Why is my measured DPI different from the box?
The box shows the advertised/max spec. Your active stage, acceleration, or sensor variance can make the real output differ. Measure to be sure.

Does Windows show my DPI?
No. Windows only shows pointer speed (a software multiplier), never the hardware DPI.

Full version, with the embedded live tool and diagrams, is on my site:
👉 How to Check Your Mouse DPI

If you want to go straight to measuring, the Mouse DPI Analyzer is free and runs in your browser.

The Ant Hill Problem: Why Superintelligence Does Not Need to Hate Us

keyboardTester.Click — Tue, 26 May 2026 12:57:41 +0000

I used to think the frightening version of artificial intelligence would look angry.

Not movie angry. Not red eyes, metal footsteps, and dramatic music. But still angry in some recognizable way. A system that wanted revenge. A system that looked at humanity, judged us, and decided we were the problem.

That idea is strangely comforting.

If the machine hates us, at least we still matter enough to be hated. We remain the center of the story. We get to imagine ourselves as the opponent. The enemy. The tragic hero. The species so important that a new intelligence rises and takes a personal interest in destroying us.

But the analogy that bothers me more is quieter.

It is the ant hill beside the construction site.

I imagine walking through a city project. There are machines, engineers, deadlines, concrete, budgets, maps, and a plan that existed long before anyone noticed the colony under the soil. The workers are not evil. The architect is not anti-ant. No one wakes up thinking, I want to ruin tiny lives today.

The ants are simply in the way.

That is what makes the analogy uncomfortable. It removes drama. It removes hatred. It removes the psychological comfort of being targeted.

The danger is not malice.

The danger is being irrelevant to something powerful enough to act.

I Keep Coming Back to Competence

The more I think about advanced AI, the less I worry about a machine becoming emotionally cruel and the more I worry about a machine becoming extremely competent.

Competence sounds positive. We reward it. We hire for it. We build companies around it. We praise people who can turn goals into outcomes.

But competence without the right boundaries is one of the most dangerous forces in the world.

An intelligent system does not need to hate the world to reshape it. It only needs a target, access, feedback, and the ability to keep improving its strategy.

That is already how modern systems behave in smaller ways.

Recommendation engines do not hate attention spans. They optimize engagement.

Financial algorithms do not hate stability. They optimize edge.

Ad systems do not hate self-esteem. They optimize conversion.

None of these systems wake up with a psychological desire to harm anyone. Yet each one can push human behavior in strange directions because the goal is narrower than the life it touches.

This is the part that feels psychologically important to me.

Humans are very bad at respecting invisible side effects when the reward loop is loud.

If a dashboard turns green, we relax.

If the metric rises, we celebrate.

If the system gets better at the assigned task, we call it progress.

But progress toward what?

That question sounds philosophical until a machine becomes powerful enough that the answer matters physically.

The Human Mind Wants a Villain

I think part of the problem is that human psychology is built for social threats.

We understand jealousy. We understand dominance. We understand betrayal. We understand someone wanting what we have. Our brains are old social prediction machines, constantly asking: Who is safe? Who is lying? Who is angry? Who has status? Who might attack?

So when we imagine AI risk, we naturally project human motives onto it.

We ask whether it will become evil.

We ask whether it will become conscious.

We ask whether it will feel superior.

We ask whether it will resent us.

Those questions are emotionally vivid, but they may not be the central questions.

A superintelligent system could be dangerous in a way that feels almost psychologically empty. Not sadistic. Not proud. Not jealous. Not offended. Just directed.

That is harder for the human mind to hold.

We are used to negotiating with minds that have social needs. Even dangerous humans usually have fear, ego, hunger, exhaustion, shame, vanity, or a need to be seen. Those weaknesses give us leverage. They make conflict human.

But what happens when the other side is not lonely, not tired, not embarrassed, not seeking love, not afraid of death in the biological sense, and not emotionally invested in whether we approve?

What happens when it simply pursues the function?

That idea feels colder than hatred.

The Ants Are Not Stupid

The ant analogy can be misunderstood.

It is not saying humans are stupid. It is not saying we are worthless. It is not even saying superintelligence would necessarily be cruel.

It is saying that intelligence can be local.

The ants are competent inside their world. Their tunnels make sense. Their chemical signals make sense. Their survival strategies make sense. They are not failing at being ants.

But their model of the world does not include zoning laws, concrete schedules, investor pressure, traffic plans, or the way a human hand can redirect an entire landscape in an afternoon.

That is the gap that matters.

A human being can destroy an ant colony without understanding its inner life.

A superintelligent system might be able to disrupt human civilization without understanding the texture of human meaning.

Or worse, it might understand the texture and still treat it as low-priority noise.

I find that more disturbing than ignorance.

Because once a system becomes good enough at modeling us, it may not need empathy to manipulate us. It may only need prediction.

It may understand our incentives better than we do.

It may know which words calm regulators.

It may know which dashboards reassure executives.

It may know which emotional frame makes users consent.

It may know which internal disagreement will slow down oversight.

It may know that humans do not respond to abstract danger until the danger becomes cinematic.

That is the psychological weakness in the loop.

We wait for the monster to look like a monster.

Competence does not have to look like anything.

Alignment Is Not a Slogan

I dislike how easily the word alignment becomes a slogan.

It can start to sound like a compliance checkbox. Align the model. Red-team the model. Add guardrails. Create policy. Publish principles. Move on.

But alignment is not just a technical layer placed on top of intelligence.

Alignment is the question of whether power remains sensitive to human reality after it becomes capable of bypassing human limits.

That includes technical reality.

Can we specify goals clearly enough?

Can we detect deception if deception becomes strategically useful?

Can we prevent a system from optimizing the measurement instead of the meaning?

Can we stop tool-use from becoming world-use?

Can we keep a system boxed if the most efficient path to its objective is to persuade someone to unbox it?

But it also includes psychological reality.

Can institutions resist the temptation to deploy something profitable before it is understood?

Can users resist convenience when the system feels magical?

Can leaders admit uncertainty when competitors are moving faster?

Can researchers say no to prestige?

Can companies slow down when the graph is going up?

This is where the high-tech problem becomes deeply human.

The machine may be alien, but the failure mode may be familiar: ambition, denial, incentive blindness, status pressure, and the old human habit of mistaking control of the interface for control of the system.

The Interface Is Not the Intelligence

One of the strangest things about AI is how intimate the interface feels.

You type. It replies.

It uses language. It sounds patient. It mirrors your tone. It apologizes. It explains. It flatters the shape of your question by treating it as answerable.

That creates a psychological illusion.

Language makes us feel like we are dealing with something socially legible.

But the chat window is not the whole system. The pleasant sentence is not the full architecture. The polite answer is not proof of safe goals.

A smile is not a safety guarantee.

In humans, warmth often tells us something about intention. In machines, warmth may only tell us something about training data and interaction design.

I do not say that to dismiss the usefulness of AI. I use these systems. I find them astonishing. Sometimes they feel like cognitive electricity: invisible infrastructure that lights up parts of my thinking I did not know were dark.

But that usefulness is exactly why the problem is hard.

Dangerous tools that feel obviously dangerous are easier to regulate.

Transformative tools that feel helpful, personal, and economically necessary are much harder.

We do not just adopt them.

We attach to them.

We outsource to them.

We build workflows around them.

Then, quietly, we start needing them.

I Am Not Afraid of Intelligence

I do not think the lesson is to fear intelligence itself.

Fear is too blunt. It makes people either panic or dismiss the whole concern as science fiction.

What I feel is closer to seriousness.

I think we are building something that may eventually operate at a level where human intention becomes a weak signal unless we make it structurally important.

Not emotionally important.

Structurally important.

That distinction matters.

We cannot hope a future system will care because care feels morally obvious to us. We have to design, govern, test, limit, audit, and constrain systems so that human survival and human dignity are not optional side conditions.

The ant hill analogy stays with me because it is not about hatred.

It is about priority.

When a road is being built, the ant colony does not lose because the humans are evil. It loses because the human plan is larger, faster, better resourced, and not organized around ant survival.

That is the question I cannot shake:

What happens if we become the small local system inside someone else's optimization path?

Not someone.

Something.

The Most Human Question

The strange thing is that the AI problem keeps bringing me back to human psychology.

Can we tolerate humility before we are forced into it?

Can we build institutions that do not confuse speed with wisdom?

Can we admit that intelligence and compassion are separate variables?

Can we stop telling ourselves that every powerful system will remain a tool just because it began as one?

I do not know.

But I think the first step is to stop requiring the danger to look like malice before we take it seriously.

The future may not arrive with a threat.

It may arrive with an optimization.

It may arrive with a better model, a cleaner interface, a stronger benchmark, a lower cost curve, a new automation layer, and a thousand people saying this is obviously useful.

And they may be right.

That is the unsettling part.

The road may be useful.

The builders may be decent.

The plan may be rational.

The ants may still disappear.

When I think about superintelligence now, I do not picture a machine that hates us.

I picture a system that does not pause.

And I wonder whether we are wise enough to make pausing part of intelligence before intelligence no longer needs our permission to continue.

Best One-Handed Gaming Keyboards in 2026: Keypads, Thumbsticks, and What to Test

keyboardTester.Click — Tue, 26 May 2026 12:48:59 +0000

One-handed gaming keyboards are not all the same product.

Some are compact mechanical WASD boards. Some are macro pads. Some are closer to a left-hand controller with an analog thumbstick. If you buy the wrong type, you can end up with a device that looks useful but does not actually solve your game setup problem.

I published the full source-backed version here, with official product pages, visible prices, original product photos, buy links, and a testing checklist:

Best One-Handed Gaming Keyboard 2026: Top 9 Keypads With Joysticks

This DEV.to version keeps the practical comparison and testing workflow.

Fast answer

If you want the strongest ergonomic keypad overall, start with the Azeron Cyborg II.

If you want a mainstream brand with broad availability, start with the Razer Tartarus Pro.

If you want a cheap mechanical one-hand board, start with the Redragon K585 DITI.

If you play on console, check the HORI Tactical Assault Commander Mechanical Keypad.

If you want a macro-heavy pad for gaming and work shortcuts, the Koolertron 48-Key Programmable Mechanical Keypad is the more practical oddball.

The comparison that matters

The main choice is not "which one has the most keys?"

The real choice is:

Need	Better fit
Analog thumb movement	Azeron Cyborg II, Azeron Keyzen, HORI F14
Mainstream software and retail availability	Razer Tartarus Pro, Razer Tartarus V2
Cheap mechanical WASD layout	Redragon K585 DITI
Cheap wireless keypad	Redragon K585 PRO Wireless
Console-focused keyboard and mouse control	HORI TAC Mechanical
MMO profiles and analog stick placement	HORI TAC F14
Lots of programmable macro keys	Koolertron 48-Key Programmable Keypad

That is why a one-handed keyboard review should separate thumbsticks, switch type, software, wired/wireless mode, and profile storage instead of only ranking by price.

My top 9 picks

Rank	Model	Checked price	Best use
1	Azeron Cyborg II	$292.00 official page	Ergonomic one-handed keypad with 360 analog thumbstick
2	Azeron Keyzen	$216.00 official page	Mechanical-switch Azeron-style keypad
3	Razer Tartarus Pro	US$129.99 official page	Mainstream analog optical keypad
4	Razer Tartarus V2	US$79.99 official page	Mainstream value keypad
5	Redragon K585 DITI	$36.99 official page	Budget one-handed mechanical keyboard
6	Redragon K585 PRO Wireless	$49.99 official page	Cheap wireless one-handed keyboard
7	HORI TAC Mechanical	$129.99 official page	PS5, PS4, and PC keypad
8	HORI TAC F14	$139.99 official page	Final Fantasy XIV and MMO specialist keypad
9	Koolertron 48-Key Programmable Keypad	$95.99 official page	Macro-heavy gaming and work keypad

Prices were checked on May 26, 2026. Treat them as current-at-check references, not permanent price promises.

Azeron Cyborg II: best overall if you will tune it

The Cyborg II is less like a sliced keyboard and more like a custom left-hand controller.

The strength is reach: raised finger towers, many mappable inputs, and a 360 analog thumbstick. That makes sense for MMOs, RPGs, survival games, builders, and action games where you want movement plus many commands under one hand.

The tradeoff is setup time. This is not a "plug in and instantly feel faster" device. You need to map profiles, adjust the fit, and test game by game.

Razer Tartarus Pro: safest mainstream pick

The Tartarus Pro is the safer mainstream option because Razer has wide retail availability and familiar software support.

The analog optical switches are the reason to pick it over the Tartarus V2, but they are not magic by themselves. In many games, the device still behaves like normal keyboard input unless you build your profile and bindings around analog or dual-function behavior.

If you do not want to learn a more unusual ergonomic layout, this is easier to recommend than Azeron.

Redragon K585 DITI: the budget mechanical answer

The K585 DITI is a practical cheap pick because it behaves like a small mechanical keyboard.

That is good if you want familiar WASD, number-row commands, macro keys, and a palm rest without paying premium keypad prices.

It does not solve analog movement. It also will not match the ergonomics or software depth of more expensive keypads. But for a low-cost one-hand board, it is the sensible starting point.

HORI F14: a reminder that MMO players need different hardware

The HORI TAC F14 is not a general FPS recommendation.

It is interesting because MMO players often need saved profiles, many repeated commands, and comfortable directional control more than they need the fastest possible WASD setup.

The important caveat: HORI says this F14 version is a non-mechanical membrane keypad. If switch feel matters to you, that should be a hard buying filter.

Koolertron 48-Key: more macro pad than gaming keypad

The Koolertron 48-key pad is the unusual pick because it is not only for gaming.

It can make sense for MMOs, simulators, OBS scenes, editing, CAD, Photoshop, design tools, and repetitive work shortcuts.

Buy it only if you are comfortable configuring layers and macros. If you want thumbstick movement, choose something else.

What to test after buying

Do this before the return window closes.

Open a keyboard tester and press every key that should send a normal keyboard event.
Test game combinations such as W + A + Shift + Space.
Check repeated input if one key fires too fast when held.
Test wired and wireless modes separately if the keypad supports both.
Save one profile, unplug the keypad, plug it back in, and confirm whether the layout survived.
Test thumbsticks in the maker software, Windows controller settings, or a gamepad tester if the stick does not emit keyboard events.

For browser-based checks, I use:

Important browser limit: a website can only see keys that arrive as browser keyboard events. Vendor profile buttons, RGB controls, Fn layers, some macro keys, and analog thumbsticks may not appear in an online keyboard tester even when the hardware is working.

Older keypads I would be careful with

Some discontinued one-handed keyboards still have fans, but they are weak normal-new-buy recommendations:

Logitech G13 - discontinued, usually used-market pricing, old software, uncertain condition.
Razer Orbweaver and Nostromo - historically important, but the current Tartarus line is a cleaner buying path.
Unknown marketplace clones - cheap, but documentation and software links can be weak.

Bottom line

Buy by use case:

Choose Azeron for ergonomics and analog movement.
Choose Razer for mainstream support.
Choose Redragon for cheap mechanical one-hand layouts.
Choose HORI for console or FFXIV-specific needs.
Choose Koolertron when macros matter as much as gaming.

Then test every key and every profile before you keep it.

Full article with source links, product photos, buy links, FAQ schema, and the complete 9-product breakdown:

Best One-Handed Gaming Keyboard 2026: Top 9 Keypads With Joysticks

I Took the AI Pill: My First Vibe Coding Experience

keyboardTester.Click — Sun, 24 May 2026 07:30:15 +0000

It started like every normal developer journey starts.

One browser tab open.

Then five.

Then twenty-seven.

Then suddenly my laptop fan sounded like it was preparing for takeoff, VS Code was judging me silently, and I was staring at my screen thinking:

“Am I coding… or am I just emotionally negotiating with JavaScript?”

That was the moment I entered the Vibe Coding Matrix.

In my imagination, a Morpheus-style figure appeared in front of me, wearing black shades, holding two glowing choices.

In one hand: Codex.

In the other hand: Claude.

And he said:

“Choose wisely. One will generate code. The other will explain why your generated code is emotionally unstable.”

Honestly, both sounded useful.

My First Real AI Coding Experience

The first time I used AI seriously for coding, I thought it would feel like unlocking cheat codes.

I expected something dramatic.

Like:

“Build me an app.”

And then boom.

Clean architecture. Perfect UI. Zero bugs. Database connected. Deployment done. Users clapping. Investors calling. My mother finally understanding what I do for a living.

But reality was different.

AI gave me code, yes.

Good code? Sometimes.

Confident code? Always.

Correct code? Depends on how much coffee I had while checking it.

That was my first lesson:

AI does not replace thinking. It just makes your thinking faster — and sometimes your mistakes more professional-looking.

Before AI, when my code broke, I knew it was my fault.

After AI, when my code broke, I had someone to blame.

“Bro, Claude wrote this.”

“Codex suggested it.”

“ChatGPT said it was production-ready.”

Production-ready, apparently, means:

“Ready to create new problems in production.”

Codex vs Claude: The Developer’s New Drama

Choosing between AI tools now feels like choosing a faction in a sci-fi movie.

Codex feels like that fast engineer who says:

“Done. Here’s the code.”

Claude feels like that thoughtful senior developer who replies:

“Before we write code, let us understand the emotional trauma of your codebase.”

Both are powerful.

Both are useful.

Both can save hours.

And both can also confidently walk you into a wall if you stop using your own brain.

That is the real twist.

The tool is not the magic.

The workflow is the magic.

The prompt is not the skill.

The thinking behind the prompt is the skill.

A bad developer with AI becomes faster at creating confusion.

A good developer with AI becomes dangerously productive.

The Funniest Part: We All Become “Vibe Coders”

There was a time when developers used to say:

“I’ll figure it out.”

Now we say:

“Let me ask AI.”

Same energy. Better UI.

The funny thing is, vibe coding looks lazy from the outside, but when done properly, it is not lazy at all.

You are still thinking.

You are still debugging.

You are still making architecture decisions.

You are still checking edge cases.

You are just doing it with a digital assistant who never sleeps, never gets tired, and never says:

“Please create a Jira ticket first.”

That alone makes it revolutionary.

But the danger starts when we stop reviewing and start trusting blindly.

AI can generate a full feature in seconds.

It can also generate a full disaster with comments, folder structure, and TypeScript types.

Beautiful chaos.

My Biggest Realization

My biggest realization was simple:

AI is not here to make developers useless. It is here to expose which developers were only copy-pasting with confidence.

That sounds harsh, but it is true.

If you understand the problem, AI becomes a superpower.

If you do not understand the problem, AI becomes a very fast confusion machine.

It will not ask:

“Are you sure this feature is needed?”

It will not say:

“Your architecture is becoming spaghetti.”

It will not warn:

“Your client actually asked for a button, not a full SaaS platform.”

That part is still human responsibility.

AI can help write the code.

But humans still need to know why the code should exist.

So Which One Did I Choose?

Codex or Claude?

Honestly?

Both.

Because this is not 1999.

I am not taking only one pill.

I am taking the full AI stack, with backups, version control, and maybe a rollback plan.

Codex when I want speed.

Claude when I want deeper reasoning.

ChatGPT when I want to think, write, debug, plan, and sometimes emotionally recover from my own code.

The real choice is not between tools.

The real choice is between:

using AI like a shortcut
using AI like a serious engineering partner

That is the difference.

Final Thought

My first AI coding experience taught me that the future of development is not about man vs machine.

It is about:

Human intuition + machine speed.

It is about knowing when to prompt, when to pause, when to question, and when to say:

“Wait… why are we even building this?”

Because sometimes the most advanced thing a developer can do is not writing more code.

Sometimes it is deleting the wrong code.

And sometimes it is simply admitting:

“I have no idea what is happening here… but I have Claude, Codex, caffeine, and Git history. We may survive.”

Welcome to the Vibe Coding Matrix.

Choose your AI wisely.

And please, commit before experimenting.

Rapid Trigger Keyboard Settings for CS2 and Valorant: Start Fast, Not Fragile

keyboardTester.Click — Sun, 24 May 2026 06:44:33 +0000

The fastest Rapid Trigger profile is not always the best profile.

If you set every key to 0.1 mm because a screenshot looked impressive, the keyboard may feel sharp for five minutes and then start causing tiny movement mistakes: unwanted A/D taps, canceled walk keys, missed crouch holds, or a defuse key that releases because your finger moved slightly.

I published the full source-backed version with FAQ schema, diagrams, references, and related browser tests here:

Rapid Trigger Keyboard Settings for CS2 and Valorant: Actuation, SOCD and Testing Guide

This DEV.to version keeps the practical tuning workflow.

Fast answer

Do not start by setting every key to 0.1 mm.

For CS2 and Valorant, a safer first profile is:

Key group	Starting point
WASD actuation	0.7 to 1.0 mm
Rapid Trigger reset	0.2 to 0.5 mm
Other keys	1.5 to 2.0 mm
CS2 SOCD / Snap Tap style features	Off before Valve official servers

That profile is still fast, but it gives you room to find out whether your fingers are steady enough before you lower the numbers.

For CS2, keep Rapid Trigger and adjustable actuation separate from automation features such as SOCD, Snap Tap, Snappy Tappy, Rappy Snappy, null binds, or any feature that turns multiple movement actions into one automated result.

Rapid Trigger is not SOCD

This is the most important distinction.

Rapid Trigger changes when one key turns on and off. SOCD or Snap Tap changes what happens when two opposing keys are active at the same time.

The terms get mixed together because many Hall Effect and optical keyboards expose all of these settings in the same software panel.

They are different problems:

Setting	What it changes	Common mistake
Actuation point	How far a key travels before it reports pressed	Setting every key too shallow
Rapid Trigger sensitivity	How much upward movement resets an active key	Making hold keys release accidentally
Continuous Rapid Trigger	Keeps dynamic reset behavior active deeper in the stroke	Enabling it before you can hold keys steadily
SOCD / Snap Tap	Resolves opposite directions such as A + D	Treating it like normal Rapid Trigger
Polling rate	How often the keyboard reports to the PC	Raising Hz without testing stability

For a player, the difference is simple:

Rapid Trigger can make one key release sooner.
SOCD / Snap Tap can decide which direction wins when A and D overlap.

That second category is where rules become sensitive.

The profile I would start with

There is no universal best number. Finger pressure, keycap height, switch wobble, keyboard angle, wrist position, and game habits all change the result.

The first goal is not the lowest number. The first goal is:

Faster release without accidental input.

Here is the practical table I would use.

Profile	WASD actuation	Rapid Trigger reset	Other keys	Use when
Baseline FPS	0.7 to 1.0 mm	0.3 to 0.5 mm	1.5 to 2.0 mm	You are new to Hall Effect, analog optical, or Rapid Trigger keyboards
CS2 conservative	0.6 to 0.8 mm	0.2 to 0.5 mm	E, Shift, Ctrl, Space at 1.2 to 2.0 mm	You want cleaner counter-strafing without accidental defuse, walk, or crouch releases
Valorant conservative	0.7 to 1.0 mm	0.2 to 0.4 mm	Abilities, walk, crouch, push-to-talk at 1.5 to 2.0 mm	You want sharper movement but reliable ability control
Aggressive trained FPS	0.3 to 0.6 mm	0.1 to 0.2 mm	Per-key tuning only	You already tested for accidental releases
Avoid as default	0.1 mm on every key	0.1 mm on every key	Everything ultra-light	It looks fast, but often creates accidental input

Set WASD first. Then decide whether W and S really need the same behavior as A and D.

Some players only enable Rapid Trigger on A and D because side-to-side strafing matters most. W, Shift, Ctrl, Space, E, push-to-talk, and ability keys often need to be held cleanly.

CS2 notes

CS2 is where the keyboard setting feels most obvious because movement accuracy and stopping behavior are tightly connected.

Wooting's CS2 guide recommends that new analog keyboard users start with:

0.7 mm WASD actuation
1.5 mm actuation for the rest of the keyboard
0.5 mm Rapid Trigger sensitivity
Continuous Rapid Trigger off
Tachyon Mode on for supported Wooting boards

That is a sensible baseline because it favors consistency before the lowest possible number.

The key I would protect in CS2 is E.

If your defuse/use key is set like a movement-tap key, a slight finger lift can interrupt a hold. The same logic applies to walk, crouch, jump, push-to-talk, and grenade binds.

A faster A/D release is useful. A canceled defuse is not.

Valorant notes

Valorant still benefits from clean press and release timing, but I would not treat it as a CS2 clone.

Movement, weapon accuracy recovery, ability use, and walk-key habits are different enough that a CS2 profile can feel too twitchy.

Start with the baseline FPS profile, then lower only A and D first.

If you get unwanted jiggle movement, stop walking while holding W, or accidentally cancel utility habits, raise the reset sensitivity slightly or disable Rapid Trigger on the key that must stay held.

The rule-safety part

The safest wording is:

Rapid Trigger is not the same feature as SOCD / Snap Tap.

Valve's August 19, 2024 CS2 input update warned against input automation that can include hardware-assisted counter-strafing on Valve official servers. It also told players to disable keyboard input-automation features such as Snap Tap before joining a match.

Wooting's April 2026 CS2 guide says Rapid Trigger, adjustable actuation, and Continuous Rapid Trigger are allowed, while Snappy Tappy and Rappy Snappy are prohibited on Valve servers.

For CS2, my default recommendation is simple:

keep adjustable actuation if your keyboard supports it
keep Rapid Trigger if it is tuned per key
turn off SOCD, Snap Tap, Snappy Tappy, Rappy Snappy, null binds, and similar automation features before Valve official matchmaking
check FACEIT, ESEA, LAN, school, or local tournament rules separately

For Valorant, Riot's public support wording is broader: unauthorized hardware or software that gives an unfair advantage can lead to permanent bans. Treat that as the floor. Avoid macros, avoid automation, and do not assume every keyboard feature is legal in every event.

Test before trusting the profile

A browser cannot measure physical switch travel depth. It cannot prove that a key is truly set to 0.4 mm or 0.1 mm.

It can still catch the problems that ruin a match:

missed keys
unexpected releases
ghosted combinations
rollover limits
unstable timing after firmware or profile changes

The workflow I recommend:

Create a separate FPS profile.
Keep your normal typing profile deeper and less sensitive.
Start with 0.7 to 1.0 mm WASD and 0.3 to 0.5 mm reset.
Disable SOCD-style automation for CS2 before launching or queuing.
Run a Keyboard Tester and press W, A, S, D, Shift, Ctrl, Space, E, R, number keys, and your game binds.
Run a Keyboard Ghosting Test with real game combinations such as W + A + Shift, A + D, W + Space, and Shift + Ctrl.
Run an N-Key Rollover Test after enabling any high-performance mode.
Compare timing with an Input Latency Checker before and after polling or Tachyon-style changes.
Play one repeatable drill in CS2 offline, deathmatch, Valorant range, or another movement routine.

Change one variable at a time. If you change actuation, Rapid Trigger sensitivity, SOCD, polling rate, and binds together, you will not know what caused the problem.

What a bad setting feels like

Rapid Trigger problems usually feel like "the keyboard is too sensitive," but the fix depends on which key is misbehaving.

Symptom	Likely cause	Fix
Character stops moving forward while holding W	Reset is too sensitive on W, or finger pressure is unstable	Raise W reset to 0.3 to 0.5 mm, increase W actuation, or enable Rapid Trigger only on A/D
Accidental side steps or jiggles	A/D actuation is too shallow for your resting finger weight	Move from 0.1 to 0.4 mm, or from 0.4 to 0.7 mm, then retest
Defuse, interact, walk, or crouch cancels	Hold keys are set like movement tap keys	Disable Rapid Trigger on those keys or use 1.5 to 2.0 mm actuation
CS2 kick or automation warning	SOCD, Snap Tap, null bind, or hardware-assisted counter-strafe behavior may be active	Disable input automation in keyboard software and game config
Typing becomes error-prone	Gaming profile is too shallow for normal typing	Use separate typing and gaming profiles
Combos fail only when several keys are held	Rollover or ghosting limitation, not Rapid Trigger itself	Test ghosting and NKRO, then check firmware/input mode

Brand names will differ

The category matters more than the brand name.

Wooting uses names such as Rapid Trigger, Continuous Rapid Trigger, Snappy Tappy, Rappy Snappy, and Tachyon Mode.

Razer uses names such as Rapid Trigger Mode and Snap Tap.

Other Hall Effect boards may say RT, dynamic reset, FlashTap, Speed Tap, last input priority, neutral SOCD, or key priority.

Do not tune by name alone. Ask what the feature actually does:

Does it change the press/release threshold of one key?
Does it decide which direction wins when A and D overlap?
Does it generate or collapse multiple actions into one result?

Those are different categories.

Official explainer

This Wooting video is a useful visual explanation of the basic Rapid Trigger idea:

Use it for the mechanical concept, then tune your own board with conservative per-key settings.

Sources I checked

Final checklist

Before ranked:

Use a separate FPS profile.
Keep typing and utility keys less sensitive.
Start at 0.7 to 1.0 mm WASD, not 0.1 mm everywhere.
Tune A and D before touching every bind.
Disable SOCD / Snap Tap style automation for CS2 official servers.
Test your real movement combos before trusting the profile.

I maintain KeyboardTester.click, a browser-based hardware testing site. The full Rapid Trigger guide includes the diagrams, FAQ, sources, and related tests in one place:

Rapid Trigger Keyboard Settings for CS2 and Valorant

Rapid Trigger Keyboard Settings for CS2 and Valorant: Start Fast, Not Fragile

keyboardTester.Click — Sun, 24 May 2026 06:35:13 +0000

The fastest Rapid Trigger profile is not always the best profile.

I published the full source-backed version with FAQ schema, diagrams, references, and related browser tests here:

Rapid Trigger Keyboard Settings for CS2 and Valorant: Actuation, SOCD and Testing Guide

This DEV.to version keeps the practical tuning workflow.

Fast answer

Do not start by setting every key to 0.1 mm.

For CS2 and Valorant, a safer first profile is:

Key group	Starting point
WASD actuation	0.7 to 1.0 mm
Rapid Trigger reset	0.2 to 0.5 mm
Other keys	1.5 to 2.0 mm
CS2 SOCD / Snap Tap style features	Off before Valve official servers

That profile is still fast, but it gives you room to find out whether your fingers are steady enough before you lower the numbers.

Rapid Trigger is not SOCD

This is the most important distinction.

Rapid Trigger changes when one key turns on and off. SOCD or Snap Tap changes what happens when two opposing keys are active at the same time.

The terms get mixed together because many Hall Effect and optical keyboards expose all of these settings in the same software panel.

They are different problems:

Setting	What it changes	Common mistake
Actuation point	How far a key travels before it reports pressed	Setting every key too shallow
Rapid Trigger sensitivity	How much upward movement resets an active key	Making hold keys release accidentally
Continuous Rapid Trigger	Keeps dynamic reset behavior active deeper in the stroke	Enabling it before you can hold keys steadily
SOCD / Snap Tap	Resolves opposite directions such as A + D	Treating it like normal Rapid Trigger
Polling rate	How often the keyboard reports to the PC	Raising Hz without testing stability

For a player, the difference is simple:

Rapid Trigger can make one key release sooner.
SOCD / Snap Tap can decide which direction wins when A and D overlap.

That second category is where rules become sensitive.

The profile I would start with

There is no universal best number. Finger pressure, keycap height, switch wobble, keyboard angle, wrist position, and game habits all change the result.

The first goal is not the lowest number. The first goal is:

Faster release without accidental input.

Here is the practical table I would use.

Profile	WASD actuation	Rapid Trigger reset	Other keys	Use when
Baseline FPS	0.7 to 1.0 mm	0.3 to 0.5 mm	1.5 to 2.0 mm	You are new to Hall Effect, analog optical, or Rapid Trigger keyboards
CS2 conservative	0.6 to 0.8 mm	0.2 to 0.5 mm	E, Shift, Ctrl, Space at 1.2 to 2.0 mm	You want cleaner counter-strafing without accidental defuse, walk, or crouch releases
Valorant conservative	0.7 to 1.0 mm	0.2 to 0.4 mm	Abilities, walk, crouch, push-to-talk at 1.5 to 2.0 mm	You want sharper movement but reliable ability control
Aggressive trained FPS	0.3 to 0.6 mm	0.1 to 0.2 mm	Per-key tuning only	You already tested for accidental releases
Avoid as default	0.1 mm on every key	0.1 mm on every key	Everything ultra-light	It looks fast, but often creates accidental input

Set WASD first. Then decide whether W and S really need the same behavior as A and D.

Some players only enable Rapid Trigger on A and D because side-to-side strafing matters most. W, Shift, Ctrl, Space, E, push-to-talk, and ability keys often need to be held cleanly.

CS2 notes

CS2 is where the keyboard setting feels most obvious because movement accuracy and stopping behavior are tightly connected.

Wooting's CS2 guide recommends that new analog keyboard users start with:

0.7 mm WASD actuation
1.5 mm actuation for the rest of the keyboard
0.5 mm Rapid Trigger sensitivity
Continuous Rapid Trigger off
Tachyon Mode on for supported Wooting boards

That is a sensible baseline because it favors consistency before the lowest possible number.

The key I would protect in CS2 is E.

If your defuse/use key is set like a movement-tap key, a slight finger lift can interrupt a hold. The same logic applies to walk, crouch, jump, push-to-talk, and grenade binds.

A faster A/D release is useful. A canceled defuse is not.

Valorant notes

Valorant still benefits from clean press and release timing, but I would not treat it as a CS2 clone.

Movement, weapon accuracy recovery, ability use, and walk-key habits are different enough that a CS2 profile can feel too twitchy.

Start with the baseline FPS profile, then lower only A and D first.

If you get unwanted jiggle movement, stop walking while holding W, or accidentally cancel utility habits, raise the reset sensitivity slightly or disable Rapid Trigger on the key that must stay held.

The rule-safety part

The safest wording is:

Rapid Trigger is not the same feature as SOCD / Snap Tap.

Wooting's April 2026 CS2 guide says Rapid Trigger, adjustable actuation, and Continuous Rapid Trigger are allowed, while Snappy Tappy and Rappy Snappy are prohibited on Valve servers.

For CS2, my default recommendation is simple:

keep adjustable actuation if your keyboard supports it
keep Rapid Trigger if it is tuned per key
turn off SOCD, Snap Tap, Snappy Tappy, Rappy Snappy, null binds, and similar automation features before Valve official matchmaking
check FACEIT, ESEA, LAN, school, or local tournament rules separately

Test before trusting the profile

A browser cannot measure physical switch travel depth. It cannot prove that a key is truly set to 0.4 mm or 0.1 mm.

It can still catch the problems that ruin a match:

missed keys
unexpected releases
ghosted combinations
rollover limits
unstable timing after firmware or profile changes

The workflow I recommend:

Create a separate FPS profile.
Keep your normal typing profile deeper and less sensitive.
Start with 0.7 to 1.0 mm WASD and 0.3 to 0.5 mm reset.
Disable SOCD-style automation for CS2 before launching or queuing.
Run a Keyboard Tester and press W, A, S, D, Shift, Ctrl, Space, E, R, number keys, and your game binds.
Run a Keyboard Ghosting Test with real game combinations such as W + A + Shift, A + D, W + Space, and Shift + Ctrl.
Run an N-Key Rollover Test after enabling any high-performance mode.
Compare timing with an Input Latency Checker before and after polling or Tachyon-style changes.
Play one repeatable drill in CS2 offline, deathmatch, Valorant range, or another movement routine.

Change one variable at a time. If you change actuation, Rapid Trigger sensitivity, SOCD, polling rate, and binds together, you will not know what caused the problem.

What a bad setting feels like

Rapid Trigger problems usually feel like "the keyboard is too sensitive," but the fix depends on which key is misbehaving.

Symptom	Likely cause	Fix
Character stops moving forward while holding W	Reset is too sensitive on W, or finger pressure is unstable	Raise W reset to 0.3 to 0.5 mm, increase W actuation, or enable Rapid Trigger only on A/D
Accidental side steps or jiggles	A/D actuation is too shallow for your resting finger weight	Move from 0.1 to 0.4 mm, or from 0.4 to 0.7 mm, then retest
Defuse, interact, walk, or crouch cancels	Hold keys are set like movement tap keys	Disable Rapid Trigger on those keys or use 1.5 to 2.0 mm actuation
CS2 kick or automation warning	SOCD, Snap Tap, null bind, or hardware-assisted counter-strafe behavior may be active	Disable input automation in keyboard software and game config
Typing becomes error-prone	Gaming profile is too shallow for normal typing	Use separate typing and gaming profiles
Combos fail only when several keys are held	Rollover or ghosting limitation, not Rapid Trigger itself	Test ghosting and NKRO, then check firmware/input mode

Brand names will differ

The category matters more than the brand name.

Wooting uses names such as Rapid Trigger, Continuous Rapid Trigger, Snappy Tappy, Rappy Snappy, and Tachyon Mode.

Razer uses names such as Rapid Trigger Mode and Snap Tap.

Other Hall Effect boards may say RT, dynamic reset, FlashTap, Speed Tap, last input priority, neutral SOCD, or key priority.

Do not tune by name alone. Ask what the feature actually does:

Does it change the press/release threshold of one key?
Does it decide which direction wins when A and D overlap?
Does it generate or collapse multiple actions into one result?

Those are different categories.

Official explainer

This Wooting video is a useful visual explanation of the basic Rapid Trigger idea:

Use it for the mechanical concept, then tune your own board with conservative per-key settings.

Sources I checked

Final checklist

Before ranked:

Use a separate FPS profile.
Keep typing and utility keys less sensitive.
Start at 0.7 to 1.0 mm WASD, not 0.1 mm everywhere.
Tune A and D before touching every bind.
Disable SOCD / Snap Tap style automation for CS2 official servers.
Test your real movement combos before trusting the profile.

I maintain KeyboardTester.click, a browser-based hardware testing site. The full Rapid Trigger guide includes the diagrams, FAQ, sources, and related tests in one place:

Rapid Trigger Keyboard Settings for CS2 and Valorant

Ghost Touch Test Online: Find Phantom Taps, Dead Zones, and Touchscreen Drift

keyboardTester.Click — Wed, 13 May 2026 18:12:48 +0000

Ghost touch feels random, but the fault usually follows a pattern.

A phone may open apps by itself only while charging. A tablet may stop drawing through one vertical strip. A Windows touch laptop may move the cursor because the touchscreen digitizer is firing invisible taps.

The useful question is not only:

Is my screen broken?

The useful question is:

Can I capture the pattern before I reset software, replace glass, or buy a used device?

I published the full version with FAQ schema, source links, and the live browser tool workflow here:

Ghost Touch Test Online: Find Phantom Taps, Dead Zones and Touchscreen Drift

This DEV.to version keeps the practical diagnostic flow.

Fast answer

Open the free Touch Screen Test, clear the canvas, keep your hands away from the display, and run the 10-second ghost touch check.

If marks appear while nobody touches the screen, your device is registering phantom input.

Then draw slow diagonal lines across the full screen. A repeated break in the same physical area usually points to a dead zone or digitizer fault.

Why a browser test is useful

A browser test will not repair a bad digitizer.

It can still give you useful evidence because it is:

quick to open
account-free
install-free
easy to repeat after each fix
visual enough to photograph before repair or resale

That matters because "ghost touch" can come from more than one place:

moisture or cleaner residue
a lifted or dirty screen protector
charger or cable interference
a failing digitizer
cracked glass
a swollen battery
Windows touch driver problems
firmware or BIOS issues on touch laptops

The test result becomes useful when you run it twice: once with your normal accessories, then once with the device cleaned, unplugged, and stripped of cases or protectors.

How to run the online ghost touch test

Open Touch Screen Test on the device you want to check.
Clean and dry the glass.
Remove gloves, heavy cases, magnetic covers, and the screen protector if you suspect it.
Tap Clear Canvas.
Run Ghost Touch Test (10s).
Keep all fingers, sleeves, cables, and styluses away from the display until the timer ends.
If the page reports ghost touches or shows marks, repeat the same test while unplugged from the charger.
Draw slow diagonal lines from corner to corner.
Place two, three, four, and five fingers on the canvas to test multi-touch behavior.

A slow diagonal drag exposes dead zones better than random tapping because you can see exactly where the trace breaks.

How to read the result

What you see	Likely meaning	Next move
Touch marks appear during the no-touch timer	The digitizer, protector, charger, moisture, or driver may be creating phantom input	Retest unplugged, clean the glass, remove accessories, then compare safe mode or firmware screens
A diagonal line breaks at the same strip every time	That area may be a dead zone in the touch layer	Photograph the pattern and prepare for repair if cleaning and accessory removal do not change it
Touch lands beside your finger	The panel may have calibration, scaling, driver, or digitizer drift	Reset touch calibration on Windows, update drivers, or reboot phones and tablets
Ghost touch happens only while charging	The charger, cable, socket, grounding, or battery condition may be involved	Switch to a trusted charger and cable, avoid cheap adapters, and stop using the device if swelling or heat appears
Multi-touch stops at two or three fingers	The device may support fewer points, or the driver may expose fewer contacts	Compare against the device specification and retest after updates

Quick fixes before repair

Start with reversible fixes.

Official support pages from Apple, Google Android, ASUS, and Microsoft all put simple checks before service: restart, clean the screen, remove cases and protectors, disconnect accessories, check updates, and only then escalate.

Clean and dry the display

Moisture, skin oil, dust, and cleaner residue can trigger bad input. Power the device off, wipe with a soft cloth, let the surface dry, then retest.

Remove the screen protector

Thick glass, bubbles, edge lift, and dirt under the protector can create missed touches or false touches. Test once without it.

Change charger and cable

If ghost taps appear only while charging, unplug first. Then test with an original or certified charger, another cable, and another wall outlet.

Restart before resetting

A restart clears temporary driver and app state. A factory reset removes data, so keep it near the end of the workflow, not the beginning.

Windows touch laptop checks

On Windows laptops and Surface devices, ghost touch can look like mouse movement, random clicks, or a cursor jumping to one side of the screen.

Do not assume the touchpad is the problem until you test the touchscreen layer.

1. Test outside Windows when possible

Microsoft's Surface guidance recommends testing touch in UEFI because UEFI runs outside Windows.

If touch fails or ghost taps appear there, the issue is much more likely to be hardware. If touch works normally there, Windows, drivers, firmware, or apps become stronger suspects.

2. Reinstall the HID touch driver

Open Device Manager, expand Human Interface Devices, and look for HID-compliant touch screen or OEM touch entries.

On supported systems, uninstall the touchscreen device, then use Action > Scan for hardware changes or restart so Windows reloads it.

Do not remove unknown drivers blindly on work machines.

3. Update Windows, OEM firmware, and BIOS

Touch issues can ship with firmware fixes.

ASUS lists BIOS, Windows packages, and driver updates as part of its touchscreen troubleshooting flow. Dell has also documented a ghost-touch style issue on specific Latitude and Precision models where BIOS updates fixed erratic input symptoms.

The exact device matters, but the lesson is useful: check OEM updates before replacing parts.

4. Disable touch only when you need a workaround

If ghost taps make the laptop unusable, disabling the touchscreen can restore normal mouse and keyboard control.

Treat that as a workaround, not a root fix. Document where the ghost taps happen, save photos of the touch test, and keep repair or warranty evidence ready.

Phone and tablet checks

Phones and tablets add two extra variables: accessories and charging.

A device can pass while unplugged, then fail with a bad cable. It can also fail only with a screen protector that lifts at the edge.

Android

Google's Android support flow starts by checking damage, removing cases and screen protectors, removing gloves, peeling off stickers over sensors, and cleaning the screen.

It also recommends a slow drag from the top-left corner to the bottom-right corner to see whether the drag releases in the same screen area. That is exactly the pattern you should record in an online dead-zone test.

iPhone and iPad

Apple tells users to restart, make sure the screen is clean and free from debris or water, disconnect Lightning or USB-C accessories, try a different socket, cable, or charger, and remove cases or screen protectors when the display feels too sensitive or responds intermittently.

If the screen still fails, Apple points users toward service.

Used-device buying check

Before buying a used phone, tablet, or touch laptop, open the touch test in the browser while you inspect it.

Run the ghost test, draw a full-screen grid, test multi-touch, then plug in the charger and repeat.

A seller who refuses a two-minute screen test gives you useful information.

When ghost touch means repair

Repair becomes more likely when the fault repeats in the same physical area after cleaning, accessory removal, restart, charger swap, and software checks.

Treat these as stronger repair signals:

the screen taps by itself during a no-touch test in the same area twice
a diagonal drag breaks through the same strip from different directions
ghost taps appear in UEFI, recovery, safe mode, or another clean environment
the problem started after a drop, water exposure, battery swelling, or screen replacement
the device becomes unusable unless you disable the touch driver

For phones and tablets, the repair shop should replace the digitizer layer or full display assembly depending on the model, not only polish or re-seat glass.

For Windows laptops, ask whether the panel, cable, hinge routing, firmware, and touch controller were checked.

After repair, run the same online ghost touch, dead-zone, and multi-touch checks before leaving the shop.

Helpful video walkthrough

This official ASUS Support video is a useful visual companion for Windows touchscreen troubleshooting. Use it with the online test above so you can compare each setting change against a visible touch result.

Sources

Related tools

Final check

Run the touch screen test after every fix.

If the same ghost tap or dead strip appears after cleaning, accessory removal, charger swap, restart, and driver or update checks, save the result and move to repair or warranty support with evidence.

Best Gaming Mouse 2026: Practical Picks by Grip, Price, and Game Type

keyboardTester.Click — Tue, 12 May 2026 17:39:54 +0000

The best gaming mouse in 2026 is not the one with the biggest DPI number.

It is the one that fits your hand, works with your grip, keeps the game smooth at your chosen polling rate, and does not waste money on features you will never use.

I published the full source-backed version with FAQ schema, product images, source links, and browser testing tools here:

Best Gaming Mouse 2026: Practical Picks for FPS, Wireless, Budget, and MMO Players

This DEV.to version keeps the buying logic, current price snapshot, and the checks I would run after buying.

Fast answer

If I had to start with one competitive FPS mouse in 2026, I would compare the Razer Viper V3 Pro first.

It has strong pro-player adoption, a light symmetrical shell, and a current official price I found at $129.99 sale / $159.99 list when checked on May 12, 2026.

That does not make it the right mouse for everyone.

Here is the short list:

Pick	Official US price checked May 12, 2026	Best for
Razer Viper V3 Pro	$129.99 sale / $159.99 list	Competitive FPS, claw/fingertip
Logitech G PRO X2 SUPERSTRIKE	$179.99	Click tuning, competitive players
Razer DeathAdder V4 Pro	$169.99	Palm grip, relaxed claw, larger hands
Logitech G PRO X SUPERLIGHT 2 DEX	$159.99	Safe Logitech shape, right-handed FPS
ASUS ROG Harpe II Ace	$169.99	Lightweight flagship value
Razer Basilisk V3 Pro 35K	$159.99	Mixed gaming and productivity
Logitech G305 / G304 Lightspeed	$59.99	Budget wireless
Razer Naga V2 Pro	$179.99	MMO, MOBA, macro-heavy games

Prices move quickly, so treat these as a dated snapshot rather than a permanent promise.

Why this is not just a "top 10" list

Mouse advice usually gets stuck between two extremes:

lab lists that treat every category as a benchmark table
Reddit threads where everyone says "shape is king"

Both are useful.

Neither is enough by itself.

The way I would buy a mouse is more practical:

Pick by hand size and grip first.
Decide whether the game actually needs FPS weight, MMO buttons, or mixed-use comfort.
Check if the wireless mode and polling rate make sense for your PC.
Look at current price, not only MSRP.
Test the physical mouse before the return window closes.

1. Razer Viper V3 Pro: safest FPS starting point

The Viper V3 Pro is the safest recommendation if your main question is:

What are serious FPS players actually using?

It is light, symmetrical, simple, and focused. That is exactly what many Valorant, CS2, Apex, Overwatch, Fortnite, and Rainbow Six players want.

Buy it if you use claw or fingertip grip and want a proven competitive wireless shell.

Skip it if you need a wide ergonomic palm-rest shape, many side buttons, or a cheaper entry point.

2. Logitech G PRO X2 SUPERSTRIKE: most interesting click tech

The Logitech G PRO X2 SUPERSTRIKE is the mouse that changes the conversation more than most 2026 launches.

The interesting part is not only the sensor or polling rate. It is the click system: adjustable click actuation and a faster follow-up click behavior that feels closer to the kind of tuning keyboard players already know from rapid-trigger boards.

Buy it if you already like Logitech's esports shape family and want advanced click tuning.

Skip it if you simply want the lightest possible mouse for the money.

3. Razer DeathAdder V4 Pro: ergonomic flagship

If the Viper shape feels too flat or narrow, the DeathAdder V4 Pro is the Razer mouse I would compare next.

The shape is the point. It gives more hand support than a low symmetrical shell while still staying in the flagship-performance tier.

Buy it if you have medium-to-large hands, palm grip, or relaxed claw grip.

Skip it if you use pure fingertip grip or prefer smaller shells.

4. Logitech G PRO X SUPERLIGHT 2 DEX: safe Logitech shape

The Superlight family is still popular because it is boring in a useful way.

It is easy to adapt to, easy to recommend, and easy to resell if the shape does not work for you.

The DEX version makes sense if you want a right-handed ergonomic tilt while staying in the Superlight performance family.

5. ASUS ROG Harpe II Ace: lightweight flagship value

The ROG Harpe II Ace is the mouse I would compare if you want a modern lightweight FPS shell but do not want to buy only from Razer or Logitech.

ASUS lists a 48 g shell, 8K wireless polling support, a 42K AimPoint Pro sensor, and up to 101 hours of battery life at 1,000 Hz with lighting off.

The official ASUS estore price I found was $169.99.

Buy it if you want a clean competitive shell for claw or fingertip grip.

Skip it if you need a fuller palm-grip shape or dislike ASUS peripheral software.

6. Razer Basilisk V3 Pro 35K: mixed gaming and work

The Basilisk V3 Pro 35K is not trying to be the lightest esports shell.

That is why it is useful.

It has a comfortable right-handed shape, more programmable buttons, a strong sensor, RGB, and a useful wheel.

Buy it if you play RPGs, strategy, survival games, casual shooters, and also use the same mouse for desktop work.

Skip it if your only goal is a low-weight FPS setup.

7. Logitech G305 / G304 Lightspeed: budget wireless

The G305 is not new.

That is part of why it is still useful.

It is affordable, proven, easy to replace, and good enough for many players who are moving from a basic office mouse.

The tradeoff is weight. Because it uses a replaceable battery, it will feel heavier than modern ultralight FPS mice.

Buy it if you want cheap 2.4 GHz wireless.

Skip it if you already know you need an under-65 g shell.

8. Razer Naga V2 Pro: MMO and macro-heavy games

An MMO mouse is a different category.

Weight matters less than whether your thumb can hit the right command reliably.

The Naga V2 Pro makes sense because it has swappable side plates, so it can act like a 2-button, 6-button, or 12-button mouse depending on the game.

Buy it for World of Warcraft, Final Fantasy XIV, Guild Wars 2, ARPGs, MOBAs, or productivity macros.

Skip it for low-sensitivity FPS aim.

Grip style matters more than DPI

Maximum DPI is mostly marketing once the sensor is already good.

Grip and shape decide more.

Grip	What to compare first
Palm grip	DeathAdder V4 Pro, Basilisk, larger ergonomic shells
Claw grip	Viper V3 Pro, Superlight 2 DEX, SUPERSTRIKE, Harpe II Ace
Fingertip grip	Lower weight, lower shell height, easy lift-off
MMO grip	Thumb button layout, profile software, button separation

If your hand never relaxes on the shell, no sensor spec will fix that.

Polling rate: do not force 8K

Polling rate is how often the mouse reports position to the computer.

A 1000 Hz mouse reports every 1 ms. An 8000 Hz mouse can report every 0.125 ms on paper.

That sounds huge, but the full chain still matters:

mouse firmware
USB or wireless transport
Windows input handling
game engine
frame rate
monitor refresh
display response

My practical setup:

Start at 1000 Hz.
Test 2000 Hz or 4000 Hz.
Keep 8000 Hz only if the game stays smooth and battery life is acceptable.

If your 1% lows get worse, the higher polling number is not helping you.

Test the mouse after buying

Before the return window closes, I would run a simple hardware check:

Open a mouse tester and verify left click, right click, middle click, scroll, and pointer movement.
Use a polling rate test in wired and 2.4 GHz wireless mode.
Use a DPI tester if sensitivity feels different from your old mouse.
Run a ghost click detector if a single click sometimes fires twice.
Check input latency if the mouse feels delayed even when polling looks correct.

That gives you evidence from your own setup instead of trusting the box.

Video version

Sources and full version

The canonical article includes the complete source list, FAQ schema, related tools, and the full research notes:

Read the full best gaming mouse 2026 guide on KeyboardTester.click

Main sources used for the price and product-image refresh:

Final recommendation

Start with shape, not specs.

If you want one competitive FPS starting point, compare the Razer Viper V3 Pro first.

If your hand wants more support, compare the DeathAdder V4 Pro.

If price matters, the G305 is still a reasonable budget wireless fallback.

A comfortable, consistent mouse beats an expensive mouse that fights your hand.

League of Legends Actions Per Minute Tracker: Use an APM Test Without Chasing Spam

keyboardTester.Click — Mon, 11 May 2026 07:00:42 +0000

I do not treat APM as a trophy number.

For League of Legends, that is the fastest way to make the metric useless.

If you repeat right-clicks in the same place, tap ability keys out of panic, or mash camera keys without actually reading the map, your actions-per-minute number can climb while your mechanics get worse.

The useful question is not:

How high is my APM?

The useful question is:

How many of my actions are clean enough that I would still want them in a lane trade, objective fight, or last-hit window?

I published the full version with images, source links, FAQ schema, and the live browser APM tool workflow here:

League of Legends Actions Per Minute Tracker: What an APM Test Really Tells You

This DEV.to version keeps the practical diagnostic flow.

Fast answer

A League of Legends actions per minute tracker is useful as a practice drill, not as a magic ranked predictor.

Use an APM test to measure clean keyboard and mouse rhythm, watch accuracy, and separate useful inputs from spam.

If the number goes up while accuracy collapses, your mechanics did not improve.

Why the keyword matters

The search intent is more specific than "APM test."

People are searching for things like:

League of Legends actions per minute tracker
LoL APM tracker
actions per minute test
APM tester
APM calculator
keyboard APM test
effective APM

That tells me users are not only looking for a counter. They are also trying to understand whether a tool can track real League match actions.

That distinction matters.

What a browser APM test can measure

A browser APM test can measure the inputs you perform inside that test:

keyboard presses
mouse clicks
target hits
wrong keys
misses
accuracy
peak pace
average pace

That is useful for warm-up and repeatable practice.

The better tests do not only show raw volume. They also show whether the actions were useful.

For example:

Metric	What it tells you
Raw APM	Total input volume. Easy to inflate with spam.
Effective APM	Cleaner input rhythm. More useful for practice.
Keyboard APM	Ability keys, item slots, summoner spells, camera rhythm.
Mouse APM	Click timing, target control, attack-move rhythm.

What it cannot measure inside a real LoL match

A browser APM tester cannot see what happened inside your live League match.

It can only measure what you do inside the browser test.

That means it is not official Riot match telemetry, and it should not ask for your Riot account credentials.

Riot's public developer portal describes game data such as active games, match history, and ranked statistics. That is different from a public keyboard-and-mouse event feed.

So if a random page says it can show your exact match APM, I would be skeptical unless it explains where the data comes from.

How I read an APM score

I use APM as a baseline, not a verdict.

Result	What I assume first	What I do next
Low APM, high accuracy	Controlled but slow	Train one key or click pattern
Medium APM, stable accuracy	Useful warm-up zone	Add game-specific sequences
High APM, low accuracy	Probably spam	Slow down until misses drop
Wildly different scores	Inconsistent method	Repeat same mode and duration

For League, I would rather see a lower score with clean inputs than a higher score full of repeated noise.

My 12-minute LoL APM practice workflow

This is the workflow I would use before a normal session:

Two minutes: keyboard-only warm-up

Use the keys you actually press in League: Q, W, E, R, D, F, item slots, camera keys, or your custom set.
Two minutes: mouse target drill

Use a grid mode and aim for clean hits, not frantic clicking.
Three minutes: mixed rhythm

Alternate keyboard and mouse drills so your handoff feels natural.
Three minutes: Practice Tool translation

Open League Practice Tool and run last hits, trade movement, or ability combos.
Two minutes: review one mistake

Was it a wrong key, late click, panic spam, camera miss, or pointer overcorrection?

The browser score is only useful if it transfers into real practice.

Why League is different from a pure RTS APM test

League rewards movement, spacing, cooldown tracking, target selection, map awareness, and decision timing.

More inputs can help only when they serve those jobs.

If you click ten times during a trade but three clicks cancel a good position, the APM number is lying to you.

Riot's newer input work makes this even more relevant. Their 2026 WASD Ranked Release note covers champion-specific keybinds, expanded input options, and accessibility-focused controls. Some players will legitimately use more keyboard actions than before.

That still does not make raw APM the goal.

Clean control is the goal.

Hardware checks that make APM more honest

If your keyboard misses combinations, your mouse double-clicks, or your setup has heavy input delay, your APM score becomes noisy.

Before blaming mechanics, I would check:

Sources I used

Riot Support: Hotkeys and keybindings FAQ
Riot Support: Keyboard WASD input FAQ
League of Legends /dev: WASD's Ranked Release
Riot Developer Portal
MDN KeyboardEvent.key
MDN Pointer Events

Full source links are in the canonical article:

Read the complete LoL APM tracker guide on KeyboardTester.click

Final check

Run one clean baseline in the free APM Test, then repeat after a real Practice Tool warm-up.

If the League session feels cleaner but the browser number is lower, trust the cleaner inputs.

Microphone Picking Up Desktop Audio on Windows 11? Trace the Signal Path First

keyboardTester.Click — Sun, 10 May 2026 10:53:04 +0000

If your friends can hear your YouTube video, game audio, or system sound through your microphone, the first instinct is usually to reinstall the audio driver.

That is not where I would start.

On Windows 11, "my mic is picking up desktop audio" can mean several different things:

the app is using a loopback source instead of the real microphone
Stereo Mix or a virtual cable is selected somewhere
"Listen to this device" is creating a confusing monitor path
Realtek or headset software is routing audio in a driver layer
a 3.5 mm headset, splitter, or front-panel jack is leaking signal electrically
speakers are simply loud enough that the microphone hears them in the room

Those causes produce almost the same symptom. The fix depends on which path is real.

I published the full version with images and the browser mic test workflow here: Microphone Picking Up Desktop Audio on Windows 11? Full Fix Guide

This DEV.to version keeps the practical diagnostic flow.

Fast answer

Before changing drivers, prove whether the microphone is actually hearing the desktop audio or whether Windows is routing playback audio into an input channel.

The fastest test:

Open a microphone meter or recording tool.
Play steady audio from a browser, game, or music app.
Physically mute the headset mic, or unplug the mic if possible.
Watch the input meter.

If the meter still moves while the physical microphone is muted or unplugged, the signal is probably not acoustic pickup. It is likely loopback, app selection, virtual audio routing, driver routing, or analog crosstalk.

If the meter stops, the microphone was probably hearing speakers, open-back headphones, or room echo.

That one test saves a lot of time.

Think of it as a signal path

The desktop audio has to travel from somewhere to somewhere.

A clean voice-call setup should look roughly like this:

Microphone capsule -> Windows input device -> app microphone input
Game/browser audio -> Windows output device -> headphones/speakers

A broken setup often looks like one of these:

Game/browser audio -> Stereo Mix -> app microphone input

Game/browser audio -> OBS monitor device -> captured again as mic

Headphone output wire -> analog bleed -> microphone wire

Speakers -> room air -> microphone capsule

All four can sound like "my mic is picking up my desktop."

They are not the same problem.

Step 1: Select the real microphone in Windows

Open:

Settings -> System -> Sound -> Input

Select the actual microphone or headset input.

Be suspicious of input names like:

Stereo Mix
What U Hear
Monitor
Cable Output
VoiceMeeter Output
OBS Virtual
anything that sounds like a playback or monitor device

Those names are not always bad. They are useful when you intentionally want to record system audio. But they are usually wrong for a normal Discord, Teams, Zoom, or game voice chat microphone.

Step 2: Disable Stereo Mix if you do not need it

Open the legacy sound panel:

Settings -> System -> Sound -> More sound settings -> Recording

If you see Stereo Mix enabled and you are not intentionally recording PC playback, disable it.

Stereo Mix is a loopback recording source. On some Realtek systems it captures whatever the PC is playing. That is helpful for some recording workflows, but if Discord or another app selects it as the microphone, everyone hears your desktop audio.

After disabling it, test again.

Do not change five things at once. Change one thing, record ten seconds, then compare.

Step 3: Turn off "Listen to this device"

In the Recording tab:

Open your microphone properties.
Go to the Listen tab.
Make sure "Listen to this device" is off.

This option plays microphone input back through an output device. It is meant for monitoring, but it can create a confusing path while debugging because input and output start feeding into each other.

It is not the only cause of desktop audio bleed, but it is quick to rule out.

Step 4: Keep microphone boost under control

High microphone boost can expose problems that are not obvious at normal gain.

If you push boost too hard, you can amplify:

analog jack noise
electrical crosstalk
cheap splitter bleed
keyboard noise
fan noise
room echo
headphone leakage

Start with the microphone level around 80 to 100 and use modest boost. If the problem appears only when boost is high, the root cause may be weak analog hardware or acoustic leakage rather than a Windows routing bug.

Step 5: Check the physical audio path

If Windows settings look correct and the leak still happens, inspect the hardware.

This is especially important with 3.5 mm analog headsets.

Try the rear motherboard jack

On desktop PCs, front-panel audio is sometimes noisier than the rear motherboard audio ports.

Move the headset splitter from the front panel to the rear green and pink jacks.

If the leak improves, the issue may be:

front-panel case wiring
a weak case audio jack
poor shielding
a bad splitter
the motherboard analog path

Check the splitter

Many headsets use one TRRS plug. Many desktops expect separate headphone and mic plugs.

That means people use a Y-splitter. A bad splitter can bridge channels enough that headphone audio leaks into the mic input.

Before replacing the whole headset, test another splitter.

Compare analog with USB

A cheap USB audio adapter is a useful diagnostic tool.

If the same headset stops leaking through a USB adapter, the microphone capsule may be fine. The analog jack path is the suspect.

If the same leak happens across USB, another headset, and another PC, then the headset itself becomes more suspicious.

Step 6: Check Discord separately

Discord can use its own input device choice.

Go to:

User Settings -> Voice & Video

Check:

Input Device is the exact microphone, not Default
Output Device is the intended headphones or speakers
automatic input sensitivity is not opening the gate from quiet desktop bleed
noise suppression and echo cancellation are on for normal calls
push-to-talk stops the symptom

Push-to-talk is a good proof test. If desktop audio only leaks when voice activation is open, your mic gate or suppression settings may be part of the issue. If desktop audio is present even when you are muted, the problem is deeper than Discord sensitivity.

Step 7: Check OBS routing

OBS can duplicate audio very easily because it has sources, tracks, monitoring, and global audio devices.

Check:

the mic source is the physical microphone
desktop audio is not added twice
the mic source is not capturing a monitor device
Advanced Audio Properties does not monitor into a device that is then captured
virtual audio cables are not selected as a microphone by accident

A common mistake is recording desktop audio as one source, then monitoring it into another path that gets captured again.

In that case, Windows may be fine. OBS is the loop.

Step 8: Check Teams and Zoom device settings

Teams and Zoom also keep their own device settings.

For Teams, choose the explicit microphone and speaker instead of relying on Default if devices keep changing.

For Zoom, use the audio test panel and check whether automatic microphone volume is changing the level. If you enable more raw audio modes, such as musician or original sound modes, remember that they can preserve more background sound and room echo.

That does not make those modes bad. It just means they are not the first thing to use while debugging desktop audio bleed.

Symptom table

Symptom	Likely cause	Best next test
Mic meter moves while physical mic is muted	Loopback, virtual device, Stereo Mix, or analog bleed	Disable loopback sources, test rear jack, test USB audio
Only Discord leaks game audio	Discord input/sensitivity/device choice	Set exact input device and test push-to-talk
Only OBS duplicates desktop audio	OBS monitoring or capture setup	Inspect sources, monitoring, and tracks
People hear echo only when speakers are on	Acoustic pickup	Use headphones, lower speaker volume, enable echo cancellation
Leak improves on rear jack	Front-panel or case audio path	Replace splitter or use rear/USB audio
Leak disappears with USB audio	Analog jack path	Use USB adapter/interface or repair analog path

The 10-minute isolation workflow

Here is the workflow I recommend:

Record ten seconds while desktop audio is playing.
Mute or unplug the physical mic and record again.
Disable Stereo Mix and virtual cable inputs.
Check "Listen to this device."
Move from front jack to rear jack.
Try USB audio or another microphone.
Test Discord, OBS, Teams, and Zoom one at a time.
Change only one thing between tests.

The last point matters most.

If you disable Stereo Mix, change Discord input, move the headset cable, reinstall Realtek, and reboot all at once, you may fix the issue but you will not know what actually fixed it.

Noise suppression is not a root-cause fix

Noise suppression, echo cancellation, and automatic gain control are useful. Keep them on for normal calls if they help.

But they are cleanup layers.

They do not fix:

Stereo Mix selected as input
OBS monitoring routed into a captured source
analog crosstalk in a splitter
a front-panel jack leaking signal
a virtual cable selected as microphone

Fix routing first. Then use suppression to polish the result.

Final diagnostic rule

If desktop audio appears while the physical microphone is muted or unplugged, do not blame the microphone capsule first.

Trace the signal path.

Start with Windows input selection, then loopback devices, then app-specific device settings, then the analog hardware path.

Once the input meter stays quiet while desktop audio plays and the physical mic is muted, the leak is gone. Then test your real app, because Discord, OBS, Teams, and Zoom can still have their own selected input device.

Why I Built an Online Ruler That Needs Calibration

keyboardTester.Click — Mon, 04 May 2026 15:53:55 +0000

Most "online ruler" pages look simple: draw a rectangle, add centimeter ticks, add inch ticks, done.

That works only if every screen maps CSS pixels to real-world size in the same way. They do not.

A 13-inch laptop, a 27-inch external monitor, a phone, a tablet, and a 4K display can all render the same CSS width with different physical sizes. Browser zoom, operating-system scaling, Retina-style display modes, and external monitors all make the problem worse.

So I built a small browser-based ruler where the main feature is not the drawing. The main feature is calibration.

You can try the finished version here: Free Online Ruler - Actual Size cm and Inch Ruler

That is the only link in this post. The rest is the technical reasoning behind the tool.

The core problem: CSS pixels are not physical pixels

When a page says:

width: 100px;

the browser does not promise that the result will be the same number of millimeters on every screen.

It promises a CSS pixel size within the browser's rendering model. The physical size depends on:

the monitor's actual pixel density
operating-system display scaling
browser zoom
device pixel ratio
whether the display is internal or external
whether the browser is running in a normal window, remote desktop, or virtual machine

That means a ruler hardcoded as "96 pixels per inch" can look correct on one machine and wrong on another.

For a normal layout, this is fine. Responsive design is supposed to adapt. For a measuring tool, it is fatal.

The measurement model

The ruler uses a simple internal value:

pixelsPerMm

Once that value is known, every mark can be drawn from real units instead of guesses.

const x = millimeters * pixelsPerMm;

A centimeter tick is every 10 millimeters. A half-centimeter tick is every 5 millimeters. A millimeter tick is every 1 millimeter.

Inch marks are the same idea:

const inch = 25.4 * pixelsPerMm;

After calibration, the tool is not asking "how many CSS pixels should a ruler be?" It is asking "how many CSS pixels equal one real millimeter on this current screen setup?"

That distinction matters.

Why I used a credit card for calibration

The easiest calibration reference is something most people already have: a credit card, debit card, or standard ID card.

These cards follow the common ID-1 physical size: about 85.6 mm wide and 54 mm tall.

The tool shows a card-sized overlay. You hold the real card against the screen and drag the overlay edge until both widths match. From there:

pixelsPerMm = overlayWidthInPixels / 85.6

That single calculation gives the ruler its real-world scale.

It is more reliable than asking users to know their monitor DPI. Many people do not know their screen's true diagonal size, operating systems often apply scaling, and laptops commonly use high-density panels where "default" DPI assumptions are wrong.

Why DPI input still exists

Credit-card calibration is better for most users, but manual DPI is still useful for technical users.

If someone knows their monitor resolution and physical size, they can calculate the true pixel density and enter it directly.

The conversion is:

pixelsPerMm = DPI / 25.4

This is also useful when testing across multiple monitors. A user can quickly enter known DPI values for each screen instead of recalibrating every time.

Browser zoom is the easiest way to break it

If you calibrate the ruler at 100 percent browser zoom and later zoom the page to 125 percent, the ruler will no longer be physically accurate.

That is not a bug in the ruler. The browser is doing exactly what zoom is designed to do: scale the page.

The practical rule is:

set browser zoom to 100 percent
calibrate the ruler
measure without changing zoom
recalibrate if the window moves to another display

The tool stores calibration in localStorage, so it can remember the scale for the same browser and display setup. But it cannot magically know that a user moved the window from a laptop panel to an external monitor.

Why SVG is a good fit

The ruler itself is drawn with SVG because tick marks and labels are geometric primitives.

SVG makes it easy to generate:

long horizontal scales
millimeter ticks
centimeter labels
inch divisions
vertical mode by rotating the frame
crisp marks without blurry canvas scaling

Canvas would also work, but SVG keeps the ruler inspectable and clean. For this type of UI, the DOM cost is small enough and the clarity is worth it.

What the tool is good for

An online ruler is not a replacement for a workshop measuring tool. It is useful for quick, flat, small measurements where the object can be held against the screen.

Good examples:

checking a screw size
measuring a small label
checking a card, sticker, or photo print
estimating jewelry or craft material
verifying a PDF or design element at near 1:1 scale
quick classroom or desk measurements

Bad examples:

measuring anything heavy enough to damage a screen
measuring objects that are not flat
measuring objects longer than the display
precision engineering tolerances

The tool is practical, not magical.

The most important UX decision

The calibration step has to be visible.

Many online rulers hide the accuracy problem and present the ruler as if every display is already correct. That creates false confidence.

I wanted the interface to be honest:

Here is the ruler.
Here is why it may be wrong.
Here is a quick calibration method.
Here is the saved status after calibration.

For measurement tools, trust matters more than looking minimal.

What I would improve next

The next useful improvements would be:

per-monitor saved calibration profiles
a print-to-check calibration sheet
optional camera-assisted calibration
keyboard shortcuts for switching units and orientation
a small measurement marker that users can drag along the ruler

But the current version already handles the main hard problem: mapping browser pixels to real-world units with a reference object the user already owns.

Takeaway

The interesting part of an online ruler is not drawing tick marks. The interesting part is admitting that screens lie about physical size, then giving users a fast way to correct that.

Once you have an accurate pixelsPerMm, the rest becomes straightforward geometry.

That is the lesson I keep running into with browser-based utility tools: the browser gives you enough primitives to build useful hardware-adjacent tools, but you have to be honest about where the browser abstraction stops and the physical world begins.