Repository navigation
Replies: 12 comments 6 replies
|
Thanks for the suggestion! I’ve actually thought about reuse too, but from a slightly different direction. My main goal with PlxNative has always been the user experience rather than building a particularly advanced playback engine. The playback/TV layer is actually the part I consider the most reliable already, and if the goal were a truly reusable media engine, mature projects like Kodi have years of work and testing across a huge range of devices behind them. What I had in mind instead was eventually making the native UI reusable across different backends — Plex, Jellyfin, Emby, etc. I think that’s where PlxNative could provide more value. For now, though, I’d like to get the Plex experience properly finished first, since that’s what I personally use and why I started the project. |
|
Thanks, that makes sense, and I think you are right about the direction. The Kodi point is fair: a portable playback engine is a solved problem, and the thing PlxNative has that nothing else does is the native UI. Reusing that across media servers is a better trade than splitting the engine out, and it is the version that would actually help people on older sets, whatever they run on the server side. One thing I would keep an eye on when you get to that seam is the data model. The UI currently speaks Plex types end to end, and an abstraction written after the fact around Plex alone tends to stay Plex-shaped underneath. If a second backend is a design requirement from day one, even if only on paper, the boundary ends up neutral. I would be glad to help define that boundary, and I Finishing the Plex experience first sounds right. The seam only matters once the app itself is where you want it. |
|
Yeah, good point about the data model. I’ll keep that in mind while finishing the Plex side — I definitely don’t want to make it unnecessarily Plex-shaped if the UI can eventually be reused. And if you end up taking the Jellyfin side when we get there, that’d be awesome :) |
|
Hi @GLinnik21 (and @gnacho, since you asked for the same thing) I wanted a Jellyfin client like this, so I had Claude (Claude Code) build the Jellyfin side you mentioned here, on top of PlxNative. To be upfront: the code is AI-written, I steered it, tested it on my TV and reviewed what went in. It's called FinNative: your UI and player, with a Jellyfin backend behind it. It's been running on my LG C1 for a few days and it's way smoother than the other Jellyfin apps on webOS. All credit to your work. The Jellyfin code lives in its own crate. Your Plex client just gets a small hook that sends calls to it, behind a feature flag that's off in PlxNative, so nothing changes on your side. It has its own name, app id and icon, and says "powered by PlxNative". A few fixes came out of it that I'd like to send back: pt-PT translation, emoji in titles, an HDR10+ stall and http direct play recovering from dropped connections. Same deal, AI-written with tests, and only tested on webOS 6. Since you said you'd like the UI to work with other backends eventually, would you be open to something like that hook upstream at some point? No rush, just curious if it fits what you had in mind. I'm planning to publish it under the GPL either way, but let me know if you'd want anything done differently. Thanks! Screenshots:
|
|
Small world :) Since this thread started with me asking for exactly this, a heads up on duplication: I already built the Jellyfin side as a fork - https://github.com/gnacho/butaca, synced up to upstream 0.8. And there is a newer independent client worth knowing: https://github.com/SchulzCode/WebOS-Jellyfin-Native (pure Rust, 0BSD, no LG SDK needed). Honest assessment of my own fork: next to other Jellyfin clients it is still missing a lot of options. If any of it is useful to you, take it - I would gladly hand the code over. One thing that will matter for FinNative specifically: plx-native's telemetry stack (Sentry, PostHog, consent screens, report IDs) comes along for the ride in a fork. Plex users may be used to that, but Jellyfin users will not accept it. Stripping all of it was the first real work in my fork and it was not a small diff, so it is better to decide before you publish. |
|
We should bring to this conversation @SchulzCode |
|
@GLinnik21 I've opened a PR with the backend hook I mentioned: a The code that actually uses the hook (FinNative) isn't public yet. I'll make it public soon so you can see exactly how the hook is used to integrate Jellyfin, which should make the review easier. I'll ping you when it's up. @gnacho this could help butaca too. With the hook upstream, it could plug into PlxNative as a backend instead of carrying the rebase work it does now. |
|
Hi @GLinnik21, @gnacho, @SchulzCode FinNative is now public: https://github.com/tiper/fin-native It's a Jellyfin client for LG webOS TVs, built as a fork of PlxNative. PlxNative's player, UI and performance work are what make it fast and smooth on the TV, so thank you, @GLinnik21 . Naming and credit: FinNative has its own name, icon and app id, and it says "powered by PlxNative". Your authorship stays in the history, and it remains GPL-3. If you'd like anything changed (credit wording, naming), tell me here and I'll do it. |
|
Hi, webosbrew dev here. |
|
Hey @mariotaku A unified player is an interesting idea, one that @GLinnik21 is open to, you can check his comment here, but Plex and Jellyfin are different servers with different backends, so it would need a good restructure. To be completely transparent, I'm fine with the submission being rejected, and even with shutting the project down, I can continue to develop it for myself, and continue to contribute to PlxNative any issues any issues I come across as I have done so far. It was never my intention to cause problems for PlxNative or its owner. I just wanted more people who appreciate PlxNative's work to have something similar for Jellyfin, which is why I kept the credits and authorship intact. Edit: For reference, you can see the credit to PlxNative on the splash screen: https://github.com/tiper/fin-native/blob/main/assets/splash-master.png |
|
Hey @tiper, @mariotaku, thanks for the discussion! First of all, @tiper, no worries at all! I have absolutely no problem with FinNative existing, quite the opposite :) The name and credits are perfectly fine with me, and I really appreciate the work you’ve put into it. I also get @mariotaku’s concern about forks falling behind. Ideally, I’d love to have both Plex and Jellyfin supported in PlxNative, and that’s actually what I’d like to tackle next once I’ve caught up with Plex feature parity. That’s also why I closed #827. The problem wasn’t Jellyfin support itself, but the approach of adding hooks throughout the existing Client. I’d much rather have a common data layer with separate implementations for each server. It’s a bigger change, but I think it’ll be much easier to maintain in the long run. That doesn’t mean anyone has to wait for me, though! I’m absolutely open to PRs and happy to discuss the architecture or review contributions if someone wants to work on it sooner. I can’t promise a timeline yet, and I don’t want to hold up anyone’s submissions or projects in the meantime. Hopefully, we can bring all this work together eventually. And @tiper, thanks again for contributing fixes back to PlxNative too! |
|
Hi @GLinnik21, @mariotaku, @tiper, @SchulzCode, @mariotaku, your concern is fair, and the answer is the code itself, Butaca's engine still comes from PlxNative, but everything above it is ours: no longer a fork, Plex backend gone, not hidden behind a flag. Most of that work cannot go upstream as it is, so I will not sell it as contribution. What I can share, I share at file level, as FinNative already does with Butaca's PlaybackInfo profile, credited in its notices. Meanwhile I use Butaca daily, so it stays alive. Why exclusive: I want the best native Jellyfin experience on these TVs, and that means features only a Jellyfin-only app can have, plugins, integrations, and a UI shaped around them that I already made. Not an argument against the shared data layer, just what I have until it exists. If that layer ever exists, I would rather build Butaca on top of it than keep maintaining my own copy of the player and the UI. Butaca and Plx-FinNative can't merge in code, but two fronts over one layer one day is not the same as two clients. And yes, several apps doing the same thing is confusing for users. Moonfin and Litefin didn't feel as fast as Butaca on my 2020 LG TV. That is why I keep at it, and hopefully it can serve other users too. |



