Frontend Device FAQ
FAQ for frontend device connection. Confirm active path first: local output, DLNA, AirPlay 1, or HQPlayer. Overview: Connect frontend playback devices.
Paths and concepts
Section titled “Paths and concepts”Is “frontend device” the same as audio output settings?
Section titled “Is “frontend device” the same as audio output settings?”Not exactly. Frontend device is where sound is ultimately produced; Audio output settings (Settings → Playback) mainly control the local path. Network cast uses Connect, not WASAPI / ASIO device selection. See Concepts.
Connect vs remote library?
Section titled “Connect vs remote library?”| Remote library | Connect | |
|---|---|---|
| Role | Read files from NAS / Jellyfin | Cast current track to Renderer / AirPlay |
| Sound | Still needs local or Connect output | Defines network-side output |
See Connect page · vs remote library.
NAS in the list but cannot cast?
Section titled “NAS in the list but cannot cast?”NAS as Media Server (DMS) only serves files, not Media Renderer (DMR) playback. Connect a streamer or receiver with Renderer capability.
DLNA or AirPlay?
Section titled “DLNA or AirPlay?”If both supported, verify DLNA first (richer troubleshooting docs). AirPlay requires AirPlay 1 compatibility; no AirPlay 2. See Connect page · selection.
Local output
Section titled “Local output”OS plays, ECHO silent
Section titled “OS plays, ECHO silent”Conclusion: ECHO output configuration, not wiring.
- Mode System.
- Output device matches Windows.
- Disable EQ, DSP, DSD, HQPlayer.
- Reset audio engine.
- Play MP3 test.
USB DAC plugged in, OS also silent
Section titled “USB DAC plugged in, OS also silent”Conclusion: Physical layer, driver, or Windows — not ECHO.
Check data cable, DAC power, default device, Device Manager. See Local output · USB DAC.
Should I install ASIO4ALL?
Section titled “Should I install ASIO4ALL?”Usually no. System or WASAPI Shared suffices for most USB DACs. ASIO for interfaces with vendor ASIO drivers. See ASIO vs exclusive.
Bluetooth headphones?
Section titled “Bluetooth headphones?”Supported via Windows Bluetooth; ECHO has no separate Bluetooth output mode. Use wired while troubleshooting.
Connect / DLNA
Section titled “Connect / DLNA”Empty Connect device list
Section titled “Empty Connect device list”Verify in order:
- Same segment as Renderer?
- Media Renderer enabled?
- Windows Private + firewall allows ECHO?
- VPN off?
- Router AP / guest isolation off?
- Phone DLNA app sees same Renderer?
See LAN and firewall · DLNA · not found.
Found but connect fails
Section titled “Found but connect fails”Common: Renderer cannot reach ECHO HTTP URL, format mismatch, firewall, no track selected.
See DLNA · connect fails.
After a successful cast, the PC is still audible
Section titled “After a successful cast, the PC is still audible”Expected: ECHO attempts to pause local playback.
If PC still audible: verify Connect shows connected; confirm sound source; disconnect and reconnect. See DLNA · misconceptions.
Renderer silent or drops after connect
Section titled “Renderer silent or drops after connect”| Verify | Action |
|---|---|
| Try MP3 | Rule out format |
| Wire streamer | Rule out Wi-Fi |
| Renderer can reach ECHO LAN IP | Firewall / multi-NIC / isolation |
| Disable EQ, exclusive | Processing conflict |
Remote library track fails to cast
Section titled “Remote library track fails to cast”ECHO may proxy or transcode remote files. Confirm track plays locally in ECHO first. Insufficient bandwidth causes stutter or timeout.
AirPlay
Section titled “AirPlay”HomePod / recent Apple speaker will not connect
Section titled “HomePod / recent Apple speaker will not connect”No AirPlay 2 support. Use DLNA if available or local output. See AirPlay boundaries.
AirPlay vs Bluetooth speaker?
Section titled “AirPlay vs Bluetooth speaker?”Different paths. AirPlay uses IP LAN (RAOP); Bluetooth uses Windows pairing.
HQPlayer
Section titled “HQPlayer”Skip local output and go straight to HQPlayer?
Section titled “Skip local output and go straight to HQPlayer?”Not recommended. Verify ECHO System (or WASAPI), then HQPlayer + NAA alone, then enable in ECHO.
See Scenarios · HQPlayer.
Explicitly unsupported
Section titled “Explicitly unsupported”- AirPlay 2 multi-room sync
- System screen / video mirroring
- DRM or paid-access bypass
- NAS automatically as Renderer (DMS ≠ DMR)
- Guaranteed full UPnP optional features on all third-party Renderers
Still stuck?
Section titled “Still stuck?”Include when reporting:
| Info | Example |
|---|---|
| Primary path | Local / DLNA / AirPlay / HQPlayer |
| ECHO version | From settings / about |
| Windows version | Settings → System → About |
| Hardware | DAC / streamer / speaker model |
| Network | Home router / dorm / VPN yes/no |
| Docs tried | Steps attempted and symptoms |
| Screenshots | Connect state, output settings, errors |
Further reading
Section titled “Further reading”| Topic | Doc |
|---|---|
| Local wiring | Local output |
| Connect | Connect page |
| Scenarios | Typical scenarios |
| Network | LAN and firewall |