Apple TV 4K and Dolby Vision profile 8

Hello, just discovered Infuse and loving it so far on Apple TV.

I am reading a lot about Dolby Vision profiles on ATV and as far I know this is the situation:

  • ATV only displays DV profile 5 properly
  • I have a lot of backups with DV profile 8 (dvhe08.06) which Infuse sees as DV in the menu but if I am correct eventhough Infuse recognizes it as DV and my TV goes into/triggers Dolby Vision mode IT IS STILL HDR 10 right? I have read a lot in these forums and it still confuses me a bit. Why would Infuse not see it as HDR instead of DV? I reckon this might be the cause of DV profile 8 support with videos shot on Iphone 12? What I would expect: Infuse to recognize all DV profiles EXCEPT 5 as HDR cause thats the only profile officially supported by ATV. Or might it be cause of iphone 12 format DV profile 8 we really do get to play DV profile 8 properly on ATV? Here’s hoping…

Hi there!

Correct, it is still only HDR10 playback.

See here: Profile 8 fallback to HDR support - #8 by tbor85

There might be a fix for this on its way for v7.3.5

See here: Upcoming Features (updated 2/19/22)

I assume a possible fix by @james will be regarding TVs not triggering Dolby Vision but HDR10 instead. Also maybe showing P8 files only with the „HDR“ media attribute in Infuse menus.

Thank you tbor85! If only Apple TV would just permit DV 8 it would have been complete. I have the Shield Pro tough which does accept profile 8 but thats knows for few years for a ‘Dolby Vision’ bug that the colour has a bit of a red push. I dont mind that all tbh for me its bareley visible. So I can watch already DV8 on Shield but the picture image of ATV is simply superior compared to other devices so I prefer ATV any time

Maybe the latest tvos 15.3 has the ability to support DoVi profile 8.1 for now?
I have tested profile 8.1 mkv video with infuse 7.3.5 AND PLEX, both of them can trigger DoVi mode or TV(My TV: sony Z9F)

this is my tested file info:

Format : Matroska
Format version : Version 4
File size : 21.0 GiB
Duration : 2 h 10 min
Overall bit rate mode : Variable
Overall bit rate : 23.0 Mb/s
Encoded date : UTC 2022-02-22 11:14:17
Writing application : mkvmerge v62.0.0 (‘Apollo’) 64-bit
Writing library : libebml v1.4.2 + libmatroska v1.6.4

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 10 min
Bit rate : 15.3 Mb/s
Width : 3 840 pixels
Height : 1 608 pixels
Display aspect ratio : 2.40: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.104
Stream size : 14.0 GiB (67%)
Writing library : x265 3.3+3-g8f8e332f1+29:[Windows][#Erg`Djh#][@Yuuki] made by @Dongfangbubai
Encoding settings : rc=crf / crf=18.0000 / qcomp=0.70 / qpstep=4 / stats-write=0 / stats-read=0 / vbv-maxrate=160000 / vbv-bufsize=160000 / vbv-init=0.9 / crf-max=0.0 / crf-min=0.0 / no-lossless / no-cu-lossless / aq-mode=3 / aq-strength=0.80 / cbqpoffs=-3 / crqpoffs=-3 / ipratio=1.40 / pbratio=1.30 / psy-rd=2.00 / psy-rdoq=3.00 / deblock=-1:-1 / ref=5 / limit-refs=0 / no-limit-modes / bframes=8 / b-adapt=2 / bframe-bias=0 / b-pyramid / b-intra / weightp / weightb / min-keyint=23 / max-keyint=240 / rc-lookahead=60 / gop-lookahead=0 / scenecut=40 / hist-scenecut=0 / radl=0 / max-cu-size=32 / min-cu-size=8 / me=3 / subme=4 / merange=25 / rdoq-level=2 / rd=4 / rdpenalty=1 / dynamic-rd=0.00 / no-rd-refine / ----- / no-cutree / no-sao / no-rect / no-amp / no-open-gop / wpp / pmode / pme / no-psnr / no-ssim / nr-intra=0 / nr-inter=0 / no-constrained-intra / no-strong-intra-smoothing / max-tu-size=32 / tu-inter-depth=2 / tu-intra-depth=2 / limit-tu=0 / qg-size=32 / qpmax=69 / qpmin=0 / ----- / cpuid=1176575 / frame-threads=6 / numa-pools=54,- / log-level=2 / input-csp=1 / input-res=3840x1608 / interlace=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / no-allow-non-conformance / repeat-headers / aud / hrd / info / hash=0 / no-temporal-layers / lookahead-slices=0 / no-splice / no-intra-refresh / no-ssim-rd / signhide / no-tskip / max-merge=3 / temporal-mvp / no-frame-dup / no-hme / no-analyze-src-pics / no-sao-non-deblock / selective-sao=0 / no-early-skip / no-rskip / no-fast-intra / no-tskip-fast / no-splitrd-skip / zone-count=0 / no-strict-cbr / no-rc-grain / no-const-vbv / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=0 / display-window=0 / master-display=G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50) / cll=0,0 / 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 / hist-threshold=0.01 / 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 / no-scenecut-aware-qpconformance-window-offsets / right=0 / bottom=0
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

