-
Notifications
You must be signed in to change notification settings - Fork 199
Subsonic
The Music app has supported also the Subsonic interface starting from version 0.11.0, and the support has gradually improved in the next versions. There are many Subsonic compatible client applications but not all of them work with the Music app or at all.
If the client app offers an option to use token/salt authentication, it should be disabled. The option may also be called something like "LDAP support" in which case it should be enabled (ownCloud Music does not support token/salt authentication and neither does the real Subsonic server in case LDAP is being used).
This is a list of Subsonic clients which have been tested to be compatible with the Music app v0.14.1:
- Subsonic Music Streamer (Android)
- DSub (Android) (*)
- Audinaut (Android) (**)
- UltraSonic (Android) (***)
- Supersonic (Windows)
- Clementine (Multi-platform, tested on Windows)
- Soundwaves (iOS) (****)
- play:Sub (iOS)
- SubMusic (Garmin watch) (*****)
(*) Starting from the DSub version 5.5.1, there is a server option "Authorization Basic headers" which must be unselected. Also versions 5.3.2 and older can be used as they never send those headers. Versions in the range [5.3.3, 5.5.0] cannot be used, unless you apply a bit clumsy workaround. You can find version 5.0.3 from F-Droid, and all versions from github.
(**) Works starting from the version 0.5.0. The token/salt authentication should be disabled from the server settings of Audinaut.
(***) Not compatible with Music app versions older than 0.14.1. The option "Enable support for LDAP users" must be ticked in the server settings.
(****) The app has problems playing tracks in FLAC format.
(*****) The app can use both Subsonic and Ampache APIs. Using Ampache API is recommended, but it requires Music app v0.15.1 or higher.