What it plays, and what it plays on.
The useful version of a compatibility page is the one that tells you what does not work yet as plainly as what does. Here is both, so nobody installs yamsap and finds out afterwards.
Where the music comes out.
AirPlay speakers and receivers
Found on the network on their own. Yamsap picks the newer or the older AirPlay protocol for each speaker without being told which. Cover art, volume and the buttons on the speaker itself all work.
A Mac, through the desktop app
The desktop app turns a Mac into a zone and plays straight out to whatever it is plugged into, including a USB DAC.
iPhone and iPad
The app plays to the device in your hand, at home or over remote access.
CarPlay
Recently played and recently added as artwork on the dash, the rest one tap down.
DLNA renderers
Network streamers and receivers that speak DLNA, WiiM among them. Found on their own, the same as AirPlay speakers, with the title and cover art on the device's own screen and the buttons on it wired back to the zone.
Any browser
Every browser that opens the library offers itself as a zone. That is how a Linux desktop, a Windows laptop or a machine you are borrowing for the afternoon plays, with nothing to install.
Zones can be grouped, and grouped rooms stay in sync. A speaker that needs more time to buffer than the laptop next to it is accounted for rather than left to drift. DLNA renderers are the exception and play on their own: DLNA gives a sender no clock to hold a group together, so a grouped one would drift with nothing to correct it.
What does not work yet.
Some of this is coming and some of it is not. Either way you should know before you spend an evening on it.
Sonos
Not yet. Sonos may answer the same DLNA the renderers above do, but none has been tested here.
Chromecast and Google speakers
Not yet.
HomePod, Apple TV, and AirPlay out of a Mac
Not yet. Apple's own receivers require a pairing handshake that third-party senders cannot complete. Third-party AirPlay speakers are fine.
AirPlay speaker groups
Not yet. Grouping a stereo pair inside a speaker's own app is not yet visible to yamsap. Grouping yamsap's own zones works today.
Windows, as the server
Not yet. The server runs on macOS and Linux.
A desktop app for Windows or Linux
Not yet. Those machines play through the browser, and the Mac app is what reaches a USB DAC directly.
If the speaker you care about is not named here, write and ask. The list of hardware yamsap has actually been tested against grows every month, and knowing what people are trying to drive is how we decide what to buy next.
Files and fidelity.
Audio leaves the server at the file’s own sample rate. Nothing is resampled down to make the network’s life easier, and nothing is upsampled to make a specification look better.
Where a zone cannot take the rate a file was made at, that zone alone is brought down to a rate it can take, by halving rather than by an arbitrary conversion. The other rooms carry on at full rate.
- Lossless
- FLAC, ALAC, WAV, AIFF
- Lossy
- MP3, AAC, Ogg Vorbis, Opus
- Depth
- Up to 24 bit
- Rates
- The file's own, per zone
- Caps
- Set per zone, when hardware needs it
- DSD
- Not yet
What the server needs.
One computer, awake when you want music. It does not have to be dedicated, it does not have to be new, and it does not have to stay on overnight unless you want the library reachable while you are out.
- macOS
- Apple silicon or Intel
- Linux
- amd64 or arm64
- Storage
- Your music, wherever it already lives
- Network
- Wired or wireless, one subnet
A machine that can already play the music can already run the server. How the pieces fit together.
Hear when yamsap is ready
Yamsap is $6.99 a month, or $5.99 paid yearly, after a 14 day trial. Builds for macOS, Linux and iOS are close. Join the waitlist and you’ll hear when yours is ready.
Check availability and join the waitlist