Audio problems

​

macOS

1. Grant microphone permissions
   • Open System Settings → Privacy & Security → Microphone
   • Enable TCP Streamer in the list
   • Restart the application
2. Check device status
   • Open Audio MIDI Setup (Applications → Utilities)
   • Verify device appears and is not grayed out
   • Ensure sample rate matches TCP Streamer settings (44.1 or 48 kHz)
3. Restart CoreAudio
   sudo killall coreaudiod
   

​

Windows

1. Enable audio device
   • Open Settings → System → Sound
   • Click More sound settings
   • Right-click in device list → Show Disabled Devices
   • Enable your device if disabled
2. Update audio drivers
   • Open Device Manager
   • Expand Audio inputs and outputs
   • Right-click device → Update driver
3. Check device properties
   • Right-click device → Properties
   • Ensure device is working properly
   • Match sample rate in Advanced tab to TCP Streamer settings

​

Linux

1. Verify ALSA/PulseAudio
   # List ALSA devices
   arecord -l
   
   # List PulseAudio sources
   pactl list sources
   
   # Check PipeWire (if using)
   pw-cli list-objects Node
   
2. Permissions
   # Add user to audio group
   sudo usermod -a -G audio $USER
   
   # Log out and back in for changes to take effect
   
3. Test device directly
   # Record 5 seconds of audio
   arecord -d 5 -f cd test.wav
   aplay test.wav
   

1. Check device names carefully
   • Devices may have similar names (e.g., “Microphone (USB)” vs “Microphone (Built-in)”)
   • Look for manufacturer names or connection type
2. Use the visual volume indicator
   • Select a device from the dropdown
   • Speak or play audio
   • The real-time RMS meter should show activity
   • If no movement, you have the wrong device
3. Test each device systematically
   • Select device
   • Generate audio on that source
   • Check the volume meter
   • Note which device responds

• Built-in microphone selected instead of loopback device
• HDMI audio output selected instead of system audio
• Monitor device instead of playback device (Linux)
• Disabled device still showing in list

1. Device was unplugged
   • USB devices disconnected
   • Bluetooth devices went out of range
   • Docking station disconnected
2. Driver crash or reload
   • Audio driver encountered an error
   • System updated drivers in background
   • Power management suspended device
3. Sample rate mismatch
   • System changed device sample rate
   • Another application requested exclusive mode
   • Device doesn’t support requested format

1. Use wired connections
   • Prefer USB or built-in devices over Bluetooth
   • Ensure USB cables are secure
   • Avoid USB hubs when possible
2. Disable exclusive mode (Windows)
   • Sound Settings → Device Properties → Additional device properties
   • Advanced tab → Uncheck “Allow applications to take exclusive control”
3. Disable power management
   • Device Manager → Audio device → Properties
   • Power Management tab → Uncheck “Allow computer to turn off this device”
4. Lock sample rate
   • Configure device to use fixed sample rate matching TCP Streamer
   • Windows: Sound Settings → Device Properties → Advanced
   • macOS: Audio MIDI Setup → Device → Format

• Base ring buffer: 8000ms (vs 5000ms for standard inputs)
• Adaptive range: 4000-12000ms (wider tolerance)
• Expected latency: 4-12 seconds depending on network quality

1. Enable adaptive buffering
   • Turn on Adaptive Buffer in Advanced settings
   • Set minimum to 4000ms, maximum to 12000ms
   • Allow buffer to stabilize over 30-60 seconds
2. Use network preset for your connection
   • Ethernet: Better performance, lower latency possible
   • WiFi: Use WiFi preset for balanced performance
   • WiFi (Poor): Maximum stability for challenging conditions
3. Increase buffer size
   • Change Buffer Size to 2048 samples
   • Reduces processing frequency
   • Gives WASAPI more time for each callback
4. Alternative: Use VB-Audio Cable
   • Install VB-Audio Virtual Cable
   • Set as default playback device
   • Select as input device in TCP Streamer
   • More stable than WASAPI loopback, lower latency possible

1. Connect audio output device
   • Plug in speakers or headphones
   • Ensure device is enabled and set as default playback device
   • Volume doesn’t need to be high, but audio must be playing
2. Verify playback is occurring
   • Open Volume Mixer (right-click volume icon)
   • Confirm application is producing audio
   • Check that playback device is receiving signal
