Skip to content
⌂ Home

DLNA / Network Streamer

This guide is for sending music from ECHO to a DLNA / UPnP network streamer, receiver, TV, smart speaker, or amplifier.

ECHO’s casting model is:

ECHO selects and controls music -> ECHO exposes a temporary audio URL -> the DLNA renderer plays it

ECHO is not recording your sound card and streaming that audio. It gives the renderer a network URL for the current track.

  1. Put the ECHO computer and streamer on the same LAN.
  2. Enable DLNA / UPnP Renderer / Media Renderer mode on the streamer.
  3. Play or select a normal MP3 or FLAC in ECHO.
  4. Open ECHO’s Connect page.
  5. Click Refresh.
  6. Find your streamer in the device list.
  7. Click Connect.
  8. After playback starts, control play, pause, stop, volume, and seek from ECHO.

If the device list is empty, troubleshoot LAN discovery, firewall, router isolation, and streamer mode before changing audio output or EQ settings.

RoleMeaningExample
DMS / Media ServerProvides media filesNAS, Jellyfin, Windows media sharing
DMR / Media RendererPlays audioNetwork streamer, receiver, TV, smart speaker
DMC / Control PointControls playbackECHO or a phone controller app

ECHO acts like a control point and also exposes the current track through a temporary HTTP URL. You need a Media Renderer, not only a Media Server.

ECHO can:

  • Discover DLNA / UPnP Media Renderers.
  • Set the playback URL.
  • Send play, pause, stop, seek, and volume commands.
  • Poll playback state and position.
  • Provide audio and artwork URLs to the renderer.

ECHO prefers formats the device reports as supported. If the current file is unsupported, ECHO may use a conservative MP3 transcode path. Common friendly formats include MP3, WAV, FLAC, M4A/AAC, OGG, and AIFF, but device firmware matters.

Recommended:

ItemRecommendation
ECHO computerSame home router as the streamer
StreamerSame router; wired Ethernet if possible
Windows networkPrivate network
RouterGuest/AP isolation off
VPN / proxyOff for first setup
FirewallAllow ECHO / Electron / Node on private networks

Avoid first setup on hotel Wi-Fi, campus networks, corporate networks, guest Wi-Fi, phone hotspots, or VPN-routed networks. These may allow internet access while blocking local discovery.

Check:

  1. The device is powered on.
  2. It is on the same LAN as ECHO.
  3. DLNA / UPnP Renderer / Media Renderer mode is enabled.
  4. It is not stuck in Bluetooth, USB DAC, optical, coaxial, or another input mode.
  5. Volume is not zero.
  6. Another controller app is not occupying it.
  7. Old firmware devices may need a reboot.

Some devices expose DLNA Server but not DLNA Renderer. ECHO needs Renderer mode for casting.

  1. Play or select a track in ECHO.
  2. Use MP3 for the first test if possible.
  3. Open Connect.
  4. Click Refresh.
  5. Wait a few seconds.
  6. Find the device marked DLNA / UPnP.
  7. Click Connect.
  8. ECHO pauses local playback and asks the renderer to play.

ECHO does not allow empty-metadata casting. If the button is disabled, there may be no current track, the device may be unavailable, or the device is unsupported.

For local files:

local file -> ECHO HTTP service -> streamer reads URL -> streamer plays

For remote files:

remote URL -> ECHO forwards or transcodes -> streamer reads ECHO URL -> streamer plays

ECHO chooses a local LAN address for the streamer and creates a temporary URL similar to:

http://192.168.1.20:random-port/connect/audio/...

The streamer must be able to reach that URL, so firewall and router isolation matter.

FormatAdvice
MP3Best first test
FLACCommonly supported by streamers
WAVCompatible but large
M4A / AACOften works, older devices vary
OGG / OpusDevice support varies
DSDDo not use for the first DLNA test

If one track fails, test MP3 first. If MP3 works, discovery and control are fine, and the problem is likely format support.

Check in order:

  1. The streamer is on and in renderer mode.
  2. ECHO and streamer are on the same LAN.
  3. Click Refresh in ECHO.
  4. Set Windows network type to Private.
  5. Allow ECHO through Windows Firewall on private networks.
  6. Disable VPN.
  7. Disable AP/client/guest isolation on the router.
  8. Reboot the streamer.
  9. Reboot the router.
  10. Test with a phone DLNA controller app.

If the phone app cannot find the streamer either, fix the network or streamer first.

Common causes:

  • The renderer’s AVTransport control endpoint is unstable.
  • Another app controls the streamer.
  • The current format is unsupported.
  • Firewall blocks ECHO’s temporary media URL.
  • The streamer cannot reach the ECHO computer IP.
  • Wired and wireless devices are isolated.

Try:

  1. A normal MP3.
  2. Reboot the streamer.
  3. Close other controller apps.
  4. Allow ECHO through firewall.
  5. Put both devices on the same router.
  6. Use Ethernet for the streamer.

ECHO sends title, artist, album, duration, and artwork URL, but each renderer interprets metadata differently. Some devices do not show artwork, cache previous artwork, omit artist fields, or report position poorly.

Prioritize audio playback and control stability first.

PathBest for
DLNA / UPnPNetwork streamers, TVs, receivers, smart speakers
AirPlayApple ecosystem and AirPlay 1 / RAOP-compatible paths; AirPlay 2 is not supported
HQPlayerUpsampling, NAA, external HQPlayer chains
ECHO native outputHeadphones, DACs, sound cards connected to the computer

Use DLNA for ordinary network streamers. Read AirPlay Support Boundaries for AirPlay, and use HQPlayer for HQPlayer/NAA chains.

  1. ECHO computer and streamer on the same home router.
  2. Windows network type set to Private.
  3. Streamer in DLNA Renderer mode.
  4. ECHO plays an MP3.
  5. Open Connect.
  6. Click Refresh.
  7. Find the streamer.
  8. Click Connect.
  9. Audio comes from the streamer.

After this works, test FLAC, remote sources, artwork, seek, and high-bitrate files.