Sammy 794 Posted 6 hours ago Posted 6 hours ago I am not exactly sure if I should put this here or in the server sub thread. I use Emby for Windows server beta and generally keep it up-to-date every time there is a new update. I also use Google TV devices such as the ONN Google TV or a native Google TV app built into the TV when playing Dolby Vision files. Sometimes they fail completely or sometimes I get the green and purple hues. Other times they play fine. This seems to be file specific and occurs on TV's that don't natively support Dolby Vision. Is this due to encoding or an issue with transcoding or an issue with the playback device?
Solution ebr 16603 Posted 5 hours ago Solution Posted 5 hours ago Hi. The ones that work have an HDR fallback and the ones that don't work, don't. 1
Sammy 794 Posted 5 hours ago Author Posted 5 hours ago 30 minutes ago, ebr said: Hi. The ones that work have an HDR fallback and the ones that don't work, don't. So fallback is encoded in the mkv? It was a 43" TV in my bar so I just updated it to a Hisense TV that supports Dolby Vision. The 24" in the kitchen isn't worth the bother..
Lessaj 543 Posted 4 hours ago Posted 4 hours ago Provide mediainfo from one that works and one that doesn't, it will be apparent if it has an HDR fallback - the profile tells the story. 1
Sammy 794 Posted 1 hour ago Author Posted 1 hour ago 3 hours ago, Lessaj said: Provide mediainfo from one that works and one that doesn't, it will be apparent if it has an HDR fallback - the profile tells the story. I took a peak at the Media Info and see the difference in the video. One says HDR 10 Compatible and the other doesn't. I don't suppose Handbrake can reencode Dolby Vision to HDR 10. Not that it matters, I just went ahead and sprung for another TV in the bar and the kitchen TV isn't used to watch 4k stuff anyhow because who wants to watch much on a 24" screen anyhow..
Lessaj 543 Posted 1 hour ago Posted 1 hour ago 3 minutes ago, Sammy said: I took a peak at the Media Info and see the difference in the video. One says HDR 10 Compatible and the other doesn't. I don't suppose Handbrake can reencode Dolby Vision to HDR 10. Not that it matters, I just went ahead and sprung for another TV in the bar and the kitchen TV isn't used to watch 4k stuff anyhow because who wants to watch much on a 24" screen anyhow.. I am not sure that it can because I've never used it, might be able to generate one based on DV data though. I was referring to this for the profiles, for example this is a 7.6 with DV and HDR (typically bluray): Quote HDR format : Dolby Vision, Version 1.0, Profile 7.6, dvhe.07.06, BL+EL+RPU, no metadata compression, Blu-ray compatible / SMPTE ST 2094 App 4, Version HDR10+ Profile B, HDR10+ Profile B compatible Or an 8.1 (typically streaming): Quote HDR format : Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2094 App 4, Version HDR10+ Profile B, HDR10+ Profile B compatible Or 5, pure DV Quote HDR format : Dolby Vision, Version 1.0, Profile 5, dvhe.05.06, BL+RPU, no metadata compression
Sammy 794 Posted 55 minutes ago Author Posted 55 minutes ago This Plays: General Unique ID : 55506409233751984695444824153212061355 (0x29C22543BD41FF89BF1D657FC63406AB) Complete name : Z:\TV Series\Lucky (2026)\Season 1\S01E01 - No Shortcuts.mkv Format : Matroska Format version : Version 4 File size : 8.39 GiB Duration : 47 min 30 s Overall bit rate : 25.3 Mb/s Frame rate : 23.976 FPS Title : Lucky S01E01 No Shortcuts Writing application : mkvmerge 94.0 ('Initiate') 64-bit Writing library : libebml v1.4.5 + libmatroska v1.7.1 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L5@High HDR format : Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2094 App 4, Version HDR10+ Profile B, HDR10+ Profile B compatible Codec ID : V_MPEGH/ISO/HEVC Duration : 47 min 30 s Bit rate : 24.5 Mb/s Width : 3 840 pixels Height : 1 606 pixels Display aspect ratio : 2.39:1 Frame rate mode : Constant Frame rate : 23.976 (24000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 (Type 2) Bit depth : 10 bits Bits/(Pixel*Frame) : 0.166 Stream size : 8.13 GiB (97%) Default : Yes Forced : No Color range : Limited Color primaries : BT.2020 Transfer characteristics : PQ Matrix coefficients : BT.2020 non-constant Mastering display color primaries : Display P3 Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2 Maximum Content Light Level : 1 842 cd/m2 Maximum Frame-Average Light Level : 214 cd/m2 This doesn't: General Unique ID : 155711748636044123552656759211769784089 (0x7524FDEFB8A20CB7AC8BD889F300E719) Complete name : Z:\TV Series\Lucky (2026)\Season 1\S01E02 - Make 'em Dance.mkv Format : Matroska Format version : Version 4 File size : 8.55 GiB Duration : 48 min 1 s Overall bit rate : 25.5 Mb/s Frame rate : 23.976 FPS Title : Lucky S01E02 Make 'em Dance Writing application : mkvmerge 94.0 ('Initiate') 64-bit Writing library : libebml v1.4.5 + libmatroska v1.7.1 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L5@High HDR format : Dolby Vision, Version 1.0, Profile 5, dvhe.05.06, BL+RPU, no metadata compression Codec ID : V_MPEGH/ISO/HEVC Duration : 48 min 1 s Bit rate : 24.7 Mb/s Width : 3 840 pixels Height : 1 606 pixels Display aspect ratio : 2.39:1 Frame rate mode : Constant Frame rate : 23.976 (24000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 10 bits Bits/(Pixel*Frame) : 0.167 Stream size : 8.29 GiB (97%) Language : English Service kind : Original Default : Yes Forced : No Color primaries : BT.2020 Transfer characteristics : PQ Matrix coefficients : IPT-PQ-C2
ebr 16603 Posted 52 minutes ago Posted 52 minutes ago Yep, as seen in your media info, the one that plays is 8.1 (has fallback) and the one that doesn't is 5 (pure DV - no fallback). 1
Sammy 794 Posted 48 minutes ago Author Posted 48 minutes ago I'm not thinking any "free" solution will convert this such as Handbreak or MKVToolNix.. Plus that's a bunch of work. A new TV that supports DV is the better solution! 1
Lessaj 543 Posted 8 minutes ago Posted 8 minutes ago I believe it can be done with dovi_tool but requires a re-encode, so it's a little bit of a lossy process, but feasible. New TV does sound better though.
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