AshranPewter 6 Posted November 19, 2024 Posted November 19, 2024 Apparently this is supported by Jellyfin through Remuxing server side. Is this something that might be supported in the near future? https://old.reddit.com/r/LGOLED/comments/1f1bjba/dolby_vidion_now_supported_on_mkv_with_jellyfin/ Thanks! AshranPewter
rbjtech 5284 Posted November 19, 2024 Posted November 19, 2024 This is only relevant for the LG Emby Client - as it's the LG that has a limitation on using MKV files. All the other Emby TV Clients don't have an issue playing DV via MKV. But yes, it would be nice for the LG Emby Client to recognise this condition and remux the MKV on the fly (to MP4) and then DV would direct play.
yocker 1248 Posted November 19, 2024 Posted November 19, 2024 Using an external player might be a temporary answer. Problem is that timestamps do not get saved when using one.
AshranPewter 6 Posted November 19, 2024 Author Posted November 19, 2024 1 hour ago, rbjtech said: This is only relevant for the LG Emby Client - as it's the LG that has a limitation on using MKV files. All the other Emby TV Clients don't have an issue playing DV via MKV. But yes, it would be nice for the LG Emby Client to recognise this condition and remux the MKV on the fly (to MP4) and then DV would direct play. Hmm I'm using the Android TV client on Shield (and also tried the built-in Google TV for my TV) and when I check the stats it shows as hdr10/dv in emby, but the actual stream itself is hdr10 when I check the video feed information from the TV's menu. Is there a setting i'm missing? It works fine on Plex on Shield, Plex on the Google TV, and also local files.
AshranPewter 6 Posted November 19, 2024 Author Posted November 19, 2024 Thought I'd share the versions in case it helps and this isn't intended behavior. Emby for Shield - 2.1.22g Emby for Sony Google TV - 2.1.22g Emby Server (Docker) - 4.8.10.0
Lessaj 467 Posted November 19, 2024 Posted November 19, 2024 (edited) How does trying to play the same on Emby for Android compare? I have no problem with DV HDR hybrid playback of either 7.6 or 8.1 on my shield using the standard Android app. EDIT: My LG TV also has a popup in the top right corner of either Dolby Vision or HDR depending on the content being played. I have once or twice when auto playing the next episode had it fall back to HDR but a stop/start of the episode reported DV again. Edited November 19, 2024 by Lessaj
rbjtech 5284 Posted November 19, 2024 Posted November 19, 2024 (edited) 4 minutes ago, Lessaj said: How does trying to play the same on Emby for Android compare? I have no problem with DV HDR hybrid playback of either 7.6 or 8.1 on my shield using the standard Android app. Likewise - AndroidTV or Android clients both play DV just fine from an MKV. edit - but of course AndroidTV for Emby is substantially faster, plays direct via SMB and doesn't blind me from the overly white highlights ... @Neminem 3 hours ago, AshranPewter said: Apparently this is supported by Jellyfin through Remuxing server side. Is this something that might be supported in the near future? https://old.reddit.com/r/LGOLED/comments/1f1bjba/dolby_vidion_now_supported_on_mkv_with_jellyfin/ Thanks! AshranPewter I'm referring to the URL - this just applies to LG TV's as they don't support DV via MKV. Edited November 19, 2024 by rbjtech 1
rbjtech 5284 Posted November 19, 2024 Posted November 19, 2024 9 minutes ago, AshranPewter said: Thought I'd share the versions in case it helps and this isn't intended behavior. Emby for Shield - 2.1.22g Emby for Sony Google TV - 2.1.22g Emby Server (Docker) - 4.8.10.0 Versions look good - is this via an MKV ? A mediainfo of the file would add info.
AshranPewter 6 Posted November 19, 2024 Author Posted November 19, 2024 ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L6.1@High HDR format : Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible Codec ID : V_MPEGH/ISO/HEVC Duration : 2 h 43 min Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 23.976 (24000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 10 bits Default : Yes Forced : No Color range : Limited Color primaries : BT.2020 Transfer characteristics : PQ Matrix coefficients : BT.2020 non-constant Mastering display color primaries : BT.2020 Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2 Maximum Content Light Level : 1000 cd/m2 Maximum Frame-Average Light Level : 400 cd/m2 Sure thing this is I think what you're looking for? I wanted to ensure it wasn't the profile, but looking now maybe 8.1 is the issue, but seems weird since other players are handling it fine.
rbjtech 5284 Posted November 19, 2024 Posted November 19, 2024 (edited) 10 minutes ago, AshranPewter said: ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L6.1@High HDR format : Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible Codec ID : V_MPEGH/ISO/HEVC Duration : 2 h 43 min Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 23.976 (24000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 10 bits Default : Yes Forced : No Color range : Limited Color primaries : BT.2020 Transfer characteristics : PQ Matrix coefficients : BT.2020 non-constant Mastering display color primaries : BT.2020 Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2 Maximum Content Light Level : 1000 cd/m2 Maximum Frame-Average Light Level : 400 cd/m2 Sure thing this is I think what you're looking for? I wanted to ensure it wasn't the profile, but looking now maybe 8.1 is the issue, but seems weird since other players are handling it fine. yes - so this is a main10/L6.1 - all of my 4K remux's are main 10/L5.1 this is the HEVC level - 6.1 is simply not required for 4K 24fps (it's designed for 8K video) - so I think that may be the issue here. @ebrCan likely confirm if Exo supports this. Edited November 19, 2024 by rbjtech
Lessaj 467 Posted November 19, 2024 Posted November 19, 2024 I found a couple films I have are Main 10@L6.1@High and Dolby Vision played just fine on my LG with my Shield. One of them is HDR10 compatible, the other is HDR10+ profile B compatible. Format/Info : High Efficiency Video Coding Format profile : Main 10@L6.1@High HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible Format/Info : High Efficiency Video Coding Format profile : Main 10@L6.1@High HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
AshranPewter 6 Posted November 20, 2024 Author Posted November 20, 2024 Any clue what might be causing the issue with this file? I did try another file and it worked just fine looks like Main 10@L5.1@High on that one. The file plays fine on other players, could it just be that the file list of what can play needs to be updated or I need some setting changed?
rbjtech 5284 Posted November 20, 2024 Posted November 20, 2024 11 hours ago, Lessaj said: I found a couple films I have are Main 10@L6.1@High and Dolby Vision played just fine on my LG with my Shield. One of them is HDR10 compatible, the other is HDR10+ profile B compatible. Format/Info : High Efficiency Video Coding Format profile : Main 10@L6.1@High HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible Format/Info : High Efficiency Video Coding Format profile : Main 10@L6.1@High HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible So the OP has a Shield but a Sony TV with Android as an OS - if that doesn't support the L6.1 HEVC passthrough - then it will have an issue. That's the only thing I can think of - the Shield just does the passthrough - so I don't think it really cares but having not ever used L6.1 - I'm not totally sure on that. (8K is a way off for me lol ..)
rbjtech 5284 Posted November 20, 2024 Posted November 20, 2024 2 hours ago, AshranPewter said: Any clue what might be causing the issue with this file? I did try another file and it worked just fine looks like Main 10@L5.1@High on that one. The file plays fine on other players, could it just be that the file list of what can play needs to be updated or I need some setting changed? As explained above - it's because that file is using the hevc profile of an 8K file - but it's a 4K file @ standard fps. Whoever created the file didn't know what they were doing - you set the lowest profile for the data it contains, not the highest - otherwise you run into these incompatibility issues. Yes some players will modify this setting and play it back, but Exo is just using the data it has been given. In short - the file needs to be replaced.
yocker 1248 Posted November 20, 2024 Posted November 20, 2024 54 minutes ago, rbjtech said: So the OP has a Shield but a Sony TV with Android as an OS - if that doesn't support the L6.1 HEVC passthrough - then it will have an issue. That's the only thing I can think of - the Shield just does the passthrough - so I don't think it really cares but having not ever used L6.1 - I'm not totally sure on that. (8K is a way off for me lol ..) Sony TVs needs a dolby vision mode activated on the HDMI port used. Can this have anything to do with it?
rbjtech 5284 Posted November 20, 2024 Posted November 20, 2024 3 minutes ago, yocker said: Sony TVs needs a dolby vision mode activated on the HDMI port used. Can this have anything to do with it? DV mode is being activated via the Shield HDMI connection for L5.1 - so that's working just fine. I think it's simply that L6.1 is not supported on the TV - but other than a hunch, I have no way to confirm this .. 1
Lessaj 467 Posted November 20, 2024 Posted November 20, 2024 5 hours ago, rbjtech said: So the OP has a Shield but a Sony TV with Android as an OS - if that doesn't support the L6.1 HEVC passthrough - then it will have an issue. That's the only thing I can think of - the Shield just does the passthrough - so I don't think it really cares but having not ever used L6.1 - I'm not totally sure on that. (8K is a way off for me lol ..) I guess I was confirming that Exo supports it at least. It is possible that that's the issue in this case since a L5.1 worked fine for the OP. 1
AshranPewter 6 Posted November 20, 2024 Author Posted November 20, 2024 I just want to be clear about this though. I have installed Emby on both my TV's OS and Shield and it reverts down to HDR10 in both situations. If I use Plex, it plays direct on both TV's OS version of the app and the Shield app. Locally using Nova, it plays both with DV. This is all confirmed using the "detailed signal information" on my TV. So I don't think there's an issue with the tv not supporting passthrough in this case. Also I hadn't noticed until just now, but emby seems to be Transcoding it server side and the stats in the app are showing "Converting to a compatible video level"
ebr 16184 Posted November 20, 2024 Posted November 20, 2024 22 minutes ago, AshranPewter said: the stats in the app are showing "Converting to a compatible video level" Hi. Yes, that's because of this: 5 hours ago, rbjtech said: As explained above - it's because that file is using the hevc profile of an 8K file - but it's a 4K file @ standard fps. Whoever created the file didn't know what they were doing We are taking the information given to us at face value - which indicate your TV should not support the video.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now