Volume2 VS barrier

If you need to quickly switch from X3 to other device (MB + speaker) there is the Volume2 app, since Win11 sound/volume settings are a mess.

https://github.com/irzyxa/Volume2 which also has many other features

I use https://github.com/irzyxa/Volume2

If you've ever used digital encoders with Creative products, you may have noticed that it's only possible to adjust the overall volume by changing the volume of the "What U Hear" recording device. While some solutions like Volume2 have been suggested, I struggled to find the right settings in there.

HideVolumeOSD or for even more control Volume²

Volume keys doesn't show a visual response: This is because an update from apple software update for windows. You can disable updates, in my case I've installed Volume2, works great and it has a skin to mimic apple and windows 11 appearance.

You will want to seek out and install a third-party tool like Volume2 to take over system-wide volume slider control and redirect the shortcuts/media keys to adjust the "What U Hear" recording device level instead of your default output device (which should remain unchanged/normal).

Yep I wanted the same thing and was able to do it. I used Volume2 and chose the skin that looks like the default windows volume osd. I also have HideVolumeOSD running like someone else mentioned but I don't think that's actually necessary with Volume2.

Try this: Volume2

Try Volume2, maybe you'll find what you need there. For example, I use the volume control by scrolling the mouse wheel over the tray, with a beautiful indicator, and the percentage of sound is displayed in the tray.

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.