Support
Write to crb@createbetter.design. One person reads that address and answers it. Tell us which server and which playback device you use — with UPnP, those two names explain most of what happens.
No server appears
The app finds servers by asking the network who is there. Three things stop that question from arriving:
- Local network access is off. iOS asks once, on first launch, and remembers a no. Settings → Song in the Air → Local Network.
- The iPhone is on a different network than the server — a guest network, a repeater with its own subnet, or a VPN that captures all traffic. Turn the VPN off for a moment and see whether the server appears.
- The router blocks multicast. Some mesh systems suppress it between devices; the setting is usually called "AP isolation" or "client isolation".
Playback stops when the screen locks
It should not, and it does not need a setting. If it does happen, iOS has revoked the app's audio session — usually after another app took over audio, or after Low Power Mode intervened. Open the app once and press play again. If it recurs reproducibly, please write; that is a bug we want to see, not a limitation.
Album art is missing
The app shows what the server delivers. If the server has no image, it asks MusicBrainz and the Cover Art Archive — an open, non-commercial music database. Their coverage is good but not complete, and for very small labels or self-released records it often finds nothing. Cover art embedded in the file itself always wins.
It says "unverified" instead of bit-perfect
That label is honest rather than decorative. It means the app could not confirm the format — usually because the server reports no bitrate. The app then reads the first bytes of the file itself and derives the format from them. If that fails too, it says so rather than claiming something it has not measured.
With AirPlay, the label is not "unverified" but a clear no: AirPlay resamples. That is a property of the protocol, not of this app.
The queue does not continue on its own
UPnP has no way to hand a playlist to a playback device — the protocol offers exactly one action for the next track. The app therefore holds the queue itself and passes the next track along in good time. That is why it keeps running in the background while music plays. If the app is force-quit from the app switcher, the current track finishes and then it goes quiet.
Something else
The questions on the home page cover the ground more broadly. Anything not answered there belongs in an email — including the ones that begin "this is probably a stupid question". Those are usually the ones that reveal something we described badly.
Reaching us
CreateBetter.Design — owner: Christian Radmann-BenderIm Holzwinkel 6
53819 Neunkirchen-Seelscheid
Germany
Email: crb@createbetter.design
Written in German or English, whichever suits you.