Skip to content
⌂ Home

AirPlay Sending and Receiving

Sending music from ECHO to a speaker and receiving audio from a phone or Mac into ECHO are separate paths. Receiver controls and protocol options depend on platform, channel, and installed build.

GoalEntry and scopeConfirmation
ECHO → speaker or receiverConnect AirPlay sending, maintained as AirPlay 1 / RAOP compatibilityConnect, check state, and hear actual output
Phone / Mac → ECHOAirPlay Receiver in Connect on builds containing that implementationEnable it and select ECHO from the sender’s audio-output picker
Experimental AirPlay 2 receivingReceiver protocol option requiring a compatible native componentVerify discovery, pairing, session setup, incoming audio, and local output separately

Experimental AirPlay 2 receiving does not establish AirPlay 2 speaker sending, multi-room synchronization, or compatibility with every Apple device. Older “AirPlay 1 only” guidance describes the sending path.

  1. Use the same LAN and enable an AirPlay 1 / RAOP-compatible receiver mode.
  2. Refresh Connect and select the device.
  3. Try an ordinary MP3 or FLAC; inspect connection state and actual output.
  4. A receiver requiring AirPlay 2 may not work through this sending path.

See Connect and LAN requirements.

  1. Open AirPlay Receiver in Connect; check receiver name and local output device.
  2. Start with the classic protocol. Test an experimental option separately when your build provides it.
  3. Choose ECHO from the iPhone, iPad, or Mac audio-output picker. Screen Mirroring is a different feature and is not implemented by this receiver.
  4. Start playback on the sender and check receiver state and desktop volume. Discovery alone does not prove audio reception.
  5. Stop sending and disable the receiver when finished if desired.

Sender application policies, OS versions, and content rights still apply. Receiving does not bypass accounts, DRM, or platform access controls, and is not a compatibility guarantee for every sender.

SymptomCheck
ECHO or speaker missingEnabled service, same subnet, guest isolation, VPN, firewall
Discovered but pairing/session failsProtocol, both versions, native component, displayed error; reconnect after changing protocol
Connected but silentSender playback, incoming audio, local output, volume
Receiver component unavailablePlatform/build packaging; see Windows startup
Need HomePod multi-room or screen mirroringOutside the currently established complete support scope

Reports should identify sending or receiving, ECHO version, sender OS, device, protocol, and whether failure occurs during discovery, pairing, or playback. For local WASAPI / ASIO problems, use Audio Output.