Working on compatibility with Emby #1448
Replies: 2 comments
-
|
It's live now if anyone wants to take a look. Hell, I'd say enjoy it while it functions; in my experience with movies and TV shows, it's a perfect experience. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Supporting Emby isn't a goal of Wholphin, but it's neat that you managed to get a middleware/proxy working for your use case. So good luck! But this is outside of the scope of Wholphin. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
So, I'm going back and forth with an AI (Yeah I know, and I don't care) and slowly but surely it's resulting in a proxy translation layer that sits between my Emby server and Wholphin to allow them to talk to each other. Almost everything works great, you'd never really be able to tell I have the app connected to an Emby server.
The AI across multiple platforms has hit a brick wall though, there's a few issues it can't seem to squash and I don't know if it's because of inherent incompatibilities that a proxy can't fix, or just a lack of documentation for the AI. Either way I don't really know anything and I'm not afraid to admit that, anybody want to take a crack at finishing it?
I'm burnt out on it and I still have to strip it of personal information before sharing, but if someone's interested I'll get right on that.
Beta Was this translation helpful? Give feedback.
All reactions