Assuming a decent host with virtualization support enabled and low latency network. Where you can allocate sufficient resources so the VM will not be starved:
Create the VM with the native cpu intruction model, not the portable version, give sufficient memory (no ballooning), harware passthrough an entire PCIe USB hub (not the simple USB passthrough) for controllers and soundcards (I think this needs the device to support ACS for VFIO). In your Windows VM, make sure you install the virtio-win drivers. Also enable the qemu guest agent.
People report better audio latency accessing the VM through NoMachine or Parsec rather than Remote Desktop.
Assuming a decent host with virtualization support enabled and low latency network. Where you can allocate sufficient resources so the VM will not be starved:
Create the VM with the native cpu intruction model, not the portable version, give sufficient memory (no ballooning), harware passthrough an entire PCIe USB hub (not the simple USB passthrough) for controllers and soundcards (I think this needs the device to support ACS for VFIO). In your Windows VM, make sure you install the virtio-win drivers. Also enable the qemu guest agent.
People report better audio latency accessing the VM through NoMachine or Parsec rather than Remote Desktop.