Does the effect ever phase out on higher nits TV?RESET_9999 wrote: ↑Fri Jan 26, 2024 11:23 pmI tested the AppleTV , Shield and x700, the behavior was the same:
100nits L2 or L8 has an effect if no 600-1000trims exist and the effect is much more pronounced with lower nits TV.
Dolby Vision now possible through MP4 Mux.
-
- Posts: 31
- Joined: Sat Feb 26, 2022 12:44 am
Re: Dolby Vision now possible through MP4 Mux.
-
- Posts: 2093
- Joined: Mon Aug 05, 2019 7:12 pm
Re: Dolby Vision now possible through MP4 Mux.
I guess and it depends on how strong the L2 trim is and a 4000nits RPU probably has a bigger effect. I only tested 1000nits RPU and in TV-LED on C2 810nits, Vizio 600nits and Samsung 400nits. I'll check with higher edid in LLDV this weekend.
Sorry for my English.
DoVi_Scripts / DoVi Playback Devices / Movies HDR-DV Plot / Screenshot Comparisons
DoVi_Scripts / DoVi Playback Devices / Movies HDR-DV Plot / Screenshot Comparisons
-
- Posts: 31
- Joined: Sat Feb 26, 2022 12:44 am
Re: Dolby Vision now possible through MP4 Mux.
This is the part I am curious.RESET_9999 wrote: ↑Fri Jan 26, 2024 11:58 pmI guess and it depends on how strong the L2 trim is and a 4000nits RPU probably has a bigger effect. I only tested 1000nits RPU and in TV-LED on C2 810nits, Vizio 600nits and Samsung 400nits. I'll check with higher edid in LLDV this weekend.
for content mastered at 1000nits, the final content after processing should be no more than 1000nits (or a little more like 1200 or 1300nits for peaks)? So theoretically, it would make sense for the effect to phase out at 1000nits TV?
for content mastered at 4000nits, the final content after processing could be > 3000nits for peaks. it would make sense it has stronger effect on 1000nits TV.
Re: Dolby Vision now possible through MP4 Mux.
I added lot of other models to available settings docs.chros wrote: ↑Fri Jan 26, 2024 8:13 amThose values come from the extracted firmware.aboulfad wrote: ↑Thu Jan 25, 2024 10:26 amWere those values retrieved using bscpylgtv command or by extracting the default DV config files from the C2 TV firmware?chros wrote: ↑Wed Jan 24, 2024 10:03 pm
I have added DoVi section to all the available settings docs.
VSVDB is the EDID value.
As discussed prior, I think @quietvoid commented that the EDID Tmax values transmitted to an hdmi external device are used for “detection/player led” and TV led uses those internal config values.
The C2 default config file entry is same to what you’ve captured in the docs. It may not or is not the same as the EDID VSVDB value transmitted over the wire. Here’s my findings for my older E7, where the EDID VSVDB Dolby Tmax is way lower (350) than my TV’s internal DV Tmax (~750). I don’t have any Vertex to confirm this, I used an rpi5 connected to the TV & a command to get the EDID.
quietvoid is right, vsvdb values are used by lldv external devices.
And internal and vsvdb values can be different, eg with C8 (560 in Cinema vs 700 vsvdb).
Maybe I will add more models later as a sub section (Bx, Ax, and diferent sizes with newer models).
Re: Dolby Vision now possible through MP4 Mux.
cool! Too bad I can’t find my 2017 E7 config, I’ve searched hi & Lo in the FW as well on my TV (lg dev mode not rooted) but can’t find it.I found some but Tmax was too low for E7.
[Oppo UDP-203, ATV 4K] —> Anthem MRX-720 —> LG OLED65E7P
Re: Dolby Vision now possible through MP4 Mux.
Look in "tvservice-dvb.pak.unsquashfs/mnt/lg/tvservice/pqldb/dolby" (not in rootfs) in the extracted firmware, that's where 2018/2019 models have it.
Re: Dolby Vision now possible through MP4 Mux.
Thanks, per prior search in a different path for 2017 E7 the highest Tmax I found was 430nits. If indeed E7 or other newer series are using default DV config files shipped with firmware for TV-Led, that would imply for older gen a much lower Tmax is used by default for TV-led. 2017 E7 as per rtings & few publicly shared DV calibration configs is around 700-760nits.
The retrieved (from EDID) VSVDB(Dolby) Tmax is 350 nits which is oddly also a very low value for player-led. I realize my TV is old but just curious what's up !
PS: path for E7 DV OLED firmware file
Code: Select all
06.10.30.01-HE_DTV_W17H_AFADATAA/tvservice-atsc.pak.unsquashfs/mnt/lg/tvservice/pqldb/dolby/OLED_All.txt
[Oppo UDP-203, ATV 4K] —> Anthem MRX-720 —> LG OLED65E7P
Re: Dolby Vision now possible through MP4 Mux.
Just checked it in "mnt/lg/tvservice/pqldb/dolby/C1_OLED.txt", Tmax = 374 in PictureMode=2 (DoVi Cinema) and only PictureMode=12 has Tmax = 350 entry (not sure which preset/vsvdb this is).aboulfad wrote: ↑Sun Jan 28, 2024 11:52 amThe retrieved (from EDID) VSVDB(Dolby) Tmax is 350 nits which is oddly also a very low value for player-led. I realize my TV is old but just curious what's up !
PS: path for E7 DV OLED firmware fileCode: Select all
06.10.30.01-HE_DTV_W17H_AFADATAA/tvservice-atsc.pak.unsquashfs/mnt/lg/tvservice/pqldb/dolby/OLED_All.txt
Note that these default Tmax values not necessarily mean the peak or 10% patch window peak values, they are set according to the underlining factory 1D LUT in DoVi presets. E.g. on the 55"-77" G2 the gamma 2.2 factory 1D LUT is the same across all SDR and HDR10 presets and they use 990 value to compensate it in HDR10 (and DoVi as well), while you could only measure 920 nits on better days with 10% patch window and only 870 after 2000 hours later.
Re: Dolby Vision now possible through MP4 Mux.
The newer TVs & their associated DV config files do have more details. Thanks for the explanation! There must be somewhere for the E7 where this higher Tmax “compensated” for HDR (HDR10/DV) resides. It’s possible it is baked in the firmware libs and not explicitly specified in config files as in later TVs.chros wrote: ↑Sun Jan 28, 2024 3:46 pm… Note that these default Tmax values not necessarily mean the peak or 10% patch window peak values, they are set according to the underlining factory 1D LUT in DoVi presets. E.g. on the 55"-77" G2 the gamma 2.2 factory 1D LUT is the same across all SDR and HDR10 presets and they use 990 value to compensate it in HDR10 (and DoVi as well), …
[Oppo UDP-203, ATV 4K] —> Anthem MRX-720 —> LG OLED65E7P
Re: Dolby Vision now possible through MP4 Mux.
Is there anything that can play Dolby Vision Profile 7 FEL and MEL from mkv-files with high quality Audio as well (Or coming soon)? Or from the full 4K BLU-RAY Rip [ISO/folder structures]. I don't care for a Menu so that's not needed.
And not via Plex please.
Preferred via Usb-SSD or NAS-Connection Without the NAS needing to do work except transfering the file.
1) Maybe like a self made Mini-PC or so that could do the trick? With certain software or so.
Or
2) Any Media-Player coming soon?
Thx in advance for the info
And not via Plex please.
Preferred via Usb-SSD or NAS-Connection Without the NAS needing to do work except transfering the file.
1) Maybe like a self made Mini-PC or so that could do the trick? With certain software or so.
Or
2) Any Media-Player coming soon?
Thx in advance for the info
Re: Dolby Vision now possible through MP4 Mux.
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
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
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
thanks
Re: Dolby Vision now possible through MP4 Mux.
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.
Thanks.
Re: Dolby Vision now possible through MP4 Mux.
I'm trying to use dovi_tool and follow the workflows to described here. I have a windows 11 machine, but can't for the life of me work out where to put the dovi_tool.exe file so that is addressable by the command line. Can anyone enlighten me?
Re: Dolby Vision now possible through MP4 Mux.
Quick and easy method, download and merge the "Command Prompt Here" registry tweak and merge it into the Windows registry (double click the .reg file or right click it and "Merge"), it will apply system wide, then just right click in the folder where dovi_tool.exe is and "Open Command Prompt Here". Pretty sure this should work in Win 11 too.
Code: Select all
https://www.tenforums.com/tutorials/158472-add-remove-command-prompt-open-here-context-menu-windows-10-a.html
Windows:
Identifying The Correct Title To Rip: Process Monitor Method - GetMPLS Method
Mux/Remux: Set A Subtitle Stream On By Default (Forced)
Identifying The Correct Title To Rip: Process Monitor Method - GetMPLS Method
Mux/Remux: Set A Subtitle Stream On By Default (Forced)
Re: Dolby Vision now possible through MP4 Mux.
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.RESET_9999 wrote: ↑Fri Jan 26, 2024 7:34 pmSame story on my PC monitor(samsung 400nits) with the Energy player.
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?