scream VS pyznap

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?

Sanoid/syncoids been mentioned but honestly for once a week learning by doing . Pyznap also excellent when you want to automate. https://github.com/yboetz/pyznap

In contrast, zfs snapshots are immutable, and thus anything short of a hardware failure can be addressed with a simple zfs rollback command. This includes deliberate, accidental, and malicious actions. They can also be automated (I personally use pyznap but syncoid is also quite popular), creating what is effectively an incremental backup. I maintain - for each dataset - 24 hourly, 7 daily, 6 monthly, and 1 yearly snapshot. Additionally, I have a wholly separate server that wakes up once a day to ingest these snapshots via zfs send/recv, so even if I made a horrible mistake or suffered a catastrophic hardware failure, I could completely restore from the other server. This last point brings snapshots firmly into the realm of backups, IMO.

Another favorite option is Pyznap, which is python based and originally created to have have a few features and changes compared to sanoid. The author is also active here on reddit. I and not sure what the differences are anymore, it'll come down to trying them and preference.

I have two Supermicro X9 2Us, each with Proxmox. One has allegedly existed solely as a backup target, which wakes up daily to ingest ZFS snapshots using pyznap. Unfortunately, for reasons which are unclear, this particular node doesn't always like to see its boot device, which is an NVMe drive. It's the exact same board as my primary, with the exact same modified BIOS to allow booting from NVMe. It usually takes 2-3 cycles before it'll see it and boot.

I have two nearly identical systems, both running Proxmox, with Debian VMs. One is a backup, which (once this is worked out) will wake up daily to ingest incremental backups. I'm using pyznap to handle the backup strategy.

https://github.com/yboetz/pyznap/issues/1#issuecomment-351015432