#Next Livestream 17th April 2pm GMT+2 - Guest: Simon, Lead Software Engineer - POST QUESTIONS HERE >

1 messages · Page 1 of 1 (latest)

gritty delta
#

Rappy Yappy live will be back, here's the details:

Next livestream episode: 17th April 2pm (GMT+2)
Guest: Simon, Lead Software Engineer (the guy behind Wooting's software and firmware)

If you have any questions about the Wooting software, how the keyboard firmware functions or other Wooting programming/software related questions, post them here!

Best questions will get answered on the April 17th livestream! See you there.

honest mulch
#

What is the most annoying type of co-worker in the view of a Software Engineer for Wooting?SwitchyHeHe

cloud mason
#

which branch of wooting staff do you hate the most

onyx glade
#

0.0001mm rapid trigger when, I want bacteria to play for me

candid cedar
#

When is a Roblox cheat client coming to wooting keyboards?

lethal imp
#

When can we have on board macro?

crimson arrow
#

When will Wooting make their own version of the Neuralink? I need switchy to play competitive bortnite for me

honest mulch
#

I think Sno wants to know "when is switch selector going live or when is next performance update coming" smile

lethal imp
#

I think Coin wants to know "who is the most annoying in his eyes"

honest mulch
crimson arrow
#

What aspirations do you have for wooting software to be in the next 10 years?

somber epoch
#

I have a few questions that I'd love to hear addressed in the next podcast:

  1. I’m trying to understand what the Wooting Analog SDK actually exposes to developers. From the docs, it looks like the public API provides per-key analog values (for example through read_analog / read_full_buffer) and device info, but I don’t see a documented way to access raw matrix data. Is that correct?

More specifically: does the SDK give developers raw matrix/sensor data, or only processed per-key analog values such as normalized travel distance/actuation values? And at a high level, how does the SDK pipeline work between the keyboard, the plugin, and the app?

  1. What was the reasoning behind choosing the current proprietary 80HE layout instead of something like H87? From a modding perspective, H87 seems much more cross-compatible with existing cases and boards, while the 80HE launched with effectively no third-party case compatibility. One of the big appeals of layouts like H87 is that they’re already widely used across many boards, with shared PCB mounting patterns and onboard USB-C placement, which makes swapping and experimenting much easier.

So I’m curious what tradeoffs led to the 80HE layout being preferred. Was it mainly engineering constraints, performance goals, structural reasons, manufacturing considerations, or something else? I’m especially asking because Wooting has used modder-friendly standards before, like GH60, so I’d love to understand why a more proprietary route made more sense here despite the reduced compatibility and mod-friendliness.

#

Oh, I'm also wondering about filtering and stuff. How does Wooting's filtering/smoothing work, if there is any? Does the board rely purely on dead zones and ignore any kind of sensor filtering or smoothing for the lowest latency, or how much delay is realistically added by the filtering?

I'm curious if users could have the option eventually to have some kind of level of customization to how much filtering there is. For example, having a three-tap Binomial FIR, which would add a single instance of delay, or a five-tap, which would add two instances of delay. They would have different levels of filtering, which could improve the precision and stability, with the downside of slightly more delay, and this way, users could choose how much they prioritize precision and stability versus raw latency.

I would also wonder if it's something that could be done on the PCB level, like having it apply to scans individually instead of reports, so instead of losing one report, every report, you could have it affect the scans, which might not affect the delay as much.

honest mulch
#

What's the next bigger feature that will use background services? SwitchyHeHe

gritty delta
#

Next Livestream 17th April 2pm GMT+2 - Guest: Simon, Lead Software Engineer - POST QUESTIONS HERE >

elfin pelican
#

Gamepad update when simon?

somber epoch
gritty delta
#

80he has been answered many times already in regards to h87 format not being anywhere close to as universal as gh60 on top of other factors