Dolby Vision now possible through MP4 Mux.

[afarvvik]

any idea why a P8 DV video in EAC3-MP4 format is playing in HDR on a LG c8?

this is the mediainfo of the movie

Code: Select all

GENERAL
Format
MPEG-4
Duration
1 h 48 min
Bitrate
16.8mb/s
Size
12.8 GiB
VIDEO
Format
HEVC (10 bits)
Resolution
3 840 × 1 608
Aspect ratio
2.40:1
Frame rate
23.976 (24000/1001) FPS
Bit rate
16.0mb/s
HDR format
Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
Color primaries
BT.2020
Transfer characteristics
PQ
AUDIO
1.
English English / E-AC-3 / 8ch / 768kb/s / E-AC-3 7.1
ENCODE SETTINGS
cpuid=1111039 / frame-threads=3 / numa-pools=12 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=3840x1608 / interlace=0 / total-frames=156665 / 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(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(40000000,50) / cll=683,136 / 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

tried converting it to m2ts using tsmuxer as I do with mkv files but it gives a error at 60% -"Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps"

thanks

hi @RESET_9999

any idea why this is happening? according to your google sheet P8 should work in the C8.

[RESET_9999]

Hi RESET, I still notice raised black level when using Microsoft Hardware Video Decoder in the Energy player. I've tried both on Oled G8 monitor and S95C TV. Does this happen to your samsung monitor? I began to worry there's something wrong with my settings.
Currently, I set output to 10bit Full Range RGB HDR in the AMD control panel, and Full Range input in samsung menu. I've tried restoring all other settings to default, but it doesn't change anything. Do you know if any other setting that may cause the problem?

I'll check on my C2. On the Samsung LS49CG932SNXZA , it seems fine. I use 444 12bit and the video I did on youtube about this player was captured/played in 422 12bit.

any idea why this is happening? according to your google sheet P8 should work in the C8.

idk, your mediainfo is incomplete. I guess your file is mp4 with id hev1.. remux to ts or use my script to convert to mp4 with id dvhe

There is any compatibility or playback difference between "Dolby Vision, Version 1.0, dvhe.08.06" and "Dolby Vision, Version 1.0, dvhe.08.10"?
Thanks.

the .10 .06 .07 etc.. is related to the resolution/framerate max pps
viewtopic.php?p=121936#p121936

[thirdmoon]

@RESET_9999

I had a 10min HDR clip, and I generated DV in Resolve but forgot to set output blanking at 42/42. While injecting DV, I edited L5 to 42/42. Is the DV correct here or I have to generate the XML from resolve again?

[sw5163]

On the Samsung LS49CG932SNXZA , it seems fine.

Do you have Game Mode on or off on that monitor?

I use 444 12bit and the video I did on youtube about this player was captured/played in 422 12bit.

I just tried YUV 444 12bit, still the same. Both P5 and P8.1 contents have raised black on my setup. I also tried your black test file.
Playing directly in Samsung internal player:

internal.player.JPG (3.33 MiB) Viewed 5045 times

Playing in Movies & TV app:

movies&tv.JPG (3.21 MiB) Viewed 5045 times

These photos were shot with 6400 ISO and 32 seconds exposure, the green is actually dark grey and wasn't that bad to naked eyes. I'm going to check with another Nvidia laptop later in case it's an AMD APU problem.

[powdeau]

@RESET_9999

Can you please tell me what the difference is between these two RPU of yours?
Generated_OSC.bin
DV_L2_original.xml

Thanks!

[RESET_9999]

@RESET_9999

I had a 10min HDR clip, and I generated DV in Resolve but forgot to set output blanking at 42/42. While injecting DV, I edited L5 to 42/42. Is the DV correct here or I have to generate the XML from resolve again?

well your video min_pq metadata wont be as accurate. It's not really a big deal though.

@RESET_9999

Can you please tell me what the difference is between these two RPU of yours?
Generated_OSC.bin
DV_L2_original.xml
Thanks!

the rpu bin file is with all the L2 trims removed and the XML is the original metadata with trims.
The generated trims have a brightening effect in low nits scenes and some people like it and don't care about the creator's intent.

These photos were shot with 6400 ISO and 32 seconds exposure, the green is actually dark grey and wasn't that bad to naked eyes. I'm going to check with another Nvidia laptop later in case it's an AMD APU problem.

wow, ok no there's no such issue on my setup (nvidia). Blacks are actually better than in HDR10 when I put them side by side.
And no crush, I can see 65 flashing. I forgot to check on the C2 but if it was as bad as in your photo, I would have noticed the other day.

this is on the Samsung G9

[sw5163]

wow, ok no there's no such issue on my setup (nvidia). Blacks are actually better than in HDR10 when I put them side by side.

I just tested with a 4060 laptop, DV still has raised black. The HDR10 playback looks similar to yours, but also has a very slight raised black. I previously considered it's decoder related because the top and bottom bars were pure black when playing 3840x1600 content. So strange that DV is much worse on my setup.

this is on the Samsung G9

May I ask do you have Game Mode on or off on that monitor?
Also, could you please tell me your GPU model and driver version?
Do you use the 1$ "HEVC Video Extensions" in MSFT store or do you use the free "HEVC Video Extensions from Device Manufacturer"?
I want to restore all devices and copy exactly the same setting you're using to see what will happen. Thanks!

[RESET_9999]

I just tested

Yes, you're right. I couldn't see it on my Samsung monitor because it's in a bright room but on the C2 I can see the slightly raised blacks.
The problem seem to be the Microsoft HEVC extension because it's a lot worse with HDR10 but if you force ffmpeg for the decoding, it's fine.


EDIT: wait that's not it. I couldn't understand how I could have missed the raised black on my Samsung.
So I played with the settings (game mode). Played some HDR10 and DV on Movies&tv / energy player and somehow whatever I did raise the black.
Rebooted my PC, and now I no longer see the raised black... Trying to figure out what's causing the issue

ps I use the 1$ extension and not the free one. Game mode off. driver 546.01 rtx3070

[sw5163]

Yes, you're right. I couldn't see it on my Samsung monitor because it's in a bright room but on the C2 I can see the slightly raised blacks.

QD-OLED will lit up by ambient light, I tend to use it in a dark room. G9 is really wide...

The problem seem to be the Microsoft HEVC extension because it's a lot worse with HDR10 but if you force ffmpeg for the decoding, it's fine.

Strangely for me, DV is worse than HDR10. Maybe because LG supports DV and Samsung does not? I read somewhere DV can be either TV-LED, or Player-LED, or map to HDR10/SDR by player and send HDR10/SDR signal, I'm guessing on Samsung it's the third one?
HDR10 6400ISO 32 seconds exposure (no HDR calibration configuration file):

Rebooted my PC, and now I no longer see the raised black... Trying to figure out what's causing the issue

Reboot doesn't change anything on my end. Since I can get most of other players to play pure black, the issue is still highly likely MSFT's fault.

[RESET_9999]

idk I can't replicate what I did ... This morning when I played with the settings and I broke something. Rebooting my PC fixed it. Before rebooting, I could clearly see a difference between the black in the pattern itself and the black border from the energy player window even in the bright room but now I no longer see a difference and it look better than HDR10/MPC like yesterday.
HDR10 blacks with the Microsoft hevc extension are not right, that's for sure.

One thing about LLDV though. If the min_pq target is not 0, then it is raised. I can replicate with any edid that is not set to 0. My C2 min_pq edid value is not 0. My Samsung G9 is set to 0:

Code: Select all

  Vendor-Specific Data Block (AMD), OUI 00-00-1A:
    Version: 2.7
    Minimum Refresh Rate: 48 Hz
    Maximum Refresh Rate: 240 Hz
    Flags 1.x: 0x00
    Flags 2.x: 0x04
    Maximum luminance: 96 (400.000 cd/m^2)
    Minimum luminance: 1 (0.000 cd/m^2)
    Maximum luminance (without local dimming): 74 (248.372 cd/m^2)
    Minimum luminance (without local dimming): 2 (0.000 cd/m^2)
  HDR Static Metadata Data Block:
    Electro optical transfer functions:
      Traditional gamma - SDR luminance range
      SMPTE ST2084
    Supported static metadata descriptors:
      Static metadata type 1
    Desired content max luminance: 96 (400.000 cd/m^2)
    Desired content max frame-average luminance: 74 (248.372 cd/m^2)
    Desired content min luminance: 0 (0.000 cd/m^2)
  YCbCr 4:2:0 Capability Map Data Block:
    VIC  97:  3840x2160   60.000000 Hz  16:9    135.000 kHz    594.000000 MHz
    VIC  96:  3840x2160   50.000000 Hz  16:9    112.500 kHz    594.000000 MHz
  Vendor-Specific Video Data Block (HDR10+), OUI 90-84-8B:
    Application Version: 1
    Full Frame Peak Luminance Index: 2
    Peak Luminance Index: 3

[RESET_9999]

Ok I was able to break my Windows black level again and I know what I did to break it.
If I launch the energy player into my 2nd monitor (vizio tv edid not 0), then blacks are raised even if I play the same file again on my first monitor (Samsung). If I reboot and launch the energy player into the Samsung display, then blacks are blacks because of my G9 edid.

Vizio TV edid:

Code: Select all

  Vendor-Specific Data Block (HDMI Forum), OUI C4-5D-D8:
    Version: 1
    Maximum TMDS Character Rate: 600 MHz
    SCDC Present
    Supports 12-bits/component Deep Color 4:2:0 Pixel Encoding
    Supports 10-bits/component Deep Color 4:2:0 Pixel Encoding
  Vendor-Specific Video Data Block (Dolby), OUI 00-D0-46:
    Version: 0 (26 bytes)
    Supports 2160p60
    DM Version: 2.8
    Target Min PQ: 124 (0.02015421 cd/m^2)
    Target Max PQ: 2908 (681 cd/m^2)
    Rx, Ry: 0.67651367, 0.30566406
    Gx, Gy: 0.25732422, 0.65771484
    Bx, By: 0.15234375, 0.04956055
    Wx, Wy: 0.31274414, 0.32910156

[sw5163]

idk I can't replicate what I did ...

HDR10 in that photo looks way off, I came across once when I dragged Movies & TV app from laptop SDR display to external HDR display while it was playing. But it's not the same this time, on my end the raised black level is unlikely to be perceived if not in a really dark room.

[RESET_9999]

as I said, in LLDV player led if your edid min target is not 0, you'll get raised blacks. I replicated on my C2 too, if I use the default c2 edid its raised, if I use a custom edid with min target set to 0 and reboot, then black is black. My C2 is in a room with black velvet on floor ceiling and walls. No windows, no lights.

[sw5163]

as I said, in LLDV player led if your edid min target is not 0, you'll get raised blacks. I replicated on my C2 too, if I use the default c2 edid its raised, if I use a custom edid with min target set to 0 and reboot, then black is black. My C2 is in a room with black velvet on floor ceiling and walls. No windows, no lights.

I have 2 questions, why LG provide "target min pq" above 0 EDID on OLED TV? And does that mean players that are able to play pure black on this EDID, are not following the "target min pq" correctly? Sorry if these have alread been asked.

With hdmi devices like HDfury vertex or raspberry pi + Pgen.
There might be other ways I'm not aware of but I know that there is some cheap HDMI splitter that can let you upload any edid(I have one for any brightness).

Any chance I can check and switch my EDID by only using a PC?

[RESET_9999]

I dont know but all LG OLED TVs have raised black in DV, even in TV-LED.
And all the players I tested LLDV had raised black without a 0 min pq edid