Good points! Thank you for bringing them up:ġ. You might want to approach this through a stand-alone app instead (ideally, one that can be containerized). Even if they do, it won't be obvious to those who host Emby Server through Docker that they'll need to make modifications. I'm not certain that Emby plugins are allowed to create their own listeners. This sounds great! I used to use subsonic years ago, loved it!!Īs much as I love emby and have quite a strong dislike for Plex I fear there will be no acceptable alternative to Plexamp for quite some time, I "almost" installed it last night but got distracted!Īlso keep in mind that Subsonic servers default to port 4040. The plugin wiki docs are kind of old but they are a starting point, and could possibly increase Emby adoption by opening up Emby to the Subsonic app universe? I don't want to duplicate work although I can't find any mention of this being done anywhere yet.
#Plexamp android auto install#
Going this route, no separate server app is needed and plugin install would be relatively straightforward from the interface.
From what I've been able to glean so far this is possible, so I started on it this morning. I had the idea last night to create an Emby plugin that can in essence extend the Emby API by implementing a Subsonic API layer that "translates" those calls to Emby's native API. No app is perfect but, for me personally, DSub comes pretty damn close. I am an Android user and my favorite Subsonic API apps of course can't use Emby (need Emby app, Yatse, etc.). This is not to say I am not interested in Emby development! I would bet good money Subsonic eventually goes away and so will continue to pay attention. I found my way to Emby and am confident it can replace Subsonic, but until that day, I am happy using play:Sub. Indeed he is one of a very few users that will show up on Subsonic forums. It's developer remains active and responsive. play:Sub does all I want/need, that Subsonic API allows).
It took me less than a minute to realise how much better Plaxamp was the anything else I tried and there was really no point in continuing my own app when there was a solution that not only worked brilliantly, but looked good and was easy to use, the easy to use part was specifically for the other members of our household.Īt the time I was considering subsonic, I seem to recall that most of the apps that were in the iOS store were basically dead, many of which hadn't been updated for years.ĭid you try play:Sub? I've tried Plex's Plexamp and all the iOS apps for Subsonic. I tried the subsonic route, pretty much every application I tried on iOS were not great, and there is some weirdness with the API as well, I know this because after I realised the apps that were out there I started to write my own, I mimicked part of the Spotify UI and I had audio playback working before I remembered plexamp was a thing. So, even ignoring all of the *sonic clones, the API is widely supported. There are probably more, but these are the ones with which I'm most familiar as they were all ones I considered before migrating from Subsonic to Emby. In fact, there is no Navidrome app: it completely relies upon existing apps that support the Subsonic API.įunkwhale also supports the Subsonic API: So any app that works with Subsonic works with Navidrome, more or less. For example, Navidrome is completely separate from Subsonic-platform, developer, etc.-but it supports the Subsonic API: Sorry if I was not clear, but what I'm trying to say is that if Emby supported the Subsonic API-which is widely supported by dozens of apps-then any apps that work with the API will work with Emby, without the need for Emby devs to worry about creating/supporting a separate music app.