Hello. I want to draw your attention to the fact that the current version 7.3.5 with the Dolby Vision 8.1 profile has an image flicker problem on Mac OS Monterey 12.2.1

It does work with me too but I have no clue if its real DV or ‘fake’ and we look at HDR. It does look sublime but anything on ATV looks sublime. I think you need some monitoring tools like HD fury who can see what signal goes to your tv I dont have that. Maybe there are DV files that when Infuse communicates with the ATV the ATV thinks/recognizes its format as a valid DV file. Maybe one day we know. The way DV is been maded its very fragmented by Dolby its a difficult codec.

If it is P8 and not coming from an iPhone recording, you‘ll look at HDR playback for now.

Your TV says „Dolby Vision“ (mine shows it, too), but it is not.

No need for fancy tools, you can see it if you compare the same media to a P5 copy.

What is funny is that Infuse already correctly labels dvhe.08.06 in the on screen menu with „HDR“ (not „DV“ as it does for dvhe.05.06 for example).
I suppose that somehow Infuse already knows, that it can only playback the media with HDR support. However, Dolby Vision is still wrongfully triggered by Infuse on TVs…

I am still hoping to having this fixed by @james in the near future… :slight_smile:

If I compare the media info to a P5 the only difference I see that P5 has no fallback to HDR. P8 does have fallback to HDR and thats why I am still confused that why it does not show HDR when playing a P8 files. P8 always have a HDR layer while P5 has not. So I think its still more complex than you think :). What makes it REALLY difficult is that some P8 files trigger DV and other P8 files not and they (when checked through mediainfo) have both the same P8 profile. So once again its not that easy and I can still have the idea that the API belong to ATV somehow thinks thats its real DV maybe a handshake issue.

Oh no, you got me wrong. I meant comparing P5 and P8 on screen… really playing both files and actually seeing the differences between Dolby Vision (P5) and „fake Dolby Vision“ (P8)… :slight_smile:

haha that I cant see indeed it both looks great. So thats why its no biggie for most of us. I mean I tried but I cannot see lol. Btw i still have P8 DV profile movies which show DV and not HDR in Infuse.

And it is correct, there is nothing to change, DV profile 8 is hybrid, and supports both HDR10 and Dolby vision, it is the best option in terms of compatibility, because if your tv is not compatible with DV, it will activate HDR10, and in case it is compatible with DV, it will activate this.

The way it works now is the right thing to do

Terry thats indeed true but the ‘funny’ thing is that on some DV P8 it shows DV on my ATV instead of HDR in the mediainfo of Infuse and when I watch it , it does trigger DV on my LG OLED and not HDR. DV which if I am correct is ‘fake’ and really is HDR.

1 Like

Correct as far as I’m aware.
The Apple TV is capable of some levels of Profile 8.
The hybrid releases that are becoming prevalent are not supported.
As you suspect they’re simply switching the ATV to DV mode but they’re actually playing HDR10.

1 Like

But how we know its fake? I mean ATV cannot play profile 8 but my LG Oled can. Maybe ATV is just passing signal through and my TV does the work? Its like playing sbs 3d on ATV. ATV does not recognize the 3D but my tv does…

Another question I read that colors appear desaturated but thats not the case at all. Maybe my eyes are that bad but it really looks stunning when I play a ‘fake’ DV file. Maybe thats technical bs what I say right now, but what if ATV just passes through the DV and our LG OLED recognizes/supports dv 8 profile and correctly triggers DV? Or is that too crazy ?

Another thing: when I watch DV8 on Shield it looks just the same as DV8 on ATV (same file/movie). Fake or not. It makes me crazy I wanna know the answer hahaha

1 Like

I agree.

My life didn’t change. Fake DV or not my life didn’t change. I certainly see nothing desaturated at all.
Perhaps with 2 identical TV’s sat side by side running the Shield and the Apple TV. :joy:

I guess a lot of us (oldies) get wrapped up in seeing Atmos trigger on our AVR and DV trigger on our TV and use that the benchmark as if we really discern it’s better than what the picture on the TV looks like and what we hear.

TL;DR I think I’m too old to care

haha I am too but later when I have daycare I will hold up my ATV and say to the nurse ‘did you know this device from 2021 had fake DV’…

1 Like

I do get you.
But to be fair @James is slightly crippled with what Apple themselves allow.

He does his best with what’s actually possible and if I may say he does it really well.

If the day comes when he develops or helps someone else develop a client (that doesn’t really suck) for something like the shield then damn…I’m in

Ofc they do their best I have no doubts and if I was developer this would end up below my list. Its a nice to have fix, not a NEED TO have. The support here is very good!