AirPlay Support Boundaries
This page defines ECHO’s AirPlay 1 / RAOP support scope and AirPlay 2 non-support. For routing among local output, DLNA, and AirPlay, see Connect frontend playback devices.
Short Version
Section titled “Short Version”ECHO currently sends audio the older AirPlay 1 way. Technical notes often call this RAOP: send sound to a speaker or receiver that still accepts AirPlay 1.
ECHO does not currently support AirPlay 2. Connecting to a device on your LAN does not mean multi-room, HomePod-only behavior, or AirPlay 2.
If your device only accepts AirPlay 2, or you need HomePod multi-room or Apple TV sync, that is outside current ECHO support.
What ECHO Supports
Section titled “What ECHO Supports”The actual entry point is the in-app Connect page.
Treat the current boundary this way:
- Send audio to AirPlay 1-compatible devices on the same LAN.
- Try a normal song, stable Wi-Fi, and default audio settings first. Do not stack EQ or exclusive output on the first test.
- Discovery and connection also depend on firewalls, the router, and the receiving device.
- ECHO will try to surface connection state and errors, but not every Apple or third-party device is guaranteed to work.
AirPlay is not Bluetooth and it is not local exclusive output. Do not troubleshoot AirPlay as a WASAPI Exclusive, ASIO, DSD, or Bluetooth-codec issue.
AirPlay 2 Is Not Supported
Section titled “AirPlay 2 Is Not Supported”Do not treat these as supported:
- AirPlay 2 multi-room synchronization.
- HomePod / Apple TV AirPlay 2-specific behavior.
- AirPlay 2-level pairing, encryption, session recovery, and device coordination.
- Screen mirroring, video mirroring, or system-level casting.
- Apple Music, FairPlay, DRM, paid-content, or access-control bypass behavior.
- Using ECHO as a full replacement for an official Apple AirPlay 2 device.
AirPlay-related logs or UI labels do not mean AirPlay 2 is complete. The public support boundary remains AirPlay 1 / RAOP compatibility.
Recommended Test Flow
Section titled “Recommended Test Flow”For a first AirPlay test:
- Put the ECHO computer and AirPlay device on the same home LAN.
- Disable VPNs, proxies, guest networks, and AP isolation.
- Set Windows network type to Private.
- Allow ECHO / Electron / Node through Windows Firewall on private networks.
- Start with a normal MP3 or FLAC.
- Disable EQ, ReplayGain, speed changes, resampling, and other advanced processing.
- Confirm basic playback first, then test AirPlay.
If the same device is unstable in other apps too, check firmware, router behavior, Apple device OS version, and the LAN before treating it as an ECHO issue.
Can ECHO guarantee every iPhone, iPad, Mac, or Apple TV works?
Section titled “Can ECHO guarantee every iPhone, iPad, Mac, or Apple TV works?”No. Apple OS versions, device models, network setup, protocol compatibility, and third-party implementations all matter. ECHO maintains only the current AirPlay 1 / RAOP compatibility boundary.
Why does another app connect when ECHO does not?
Section titled “Why does another app connect when ECHO does not?”Some apps use vendor-private behavior, system-level capabilities, or AirPlay 2 features. ECHO will not chase closed private behavior with high-risk compatibility work.
What should I check first if AirPlay has no sound?
Section titled “What should I check first if AirPlay has no sound?”Check networking and protocol boundaries before changing exclusive output:
- Confirm both devices are on the same subnet.
- Disable VPN / proxy.
- Allow firewall access.
- Restart the AirPlay-related devices.
- Try a normal MP3.
- Return ECHO to default audio settings.
If it still fails, include the ECHO version, Windows version, sender device and OS version, network environment, screenshots, and logs.