https://github.com/willmuldrew/lagmeter
(It attempts to do a few other things but it’s best for measuring keyboard event to screen update latency)
250 karma · joined September 11, 2020
https://github.com/willmuldrew/lagmeter
(It attempts to do a few other things but it’s best for measuring keyboard event to screen update latency)
The next day my debugging instinct kicked in, I bought some PUSH stickers and did some covert guerrilla ergonomic stickering. Problem solved and it made me smile every time I went past that cafe!
(Full disclosure: Weepy and I played with Jamulus then he had a crack at building sub.live)
https://m.youtube.com/watch?v=wdgULBpRoXk
edit: ah, sorry, I see someone's posted a link to this video already!
I ended up with an ESP-32 module connected to the house wifi, and an opto-isolated circuit to trigger it from the doorbell wiring. It sits in the basement where it's easy to give it power from a USB power adaptor.
Of course, the irony was that it was only after I'd lost a few days going down this particular rabbit hole that I discovered that almost every visitor (and especially delivery drivers) uses our door _knocker_, rather than the doorbell since it's much more obvious! The next project may be to electrify that, or mount a vibration sensor on the door!
There’s a bunch of similar bits of software but none of them are super welcoming for the less technically inclined. I guess that the experience is often going to be limited by network performance (specifically jitter and loss on UDP) so it’s a challenging thing to make super slick/consistent. I think that low latency 5G with latency guarantees might help solve it when its widely available though.
(Maybe double that for an alkaline one)
The threshold for me (and most people I think) is about 110ms between key strike and something appearing on the screen before something feels non-local and disembodied... which is good because I found I could get down to ~40ms local response time on a decent windows box. My 2015 macbook is about ~120ms for the terminal app.
That leaves 70ms latency budget to play with which can accommodate the the RDP overhead (~50ms) and the network hop (~10ms for me).
This whole journey started with me wondering if I should pay a small fortune for a better network connection, before I realised that most of the latency was in my keyboard and monitor!
I even built a Arduino Leonardo gadget to measure the lag systematically and some pcap software to spot the RDP packets on the wire. The code's pretty shoddy but it does the trick! You can see it and an example result with RDP here:
https://github.com/willmuldrew/lagmeter
Another big factor in the experience is jitter - so it's a good idea to ensure everything is plugged in if you can. Mice, keyboards and ethernet.
In essence, even if you have to RDP/remote into work, potentially you can still make it feel pretty local - don't give up hope!
As a physicist, turned developer, turned tech manager based in the UK I'm not quite sure what an opportunity looks like, and whether the right approach is to bash the plasma physics books, or wait for a more tech-orientated role to crop up.
I'm also really interested to know how these startup-esque companies are all going to handle their intellectual property now they're private enterprises - are their individual breakthroughs all going to be kept deeply secret (and vanish if/when most of them eventually fail) or are they all going to be frantically cross-licensing their discoveries so that in aggregate we don't lose out of the benefits of collaboration. According to A Piece of the Sun (by Daniel Clery) the early days of fusion research were hampered by international secrecy - things really started moving when researchers persuaded their governments to open up and let them work across borders.
[1] https://www.youtube.com/watch?v=L0KuAx1COEk [2] https://www.youtube.com/watch?v=KkpqA8yG9T4