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 v1.3.1:

• Subsonic Music Streamer (Android)
• DSub (Android) [1]
• Audinaut (Android) [2]
• UltraSonic (Android) [3]
• Substreamer (Android) [4]
• Airsonic Player (Android) [5]
• Supersonic (Windows)
• Clementine (Windows/Linux/MaxOS, tested on Windows)
• Strawberry Music Player (Windows/Linux/MaxOS, tested on Windows)
• Soundwaves (iOS)
• play:Sub (iOS)
• SubMusic (Garmin watch) [5]
• Jamstash (HTML5) [6]

[1] 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.

[2] Works starting from the version 0.5.0. The token/salt authentication should be disabled from the server settings of Audinaut.

[3] 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.

[4] Substreamer version 5.0.27 has been tested to work while some older versions were not compatible. The option "Use Legacy Authentication" must be enabled when setting up the server connection.

[5] Requires Music v1.3.1 or newer

[6] The app can use both Subsonic and Ampache APIs. Using Ampache API is recommended, but it requires Music app v0.15.1 or higher.

[7] With Music app versions prior to 1.0.2, you need to change the Protocol to json in the Jamstash settings for the music playback and album art loading to work. If you experience an infinite redirection problem when trying to use Jamstash directly from https://jamstash.com or by using the Chrome plugin, then it will probably help to install it on the same server with your cloud. Probably this could be solved by tuning the HTTP server settings, too.