+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Development (https://forum.jellyfin.org/f-development)
+--- Forum: Client Development (https://forum.jellyfin.org/f-client-development)
+---- Forum: Smart TV Development (https://forum.jellyfin.org/f-smart-tv-development)
+---- Thread: [WebOS client] maybe a feature request!? (/t-webos-client-maybe-a-feature-request)
[WebOS client] maybe a feature request!? - marmaladeflipper - 2024-03-21
Hey.
So, this is kind of a weird post...
At first, I thought I need troubleshooting advice.
But after some experimenting and making my assumptions, it turned more into a (potential) feature request for the WebOS client.
Since it's not (yet) a full feature request, but definitely concernes the WebOS client, I hope it's OK I posted this here.
Otherwise, feel free to move this topic wherever you see fit.
Let's start with my original problem:
Jellyfin won't direct play HEVC videos on my LG Smart TV. At least not via the WebOS client.
But when I play the exact same files on the same TV via minidlna, they work perfectly.
I.e. my TV is definitely capable of playing HEVC...
So I started digging:
Sifting through Jellyfin's logs, I noticed that the "LG Smart TV" DLNA profile was assigned to my TV.
Hence I checked the profile and found that HEVC was not set for direct play.
I added a custom DLNA profile with direct play of HEVC, restarted Jellyfin and the TV (for good measure), and tested the files again.
NOPE. No direct play.
Then I checked the logs again: the custom DLNA profile was correctly assigned...
So I activated direct access to Jellyfin's DLNA server.
On the TV, I navigated to one of the files, and started it.
It played.
Went back to the logs and found:
Code:
StreamBuilder.BuildVideoItem( Profile="CustomLG"However, with the Jellyfin's WebOS Client I got:
Code:
StreamBuilder.BuildVideoItem( Profile="Anonymous Profile"That's how I came to the following questions/assumptions:
Would direct playback work, if I could force the WebOS client to use the "CustomLG" profile instead of "Anonymous Profile"?!
Or (what I assume, is actually going on), is it that DLNA uses a totally different software player than the WebOS client?! Consequently, resulting in different sets of supported codecs.
And, based on the latter assumption, a potential feature request:
Wouldn't it be possible to make use of the DLNA player's larger set of supported codecs by making the WebOS client cast via DLNA to the TV?!
If so, this could open up "a new world of files" for all the people with capable clients but low-power servers (e.g. raspis).
Hope my process and reasoning are comprehensible.
I'm not a dev or programmer, just someone who dabbles and has no actual idea of how JF works internally...
Don't think it matters much, but I'm currently using these JF versions:
Server 10.8.13; bare metal on Debian 12
WebOS Client 1.1.0
OK, what do you think?! Am I totally wrong?! Good idea? Bad idea?
I honestly can't really judge this...
RE: [WebOS client] maybe a feature request!? - TheDreadPirate - 2024-03-21
DLNA uses a completely different player than the Jellyfin client. IIRC, all WebOS apps are essentially browser apps. Which means that the Jellyfin client is dependent on the web player built into the "browser" of WebOS. Generally, that means HEVC is not going to direct play.
RE: [WebOS client] maybe a feature request!? - Pedro - 2024-05-13
Hello and thank you for this great software.
I'm a former Plex user and I was put out from it because of the increasingly push to have an account and my server registered.
Regarding the point in this chat, I could play large files with Plex with the Plex WebOS app. So there must be a way to pass the files to the TV to play and not to behave as a browser but as a media player.