From 0a9e17af75bf2a359b8f2eec01e26bab8268f245 Mon Sep 17 00:00:00 2001 From: Joe Rayhawk Date: Wed, 27 Jul 2011 18:37:37 -0700 Subject: Notes: Windows network audio: notes on improving networking flexibility. --- notes/windows_network_audio.mdwn | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'notes') diff --git a/notes/windows_network_audio.mdwn b/notes/windows_network_audio.mdwn index 331bded..a206afe 100644 --- a/notes/windows_network_audio.mdwn +++ b/notes/windows_network_audio.mdwn @@ -28,7 +28,7 @@ On the sending (Windows) host, run something to the effect of ## Getting a PCM UDP stream *into* a Windows virtual audio device: -If you want a separate (non-echoing) device for a microphone, make [VAC][2] +If you want a separate (non-echoing) device for a microphone, make [VAC][1] cable 2, then make it the default communications device in mmsys.cpl. On the receiving (Windows) host, run something to the effect of @@ -52,7 +52,11 @@ did not pan out for me, so I had to work out their index number by hand. They start from 0. In my case, it's 1. Restarting any part of this sox/netcat/netcat/alsa chain requires restarting -everything *in order*, since that wave header is critical. +everything *in order*, since that wave header is critical. You can probably +make the network half of this a bit more dynamic by manually specifying +a raw PCM format on both ends rather than relying on the wave header, but +you'd have to be careful to match the [VAC][1] settings in order to avoid +introducing resampling latency. Windows sometimes does something horrible to TCP buffering; if you value latency, use UDP wherever practical. -- cgit v1.2.3