Connect Page In Detail

Connect is ECHO’s unified entry for network casting: send the currently selected or playing track to a LAN DLNA Media Renderer or AirPlay 1 receiver.

Connect = where sound is produced. Remote library (WebDAV / Jellyfin) = where files are read. Independent. See Remote sources.

Overview: Connect frontend playback devices. Network prerequisites: LAN and firewall.

Connect scope

ECHO provides	ECHO does not
Discover LAN Renderers / AirPlay devices	Configure your router or streamer firmware
Reachable audio URL for current track (DLNA)	Treat NAS as playable Renderer automatically
Play / pause / stop / seek / volume control	Guarantee full UPnP optional features on all devices
AirPlay 1 / RAOP compatible send	AirPlay 2 multi-room, HomePod-specific behavior

UI and state

Typical Connect page elements:

Element	Description
Device list	Discovered DLNA Renderers and AirPlay devices
Refresh	Re-run LAN discovery
Device card	Name, protocol (DLNA / AirPlay, etc.)
Connect / Recast	Establish or rebuild cast session
Disconnect	End cast; restore local path control
Status bar	Connection state, errors

When buttons are disabled (grey)

No track selected or playing (ECHO does not cast empty metadata).
Target offline or operation unsupported.
Discovery failed — no valid devices in list.

Prerequisites

ECHO host and target on same LAN segment (LAN and firewall).
Target has Media Renderer (DLNA) or AirPlay receive (AirPlay 1 compatible).
Windows private network; firewall allows ECHO on private networks.
First test: VPN off; EQ, ReplayGain, speed change, exclusive output off.
Select playable MP3 or FLAC; local System output verified recommended.

DLNA cast flow

Select track → Connect → Refresh → Pick DLNA device → Connect → Renderer pulls URL

Play or select a track in ECHO.
Open Connect.
Refresh; wait for list.
Confirm protocol DLNA / UPnP.
Connect.
On success ECHO attempts to pause local playback; sound from Renderer.
Control play, pause, seek, volume from Connect or player.
After track change, use Recast if state desyncs.

Internal behavior

Local file:

Local file → ECHO HTTP service → Renderer reads URL → Renderer plays

Remote library file:

Remote URL → ECHO proxy / forward or transcode → Renderer reads ECHO URL → Renderer plays

Temporary URL example:

http://192.168.x.x:<port>/connect/audio/...

Renderer must reach this URL. See DLNA guide.

Format recommendations (first test)

Format	First test
MP3	Preferred
FLAC	Second step
WAV	Good compatibility, large files
M4A / AAC	Renderer-dependent
OGG / Opus	High variance
DSD	Not for first DLNA test

Control capability variance

Not all Renderers support full play / pause / stop / seek / volume / position reporting. UPnP implementation differences — not necessarily ECHO-only faults.

AirPlay 1 cast flow

Select track → Connect → Refresh → Pick AirPlay device → Connect → Receiver plays

ECHO supports AirPlay 1 / RAOP only, not AirPlay 2. AirPlay 2–only hardware may not appear or may be unstable. See AirPlay support boundaries.

Do not mix AirPlay issues with WASAPI / ASIO / DSD. Local silence → Local output.

DLNA vs AirPlay

	DLNA	AirPlay 1
Typical targets	Streamers, DLNA receivers, some TVs	AirPlay 1 speakers / receivers
ECHO doc depth	Formats, URL, stepwise troubleshooting	Support boundary list
Empty list	Renderer mode, multicast, firewall	AirPlay 2–only, LAN isolation
Both supported	Verify DLNA first	Fallback

Path switching after cast

Action	Expected
Disconnect in Connect	Cast ends; local output available
Close ECHO	Session ends; Renderer behavior device-dependent
PC still audible	Verify Connect shows connected; see FAQ · PC still audible

Failure entry points

Symptom	Primary doc
Empty device list	LAN and firewall · DLNA · not found
Found but connect fails	DLNA · connect fails
Connected, renderer silent	FAQ · DLNA · stutter
AirPlay-specific	AirPlay boundaries

Topic	Doc
Full DLNA guide	DLNA / streamer guide
AirPlay boundaries	AirPlay support boundaries
Room scenarios	Typical scenarios
Network	LAN and firewall