5 min read

1-bit 1.5, the one with Chord 2Go support

1-bit 1.5 is on the App Store. Play bit-exact to a Chord 2Go or any DLNA renderer on your network, back up your playlists to your own bridge, and keep a private listening history. Bridge 0.1.5 ships alongside with a DLNA MediaServer. Same DSD over DoP, no transcoding.

Updated

1-bit 1.5 is on the App Store. Same URL, new build, free update.

The easter-egg card in Settings → About keeps the multi-line habit it picked up in 1.4. This release’s verse is “One hundred three commits are past, / The music breathes, unfettered, vast. / Pure bit-perfect sound takes flight, / To fill the room with deep delight. / Let every note and chord revive, / In beautiful version 1.5.” That fifth line is doing double duty — the headline feature is playing to a Chord 2Go.

What’s new

Play to a Chord 2Go (and other DLNA renderers)Cast a track to a DLNA / UPnP renderer on your network — the Chord 2Go is the target I built this for, and generic renderers (mconnect, BubbleUPnP, Linn Kazoo) work too. Pick it from the Now Playing output picker. The app hands the renderer the track metadata and a link to the file on your own bridge; the renderer fetches and plays the audio itself, bit-exact, over your LAN. Nothing routes through a server I operate.
Playlist backup to your bridgeOff by default, per bridge. The playlists you build in the app can now back up to the bridge you run, so they survive a reinstall or a re-pair. They go only to your bridge — never to me, never to a third party. Tracks that come from another bridge or from local / SMB storage stay as opaque references.
Listening history to your bridgeOff by default, per bridge. Turn it on and the app reports each play — track, when, how long, codec, and where available the output device and DAC sample rate — to your own bridge. It’s your data: it lives on the bridge host, shows up on the admin console’s new Data page (histograms, most-played, export), and the bridge never forwards it anywhere.
On-device diagnosticsA small daily performance summary — CPU/energy, memory, playback runtime — pulled from Apple’s on-device MetricKit and surfaced in the in-app diagnostics screen. It never leaves your phone. Handy when something feels off and you want to see whether the app is the culprit.

A note on the Chord 2Go path

DLNA casting is a bridge feature, not a standalone one. The renderer pulls the audio straight from your bridge over the LAN, so the track has to live on a bridge — an SMB share or the on-device library can’t be cast this way, because the renderer needs a URL to fetch from. And one thing worth saying plainly: UPnP has no authentication. While the bridge’s DLNA MediaServer is on, any device on your LAN can browse and stream that library. So it’s off by default, it only ever binds your local network (never a public IP), and a public-mode bridge refuses to start it at all. Turn it on for a network you trust, and leave it off on shared Wi-Fi.

And on the bridge side

Bridge 0.1.5 ships alongside — 45 commits since 0.1.4, iOS wire protocol unchanged at v1.

The big one is the DLNA / UPnP MediaServer that makes the Chord 2Go path possible: an All Tracks list plus a Folders hierarchy with free-text search, bit-exact audio, cached upscale variants surfaced as alternate streams. Then the two storage features that land on the bridge: per-device playlist backup and an opt-in listening history, both viewable on the admin console’s new Data page with JSON / CSV export. Plus a public-mode pairing-QR fix (the QR now carries the served Let’s Encrypt cert fingerprint and the public dial URL, so phone pairing no longer trips the TLS pin), a sudo bridge update fix for FUSE-mounted libraries, and honest variant accounting across the admin views. Full release notes on the bridge releases page.

The data we collect is still none

Two of the new features move your data off the phone — but only to a server you run, and only if you turn them on. Playlist backup and listening history are off by default and go solely to your own bridge. DLNA playback stays on your LAN. When backup or history is enabled, the app mints a random per-device identifier (stored in the Keychain, not linked to your Apple ID or any ad identifier) so the bridge can keep each device’s backups separate. The MetricKit summary never leaves the device. No new third-party services, and aside from the multicast capability that SSDP discovery needs, no new permissions. The privacy policy spells all of it out, and the App Store nutrition label stays “Data Not Collected”.

Same audio path

No transcoding. No resampling. No mixer in the path. DSD goes out as DoP to your USB DAC; PCM goes out at the file’s native sample rate; and when you cast to a DLNA renderer, the renderer fetches the original bytes from your bridge and does its own job. The phone moves bytes and metadata; the hardware does the rest. How DSD playback is handled →

The unromantic version

If you have 1-bit installed: open the App Store and tap update. Your SMB shares, bridge pairings, and Settings carry over. DLNA casting, playlist backup, and listening history are all off by default — you turn them on if and when you want them. To play to a Chord 2Go, enable the DLNA MediaServer on your bridge first, then pick the renderer from Now Playing.

If you’re new: it’s a free download, iPhone or iPad, iOS 26.1 or later. Bring a NAS or a bridge, a USB DAC for DSD (or a Chord 2Go on the network), and music you actually like.

Related posts

Comments