3. Select correct loopback device
   • Loopback device name usually includes “(Loopback)” suffix
   • Must match the playback device you want to capture
   • Example: If using “Speakers (Realtek)”, select “Speakers (Realtek) (Loopback)”
4. Alternative: Use VB-Audio Cable
   • More reliable than WASAPI loopback
   • Doesn’t require physical audio output
   • Lower latency and better stability

​

Option 1: BlackHole (Free)

1. Install BlackHole
   brew install blackhole-2ch
   # or download from https://github.com/ExistentialAudio/BlackHole
   
2. Create Multi-Output Device
   • Open Audio MIDI Setup
   • Click + → Create Multi-Output Device
   • Check both BlackHole 2ch and your speakers
   • Right-click → Use This Device For Sound Output
3. Configure TCP Streamer
   • Select BlackHole 2ch as input device
   • Set sample rate to match (48 kHz recommended)

​

Option 2: Loopback by Rogue Amoeba (Paid)

• Professional solution with GUI
• Easy virtual device creation
• Advanced routing capabilities
• https://rogueamoeba.com/loopback/

1. List available monitors
   # PulseAudio
   pactl list sources | grep -E '(Name|Description)'
   
   # PipeWire
   pw-cli list-objects Node | grep -E '(audio|monitor)'
   
2. Create loopback module (PulseAudio)
   # Load module
   pactl load-module module-loopback
   
   # Make persistent
   echo "load-module module-loopback" >> ~/.config/pulse/default.pa
   
3. Select monitor device
   • Look for devices with “.monitor” suffix
   • Example: “alsa_output.pci-0000_00_1f.3.analog-stereo.monitor”
   • Select this device in TCP Streamer

# Load snd-aloop module
sudo modprobe snd-aloop

# Make persistent
echo "snd-aloop" | sudo tee -a /etc/modules

• TCP Streamer detects silence and stops transmission to save bandwidth
• This is expected behavior when no audio is playing

• Play audio on your system
• Watch the real-time volume meter in TCP Streamer
• Check activity log for “Silence detected” or “Audio resumed” messages

• Play audio to trigger streaming
• Lower silence threshold if legitimate audio is being detected as silence
• Disable silence detection temporarily to test

• Input device volume is at zero
• Device is muted in system settings
• Application producing audio is muted

• Check system volume mixer
• Unmute the device
• Increase input device volume
• Verify application is producing audio output

• See “Wrong device selected” section above
• Use volume meter to verify correct device

1. Check input levels
   • Use the real-time RMS meter
   • Audio should be in the green range, not constantly maxed
   • Reduce input gain if meter is always at maximum
2. Verify sample rate match
   • Device native sample rate should match TCP Streamer setting
   • Mismatched rates cause resampling artifacts
   • Check device properties in system audio settings
3. Buffer size tuning
   • Very small buffers (256) can cause distortion under load
   • Try 512 or 1024 for better quality
   • Larger buffers reduce processing artifacts
4. Disable audio enhancements
   • Windows: Device properties → Enhancements → Disable all
   • macOS: Audio MIDI Setup → Device → Ambient Noise Reduction (off)

• Upgrade to v1.8.0+ for improved audio architecture
• Linux users especially benefit from noise elimination

• Uses RMS (Root Mean Square) analysis
• Threshold is configurable via slider
• White line on volume meter shows current noise floor
• Timeout determines how long silence must persist before stopping

1. Tune threshold using volume indicator
   • Play typical audio content
   • Watch the real-time volume meter
   • Set threshold slider just above the noise floor (white line)
   • Should trigger on silence, not quiet audio
2. Increase timeout
   • Set longer timeout (e.g., 10 seconds instead of 3)
   • Allows brief pauses without stopping stream
   • Good for music with quiet passages
3. Disable for continuous content
   • Turn off silence detection for 24/7 streaming
   • Accept higher bandwidth usage
   • Ensures no audio is missed
4. Adjust input gain
   • If legitimate audio is too quiet, increase input gain
   • Raises signal above noise floor
   • Makes distinction clearer

1. Update to v1.8.1 or later
   • Prefill gate is only available in v1.8.1+
   • Download from releases page
2. Verify buffer settings
   • Ensure ring buffer is at least 2000ms
   • Prefill gate needs buffer headroom to work
3. Check network conditions
   • Startup stutter can also be caused by initial network congestion
   • Enable adaptive buffering to compensate