barrier VS ddcutil

For software KVM you can use https://github.com/debauchee/barrier

I use it between a Windows PC & a Macbookpro (Linux version available but I don't have Linux)

libei looks useful. But IDK why libei is necessary to run Barrier with Wayland?

For client systems, couldn't there just be a virtual /dev/inputXYZ that Barrier forwards events through

And for host systems, it looks like xev only logs input events when the window is focused.

Is xeyes still broken on Wayland, and how to fix it so that it would work with Barrier?

With Barrier, when the mouse cursor reaches a screen boundary, the keyboard and mouse input are then passed to a different X session on another box until the cursor again crosses a screen boundary rule.

Barrier is a fork of Synergy's open core: https://github.com/debauchee/barrier

libei:

I have a similar gaming/WFH setup (2 monitors at 1440p 144hz) and I’ve been using Barrier instead of a physical kvm, and it works really well. Not sure if you’re open to a software kvm but if you are, I’m happy to answer any questions about it if you have any.

Have you tried Barrier? I casually used it to swap between my main rig and my MBP. Took a minute to get it setup but once I sorted it all out it worked pretty well. It has some settings and tweaks built in to address some of the layout issues you mentioned...

Barrier appears to handle PC switching only for the keyboard and mouse.

Sorry, probably not entirely on topic and can't answer anything reliable about the multimonitor stuff, but a tip regarding the 2 mice and 2 keyboards for the 2 different computers: use this: https://github.com/debauchee/barrier It's oss multi-os software that lets you use one mouse and keyboard (server) on several PCs (clients) easily over your LAN.

Barrier is a free and open source alternative.

Apologies. I hate when people do that as well.

In addition to the other links posted, ddcutil.org has some more good info: https://www.ddcutil.com/#introduction

Sous Linux j'avais utilisé ddcutil

Most monitors have a Virtual Control Panel (VCP), which implements features defined in the Monitor Control Command Set (MCCS). This is a VESA standard. You can find the Input selection command in table 8-10. You send these commands over an I2C bus called Display Data Channel/Command Interface which is yet another VESA standard. If you are running Windows https://www.nirsoft.net/utils/control_my_monitor.html will let you use every VCP feature your monitor has. For Linux, https://www.ddcutil.com/ does this. For Mac, https://github.com/alin23/Lunar

The protocol is called DDC , it's a VESA standard. In there, it's called VCP features. If you are running Windows https://www.nirsoft.net/utils/control_my_monitor.html will let you use every VCP feature your monitor has. For Linux, https://www.ddcutil.com/ does this. For Mac, https://github.com/alin23/Lunar note how all three mention input selection.

ddcutil (a command-line tool, and what most UI tools are based on)

A related non rust tool (that also has an optional GUI) is ddcutil. How does this compare to that?

I've also used ddcui: https://www.ddcutil.com/#introduction, available as an AUR package: https://github.com/rockowitz/ddcutil. This has a nice GUI: https://www.ddcutil.com/screenshots/ddcui_features.png and works on everything I've tried it on out of the box.