joechilds 18 Posted January 31, 2025 Posted January 31, 2025 I've noticed a few titles have their Dolby Profile described as "none" in Emby Server, even though Emby correctly identifies them as Dolby Vision at the top of the page - "Video 4K Dolby Vision HEVC". I've tried re-adding the file, and refreshing metadata, but no change. Here's the MediaInfo for one of those files - everything looks normal to me. Spoiler General Format : Matroska Format version : Version 4 File size : 14.3 GiB Duration : 1 h 41 min Overall bit rate mode : Variable Overall bit rate : 20.2 Mb/s Frame rate : 23.976 FPS Encoded date : 2024-07-12 21:47:13 UTC Writing application : mkvmerge v85.0 ('Shame For You') 64-bit Writing library : libebml v1.4.5 + libmatroska v1.7.1 IMDB : tt0101272 TMDB : movie/2907 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L5.1@Main HDR format : Dolby Vision, Version 1.0, Profile 8.6, dvhe.08.06, BL+RPU, no metadata compression, Blu-ray compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible Codec ID : V_MPEGH/ISO/HEVC Duration : 1 h 41 min Bit rate : 16.0 Mb/s Width : 3 840 pixels Height : 2 076 pixels Display aspect ratio : 1.85:1 Frame rate mode : Variable Frame rate : 23.976 FPS Color space : YUV Chroma subsampling : 4:2:0 (Type 2) Bit depth : 10 bits Bits/(Pixel*Frame) : 0.084 Stream size : 11.3 GiB (79%) Writing library : x265 3.5+153+15-fc339385e:[Windows][MSVC 1937][64 bit] 10bit Encoding settings : cpuid=1111039 / frame-threads=4 / numa-pools=16 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=3840x2076 / interlace=0 / total-frames=145511 / level-idc=51 / high-tier=0 / uhd-bd=0 / ref=4 / no-allow-non-conformance / repeat-headers / annexb / aud / no-eob / no-eos / hrd / info / hash=0 / temporal-layers=0 / no-open-gop / min-keyint=23 / keyint=240 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=25 / lookahead-slices=4 / scenecut=40 / no-hist-scenecut / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=2 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / no-strong-intra-smoothing / max-merge=3 / limit-refs=3 / no-limit-modes / me=3 / subme=3 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=-3:-3 / no-sao / no-sao-non-deblock / rd=4 / selective-sao=0 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=1.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=abr / bitrate=16000 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=2 / cplxblur=20.0 / qblur=0.5 / vbv-maxrate=32000 / vbv-bufsize=40000 / vbv-init=0.9 / min-vbv-fullness=50.0 / max-vbv-fullness=80.0 / ipratio=1.40 / pbratio=1.30 / aq-mode=3 / aq-strength=1.00 / aq-bias-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=1 / chromaloc-top=2 / chromaloc-bottom=2 / display-window=0 / master-display=G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,10) / cll=1000,214 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / hdr10 / hdr10-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=0 / analysis-save-reuse-level=0 / analysis-load-reuse-level=0 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / scenecut-aware-qp=0 / conformance-window-offsets / right=0 / bottom=0 / decoder-max-rate=0 / no-vbv-live-multi-pass / no-mcstf / no-sbrc 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.0010 cd/m2, max: 1000 cd/m2 Maximum Content Light Level : 1000 cd/m2 Maximum Frame-Average Light Level : 214 cd/m2 Audio ID : 2 Format : DTS XLL Format/Info : Digital Theater Systems Commercial name : DTS-HD Master Audio Codec ID : A_DTS Duration : 1 h 41 min Bit rate mode : Variable Bit rate : 4 150 kb/s Channel(s) : 6 channels Channel layout : C L R Ls Rs LFE Sampling rate : 48.0 kHz Frame rate : 93.750 FPS (512 SPF) Bit depth : 24 bits Compression mode : Lossless Stream size : 2.93 GiB (21%) Title : DTS-HD MA 5.1 Language : English Default : Yes Forced : No Text ID : 3 Format : PGS Muxing mode : zlib Codec ID : S_HDMV/PGS Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs Duration : 1 h 32 min Bit rate : 33.9 kb/s Frame rate : 0.407 FPS Count of elements : 2262 Stream size : 22.4 MiB (0%) Title : English Language : English Default : No Forced : No 1
Lessaj 467 Posted January 31, 2025 Posted January 31, 2025 Interesting, I don't think I've seen profile 8.6 before. Do you have any other 8.6 files that report correctly? Or are they all 7.6/8.1? 1
joechilds 18 Posted February 1, 2025 Author Posted February 1, 2025 (edited) 4 hours ago, Lessaj said: Interesting, I don't think I've seen profile 8.6 before. Do you have any other 8.6 files that report correctly? Or are they all 7.6/8.1? Oh thanks, I didn't even notice that, that does seem wrong... The profile should be 8.1, as it's profile 8 with HDR compatibility, right? The .6 profile suffix should only be used on BluRay discs (i.e. profile 7.6), so 8.6 can't be right. I'm seeing this on multiple files, maybe there's an issue with MKVtoolnix? Or Dovi_Tool? Edited February 1, 2025 by joechilds
joechilds 18 Posted February 1, 2025 Author Posted February 1, 2025 https://discourse.coreelec.org/t/dolby-vision-for-minix-u22x-j-max-and-ugoos-am6/24273/1092 Found someone else having the same issue, no suggestion as to a solution though
Lessaj 467 Posted February 1, 2025 Posted February 1, 2025 I struggled to find much information about 8.6 too... Didn't seem like something that should happen? Do they play though? 1
joechilds 18 Posted February 1, 2025 Author Posted February 1, 2025 5 minutes ago, Lessaj said: I struggled to find much information about 8.6 too... Didn't seem like something that should happen? Do they play though? Yeah they seem to play fine, they trigger DV mode on my television, they look right to me. They appear to be profile 8.1 files, but mis-tagged or mis-labelled somehow. Strange. 1
joechilds 18 Posted February 1, 2025 Author Posted February 1, 2025 (edited) @Luke Perhaps Emby could be updated to display the “Dolby Profile” as 8.1, when it encounters these erroneous profile 8.6 videos? Having the Dolby Profile set to “None” is causing issues with apps like Infuse that pull information from Emby Server. Edited February 1, 2025 by joechilds
Luke 42077 Posted February 2, 2025 Posted February 2, 2025 On 2/1/2025 at 12:31 PM, joechilds said: @Luke Perhaps Emby could be updated to display the “Dolby Profile” as 8.1, when it encounters these erroneous profile 8.6 videos? Having the Dolby Profile set to “None” is causing issues with apps like Infuse that pull information from Emby Server. Hi, yes I think this would be ideal. Thanks. 1
65535 14 Posted May 1, 2025 Posted May 1, 2025 On 2/2/2025 at 8:55 PM, Luke said: Hi, yes I think this would be ideal. Thanks. Is this still planned? The Xbox app doesn't switch to HDR mode with such DV 8.6 files, which makes them unplayable. I believe this change would fix that.
yocker 1247 Posted May 1, 2025 Posted May 1, 2025 (edited) I looked it up using an AI, so the information might be wrong. Profile 8.6. This profile is part of the Profile 8 family, which is designed for single-layer Dolby Vision streams compatible with HDR10. Specifically, Profile 8.6 is identified by the codec string dvhe.08.06, indicating a 10-bit HEVC stream with a base layer (BL) and a reference processing unit (RPU), but no enhancement layer. It includes static metadata conforming to SMPTE ST 2086 and is compatible with HDR10, making it suitable for Blu-ray content . It is rarely used and it's purpose is meant to be for backwards compatibility with specific niche devices. Edited May 1, 2025 by yocker
rbjtech 5284 Posted May 1, 2025 Posted May 1, 2025 (edited) 1 hour ago, yocker said: I looked it up using an AI, so the information might be wrong. Profile 8.6. This profile is part of the Profile 8 family, which is designed for single-layer Dolby Vision streams compatible with HDR10. Specifically, Profile 8.6 is identified by the codec string dvhe.08.06, indicating a 10-bit HEVC stream with a base layer (BL) and a reference processing unit (RPU), but no enhancement layer. It includes static metadata conforming to SMPTE ST 2086 and is compatible with HDR10, making it suitable for Blu-ray content . It is rarely used and it's purpose is meant to be for backwards compatibility with specific niche devices. There is no such thing as Profile 8.6 - so yes AI is wrong. x.6 is used for UHD Disks - and a standard UHD Disk has a 7.6 profile - not an 8.6 profile. https://professionalsupport.dolby.com/s/article/What-is-Dolby-Vision-Profile?language=en_US A 'home brew' normal 8.x DV profile should be 8.1 or 8.4 the 8.1 meaning it has a HDR10 fallback layer (common) or 8.4 meaning it has a HLG fallback layer (rare). No HDR10 fallback layer is Profile 5. (the green/purple colours if you try and play it back on non DV equipment) If the file has been tagged as 8.6 - then it it outside the spec as defined by Dolby themselves - thus emby is likely to not recognise it. It should be easy enough to correct it using dovi_tools - but you may need to demux and then remux it using 8.1 etc as required. The fallback as suggested above, it to default to 8.1 if anything other than 8.1 or 8.4 is used Edited May 1, 2025 by rbjtech 1
yocker 1247 Posted May 1, 2025 Posted May 1, 2025 (edited) 2 hours ago, rbjtech said: There is no such thing as Profile 8.6 - so yes AI is wrong. x.6 is used for UHD Disks - and a standard UHD Disk has a 7.6 profile - not an 8.6 profile. https://professionalsupport.dolby.com/s/article/What-is-Dolby-Vision-Profile?language=en_US A 'home brew' normal 8.x DV profile should be 8.1 or 8.4 the 8.1 meaning it has a HDR10 fallback layer (common) or 8.4 meaning it has a HLG fallback layer (rare). No HDR10 fallback layer is Profile 5. (the green/purple colours if you try and play it back on non DV equipment) If the file has been tagged as 8.6 - then it it outside the spec as defined by Dolby themselves - thus emby is likely to not recognise it. It should be easy enough to correct it using dovi_tools - but you may need to demux and then remux it using 8.1 etc as required. The fallback as suggested above, it to default to 8.1 if anything other than 8.1 or 8.4 is used You are right, at least it's not on the official Dolby Vision list. A quick google search shows quite a bit of results about profile 8.6, earliest of them from about mid-late 2023. Some people claiming that it's a streaming only profile (Apple TV), though it to me looks like it originated (at least to the public) with some MakeMKV build or something. There have been non-public DV profiles before ,so it could exist, just being used for some streaming service.. Hard to tell though but there is enough talk about it and files floating around for me to not dismiss 8.6 as an actual thing. Anyway, i try to keep my Dolby Vision videos in profile 8.1. Edited May 1, 2025 by yocker 1
rbjtech 5284 Posted May 1, 2025 Posted May 1, 2025 10 minutes ago, yocker said: You are right, at least it's not on the official Dolby Vision list. A quick google search shows quite a bit of results about profile 8.6, earliest of them from about mid-late 2023. Some people claiming that it's a streaming only profile (Apple TV), though it to me looks like it originated (at least to the public) with some MakeMKV build or something. There have been non-public DV profiles before ,so it could exist, just being used for some streaming service.. Hard to tell though but there is enough talk about it and files floating around for me to not dismiss 8.6 as an actual thing. Anyway, i try to keep my Dolby Vision videos in profile 8.1. Agree it's probably a 'thing' that somebody thought was a good idea (a higher number is better right ? ) - a bit like h264 and h265 'profiles' that are far too high for the source material. All they do is cause trouble and unnecessary transcoding. 8.x is a streaming profile only - agree 100% - but it's the .6 part that is 100% wrong - as that says it's a physical BD disk - which clearly it is not.. Unfortunately, there are a lot of people out there who have the tools, but very little knowledge on what they are doing thus we get these odd combos ... A bit like the DV, HDR10+ (and thus HDR10) MKV's - totally against a defined 'standard' but 'it works' on 'some' equipment ... problem is, no hardware manufacturer wants to know about the issues, as DV or HDR10+ works - but not both as they have been 'hacked' to work ... 1
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