Uh oh!
There was an error while loading. Please reload this page.
I run Jellyfin at home and my main set is a rooted LG on webOS 5.5, so I have been watching this project with some envy. Every Jellyfin client on webOS today is the web app in a box, and none of them will ever feel like PlxNative does on an old panel.
Reading the source, there are two very different projects living in one repo. One is the webOS engine: starfish.c with the video plane, dynlib.rs with the SONAME candidate dance, the player, ABR, the FFmpeg glue, HLS. That part is knowledge that exists nowhere else, since LG's player APIs are not in OSE. The other is the Plex front: plex/, pms.rs, the QR sign-in, and a UI that speaks Plex types end to end.
My question is about the seam between them. Would you be open, at some point, to extracting the engine so separate fronts can sit on top of it? Your Plex front stays as it is, first and canonical. Everything past it is upside: a Jellyfin front, maybe an Emby one, whatever people end up bringing. The Jellyfin crowd has never had a native client on these sets, and some of them would show up as users and contributors if that changed. I may end up building one of those fronts myself, but the case does not rest on that.
The shape I would argue for is the full split: the engine as its own versioned core, fronts as separate projects on top. I will not propose the half-way version, a trait under the UI while Plex types keep flowing beneath it; half measures tend to make the final split harder, not easier. And the pace of the last few months suggests the cut is within what this repo already does: the search rework alone touched more surface than an engine extraction would. If I ever experiment in this direction, I would much rather do it on top of your tree than beside it, so asking first seemed the right move.
All reactions