-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Jellyfin provider compatible with Emby #1325
Conversation
I'm not a big fan of this, we know for a fact that these 2 projects are deviating from eachother. Maybe just a little bit today but it will become more over time. Why not just ask @lokiberra if you may copy his work on the Jellyfin provider as a base for a new Emby provider ? |
I figured there was only one IF statement required here to make things work - they deviate and it stops working then it stops working but the improvements here make sense anyway as they follow the same api calls both jellyfin and emby use I'm not suggesting this is even advertised as working/supported 🤷♂️ I am trying to use the core emby api for a dedicated plugin and will get that submitted soon(ish). That would use emby python libraries, not jellyfins. |
Ah, so this is basically just a temporary patch which makes it compatible now and then at some point there will be a separate Emby provider ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, but I'll leave final review to @lokiberra as he's the author/maintainer of the Jellyfin provider.
Thanks!
Overall it looks good and I appreciate some of the cleanup. I haven't had a chance to test. Has it been tested with a Jellyfin server? I would want to make sure it isn't breaking Jellyfin functionality. If this is just temporary I'm fine with it. I agree with Marcel that Emby should be it's own provider, and it sounds like that is your plan. |
Sorry should have noted in the PR - but yep I've got both emby and jellyfin running so tested all was working |
I updated to the dev branch this morning to test #1338 and noticed a new error:
This seems to be an existing bug, but wondering if this PR is why i'm heading down that branch. Will try and look at it some more ASAP, but wanted to flag it. |
I am currently trying to write the Emby integration using their native API (but getting some strange import issues and my time is limited). In the process of looking at that i have taken a quick look at the JellyFin integration.
JellyFin having forked from an old version of Emby still functions very much the same so with a few tweaks i have been able to get the JellyFin plugin to work while maintaining all JellyFin capabilities.
&IncludeItemTypes=MusicArtists&IncludeItemTypes=MusicArtist
this should be&IncludeItemTypes=MusicArtists,MusicArtist
One thing i couldnt get working was the Friendly Name from the provider settings appearing in the track details. I couldnt reverse engineer where that is being created from to update the property. I wanted the Friendly Name from the "Music Providers" to appear in "Provider Details"