notes: windows network audio: whoops, put 3-hour problem under the wrong heading

1 files changed, 4 insertions, 4 deletions

diff --git a/notes/windows_network_audio.mdwn b/notes/windows_network_audio.mdwn
index 2805370..537e8e1 100644
--- a/notes/windows_network_audio.mdwn
+++ b/notes/windows_network_audio.mdwn
@@ -28,10 +28,6 @@ On the sending (Windows) host, run something to the effect of
 
 ## Getting a PCM UDP stream *into* a Windows virtual audio device:
 
-After three hours, static (from Windows) or silence (to Windows) arises instead
-of the PCM stream expected. I assume this is a two or four gigabyte addressing
-limit in 32-bit version of SoX. A 64-bit version needs testing.
-
 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.
 
@@ -47,6 +43,10 @@ On the sending host, run something to the effect of
 
 ## Additional notes
 
+After three hours, static (from Windows) or silence (to Windows) arises instead
+of the PCM stream expected. I assume this is due to some addressing limit in
+32-bit SoX. A 64-bit version should probably be tested.
+
 This was done on Windows 7. The core concepts should work fine on other
 versions, though the details of making separate device defaults for playback
 and recording will presumably be different.