Your own files, and Apple Music
As many music servers as you have, and Apple Music alongside them, in one wall of covers. An album you own twice shows up once, with the copy you chose. The other stays reachable in its own library.
What each side does
Your own files
Lindale’s own audio engine, end to end: the file rather than a transcode, the output moved to the recording’s rate, gapless albums, and a readout that admits it when the path could not carry them. Everything further down this page is about this side.
Apple Music
Apple’s playback stays Apple’s, so your Lossless settings keep applying. What changes is the library around it: your own records first, no storefront, and albums Apple Music splits into four entries over a guest credit put back together as the one release they are. The whole story →
The one thing the two never do is share a queue, because two different players are doing the work. Browsing and searching span everything at once.
What it connects to
Today that means any server speaking OpenSubsonic, a documented interface built for third-party apps, so nothing here leans on one server’s private internals.
Navidrome, tested daily
It is what Lindale gets used against every evening, so it is where a problem shows up first. Navidrome also reports each file’s sample rate and depth, which is what makes the careful playback below possible.
Other servers
Only documented endpoints are used, so a compatible server should be fine. They have not all been tried. A server that keeps its file details to itself still plays. It just gives up the rate matching.
More than one
Add the machine at home and the one at your parents’ house. Look at them one at a time, or all at once, in which case the albums come back as one library rather than two lists. Switching does not stop what is playing.
Built like a record shelf
A wall of album covers
Albums arrive as a wall of artwork, sorted alphabetically or by what turned up most recently. Your playlists sit alongside them, and so do the internet radio stations you saved on the server, the one thing here that is not a file.
Box sets stay box sets
A four-disc set shows as four discs, numbered from one each time, instead of one run of sixty tracks. A details panel tells you the format, rate and depth.
Search one server or all of them
Pick the scope per search, and results come back grouped by where they came from. If one server is asleep, the others still answer.
Your play counts keep working
Finished tracks are reported back, so counts, last played and recently played stay right. Whether that travels on to Last.fm or ListenBrainz is your server’s business.
The part that took the longest
Your own files go through Lindale’s own audio engine, so the whole path from the file to the speaker sits under one roof.
The file, not a version of it
Lindale asks your server for the original file rather than a transcode, so what plays is what your server stores. Playing can start while the rest of it is still arriving, which is why a 24-bit album no longer means staring at a spinner.
The output follows the recording
Lindale reads what a track really is and asks the output device to match it. When the route can take that rate, nothing is resampled on the way. Over Bluetooth or AirPlay, or into an output stuck at one rate, it resamples and says so on screen. On iPhone and iPad the system has more of the final say than on the Mac.
No volume slider
There isn’t one, and that is the point. A slider in the app would mean touching every sample. Volume stays with your keyboard, your amplifier and the system.
Albums that run, run
The next track is lined up before the current one ends, so a live record or a mix plays through. Two tracks with genuinely different rates need the device reset between them, and that short pause is the honest cost of resampling neither.
It stops rather than improvise, too. Pull out the headphones, walk away from the speaker, take a call, and it pauses instead of carrying on out of the laptop at full volume.
What it plays
Lossless
FLAC, ALAC, WAV, AIFF, WavPack, Monkey’s Audio
Lossy
MP3, AAC, Ogg Vorbis, Opus
And the odd ones
DSD, Shorten, Speex, and the old tracker formats
Musepack and TrueAudio are the two that did not make it. If your library leans on either, this is not your app.
Setup, and being careful with your keys
HTTPS, and your own certificate
Your login crosses that connection, so a plain HTTP address is turned down and there is no setting to change it. Self-signed and private-CA certificates are fine: you get a sheet showing what could not be verified and who issued it, and accepting it trusts that one certificate from then on.
Where your details live
Passwords go in the Keychain, never into a file or a log, and never across the wire in plain form. Your list of servers follows you to your other devices through your own iCloud. With iCloud off it is simply local, and nothing breaks.
The cache looks after itself
Music you play is kept on disk up to a size you set, oldest out first. Nothing to manage, and clearing it costs you a download.
What it leaves to your server
Your server already has a web interface, and doing that job a second time badly helps nobody. So there is no:
- Editing tags, playlists or anything else on the server
- Stars and favourites
- Searching for single songs (search covers albums and artists)
- Rearranging the queue, or adding a track to play next
- Keeping an album for offline listening on purpose
- Equaliser, or anything else that processes the sound
Requirements
- macOS 26, iOS 26, iPadOS 26 or tvOS 26, or later
- A music server you can reach over HTTPS, anything speaking OpenSubsonic today
- For bit-perfect output, an output route whose rate can be set. Most wired ones can, and Bluetooth and AirPlay cannot
Lindale is not on the App Store yet, and it will be free when it gets there. Say hello if you want to hear when that happens.