scream VS barrier

Not sure about NixOS specifically, but I'm pretty sure Scream is the widely accepted audio passthrough solution for Windows VMs.

I had a situation where there was a lot of noise on any usb connection from my PC to my DAC, but no noise on the usb from my jetson nano (similar to a raspberry pi). I set up a wireless audio interface between them using a project called Scream, so I could play audio on my PC and have it come out the usb port of the jetson. It creates a virtual sound card on the windows side, meaning you can send any/all audio from any source on the pc, which I think is what you're looking for. Warning, it was a pretty involved process and the final results were imperfect, it worked great 99% of the time but had weird pops and stutters 1% of the time.

Have you tried scream (with or without IVSHMEM)?

Hello all. I'm trying to send audio from my windows desktop pc to my linux mint laptop over an ethernet cable connected betwen the two machines as I don't have a router near them (I'm using wifi in both). I found this SCREAM tool to take the audio from the windows pc to the network but I'm not a networks expert at all. I wanna know if what I'm trying to do is even possible and if so, how can I set my linux to get the audio and play it on my headphones. Thanks.

Solved with Scream https://github.com/duncanthrax/scream

So thats really strange, so maybe try Scream audio it's on github with documentation https://github.com/duncanthrax/scream

How does connecting sound in pulseaudio compare to scream?

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.