Overview
TCP Streamer on Windows provides native system audio capture through WASAPI loopback mode, eliminating the need for virtual audio cables in most scenarios. This guide covers installation, audio configuration, and Windows-specific optimizations.Installation
Download & Install
Download the installer
Download the latest Windows installer from the Releases Page.Choose between:
.msi- Standard Windows installer (recommended).exe- Portable executable
Run the installer
Double-click the downloaded
.msi file and follow the installation wizard.The application will be installed to:System Requirements
- OS: Windows 10 or Windows 11
- RAM: 100 MB minimum
- Audio: WASAPI-compatible audio device
- Network: Stable connection to TCP server
Audio Capture Methods
WASAPI Loopback (Recommended)
Windows includes native system audio capture through WASAPI loopback mode. This is the easiest method for capturing “what you hear” without additional software.Important: You must have speakers or headphones plugged in for WASAPI loopback to capture audio. The loopback device mirrors the output device.
Enable WASAPI Loopback
Enable loopback mode
Check the “Enable Loopback (Windows)” checkbox.This tells the application to capture the audio output instead of input.
WASAPI Loopback Characteristics
- Latency: Higher than virtual cables (4-12 seconds typical)
- Buffer Requirements: Larger buffers needed for stability
- CPU Usage: Very low
- Quality: Perfect digital copy of system audio
- Network Sensitivity: More sensitive to WiFi jitter than other methods
Virtual Audio Cable (Alternative)
For lower latency or more control, use virtual audio cable software: Popular Options:- VB-Audio Cable (Free)
- VoiceMeeter (Advanced routing)
Set as default output
In Windows Sound Settings:
- Right-click the speaker icon in taskbar
- Select Sound Settings
- Set the virtual cable as your default output device
Configuration
Optimal Settings for WASAPI Loopback
WASAPI loopback requires larger buffers due to timing variability:- Ethernet (Wired)
- WiFi (Good Signal)
- WiFi (Poor Signal)
For stable wired connections:
- Sample Rate: 48 kHz
- Buffer Size: 1024 samples
- Ring Buffer: 6000-8000ms
- Adaptive Buffer: Enabled
- Min: 4000ms
- Max: 12000ms
- Expected Latency: 4-6 seconds
Optimal Settings for Virtual Audio Cable
Virtual cables provide more predictable timing:- Sample Rate: 48 kHz
- Buffer Size: 512 or 1024 samples
- Ring Buffer: 2000-5000ms
- Adaptive Buffer: Enabled (2000ms - 6000ms)
- Expected Latency: 2-4 seconds
Network Presets
Use the Advanced tab network presets for quick configuration:| Preset | Ring Buffer | Chunk Size | Adaptive Range | Best For |
|---|---|---|---|---|
| Ethernet | 2000ms | 512 | 2-6s | Wired + Virtual Cable |
| WiFi | 4000ms | 1024 | 3-10s | WiFi + Virtual Cable |
| WiFi (Poor) | 8000ms | 2048 | 5-15s | WASAPI or poor WiFi |
The application automatically selects appropriate default buffers when you enable WASAPI loopback mode (8000ms base).
Performance & Optimization
CPU Usage
TCP Streamer is extremely lightweight on Windows:- Idle: <1% CPU
- Streaming (WASAPI): 1-3% CPU
- Memory: 2-3 MB typical, up to 10 MB with large buffers
Reducing CPU Usage
If you experience high CPU usage:- Increase buffer size to 2048 samples
- Lower sample rate to 44.1 kHz if 48 kHz is unnecessary
- Disable high priority thread in Advanced settings
- Close other audio applications that may compete for the audio device
Network Quality
Monitor the Network Quality indicator in the Statistics tab:- Excellent: <5ms jitter - Perfect streaming
- Good: 5-15ms jitter - Stable, minimal buffer adjustments
- Fair: 15-30ms jitter - Adaptive buffer actively managing
- Poor: >30ms jitter - Consider wired connection or larger buffers
Troubleshooting
WASAPI Loopback Stuttering
Symptoms: Audio cuts out, stutters, or has periodic dropouts Solutions:Enable adaptive buffer
Navigate to Audio Settings and enable Adaptive Buffer.Set:
- Min: 5000ms
- Max: 15000ms
Use network preset
Apply the WiFi (Poor Signal) preset in the Advanced tab, even for wired connections.
WASAPI loopback trades latency for reliability. If you need <4 second latency, use a virtual audio cable instead.
Audio Device Not Found
Problem: Your audio device doesn’t appear in the dropdown Solutions:-
Check device is enabled:
- Right-click speaker icon → Sound Settings
- Ensure the device is enabled and not disabled
- Restart the application after connecting new audio devices
-
Check for exclusive mode conflicts:
- Right-click speaker icon → Sound Settings → Device Properties
- Under Advanced, uncheck “Allow applications to take exclusive control”
- Update audio drivers from your device manufacturer
Connection Fails
Problem: “Failed to connect to TCP server” Solutions:Verify server is running
Ensure your TCP server (e.g., Snapcast) is running and listening on the specified port.
Check Windows Firewall
Add an exception for TCP Streamer:
- Windows Security → Firewall & Network Protection
- Allow an app through firewall
- Add TCP Streamer
Test connectivity
Open Command Prompt and test the connection:If this fails, the issue is network-related, not TCP Streamer.
No Audio Streaming (Connected but Silent)
Problem: Connection established but server receives no audio Possible Causes:- Silence detection is working correctly - No audio is playing
- Audio input is muted or volume too low
- Wrong device selected - Not capturing the correct audio source
- Loopback not enabled when using output device
- Play audio on your computer while streaming
- Check the real-time volume indicator moves when audio plays
- Verify silence threshold isn’t set too high
- Ensure “Enable Loopback” is checked if using speakers/headphones
- Check Windows volume mixer (Win + G → Audio)
Permission Errors
Problem: “Access denied” when starting stream Solutions:- Run as Administrator (right-click → Run as administrator)
- Check antivirus software isn’t blocking TCP Streamer
- Reinstall with administrator privileges
High Latency
Problem: 10+ seconds of delay between computer and server Expected Behavior:- WASAPI loopback typically has 4-12 seconds latency
- This is a trade-off for stability and compatibility
- Use virtual audio cable instead of WASAPI loopback (2-4 seconds)
- Use wired network instead of WiFi
- Reduce ring buffer to minimum stable value
- Disable adaptive buffer if network is very stable
Automation
Auto-start on Windows Boot
Enable Auto-start on launch in TCP Streamer settings:- Navigate to Automation tab
- Enable “Start on system boot”
- The application will launch minimized to system tray
- Press Win + R
- Type
shell:startupand press Enter - Create a shortcut to TCP Streamer in this folder
Auto-stream Configuration
For fully automated operation:- Enable Auto-start on launch - Start with Windows
- Enable Auto-stream - Begin streaming immediately
- Enable Auto-reconnect - Retry connection on failure
- Set silence detection - Stop when no audio for X seconds
Advanced Features
QoS (Quality of Service) Tagging
Improve network priority by setting DSCP/TOS values:- Navigate to Advanced tab
- Select QoS preset:
- VoIP (EF) - Highest priority
- Low Delay - Expedited forwarding
- Throughput - Bulk transfer
QoS requires router support and configuration to be effective.
High Priority Thread
Reduce network jitter by elevating thread priority:- Navigate to Advanced tab
- Enable High Priority Thread
- This may require administrator privileges
- WiFi connections with variable latency
- Systems with high background CPU usage
- Professional audio applications
- May cause audio glitches on low-end systems
- Unnecessary on stable wired connections
Best Practices
For Multi-room Audio (Snapcast)
- Use WASAPI loopback for simplicity
- Accept 4-6 seconds of latency (not noticeable across rooms)
- Enable Auto-reconnect for reliability
- Set silence timeout to 300 seconds (5 minutes)
- Use WiFi (Poor) preset for maximum stability
For Low-latency Applications
- Use virtual audio cable (VB-Audio)
- Use wired Ethernet connection
- Apply Ethernet preset
- Set buffer size to 512 samples
- Disable silence detection for continuous stream
For Laptop/Mobile Setups
- Use WASAPI loopback (no extra software)
- Apply WiFi (Poor) preset
- Enable Adaptive Buffer (5s - 15s range)
- Disable High Priority Thread to save battery
- Enable Auto-reconnect for handling network switches
Additional Resources
Platform: Windows 10/11 Audio API: WASAPI Native Loopback: Yes Typical Latency: 4-12 seconds (loopback) | 2-4 seconds (virtual cable)