Dolby Vision now possible through MP4 Mux.

Please post here for issues related to UHD discs
Chisum04
Posts: 10
Joined: Mon Feb 27, 2023 10:43 am

Re: Dolby Vision now possible through MP4 Mux.

Post by Chisum04 »

To me it looked ok, but that doesn`t say much. I was just able to see the fault in "Gamer" from Lionsgate (HDR flagged as SDR) :D .
Cannikin
Posts: 178
Joined: Tue Aug 18, 2020 11:54 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by Cannikin »

Strange Darling was probably the most RED movie I've ever seen...insanely saturated. But, I assumed this was on purpose: at the start there's a banner on screen "Shot completely on 35mm film". So I assumed the filmmakers really wanted to drive that fact home with some deep, saturated reds everywhere. I didn't see it in the theater so have no reference other than the disc.
Chisum04
Posts: 10
Joined: Mon Feb 27, 2023 10:43 am

Re: Dolby Vision now possible through MP4 Mux.

Post by Chisum04 »

Next authoring failure from Capelight is "Kill", MEL as well. Obviously they are unable to author a synchronized EL for Profile 7.
Chisum04
Posts: 10
Joined: Mon Feb 27, 2023 10:43 am

Re: Dolby Vision now possible through MP4 Mux.

Post by Chisum04 »

Tried different scenarios with "Kill" from Capelight:
1. with MakeMKV to Single Layer P7
2. with DGDemux and Dovi Tool to Single Layer P7
3. with DGDemux and Dovi Tool to P8
4.Extracted BL only and measured scenecuts with madVR

Then I compared the scenecuts of the newly created rpu's with the rpu of the original EL-rpu and got the following results:
1. Scenecuts had up to 300 frames difference to original
2. Scenecuts had 0-6 frames difference to original
3. Exactly as No. 2
4. Same scenecuts as original.

So for me it appears better to create a new rpu with cm analyzer than just changing to Profile 8, not to say using MakeMKV.
What do you think?

Attached the MakeMKV log:

Code: Select all

004007:0010 AV synchronization issues were found in file 'file://D:/Filme/title_t00.mkv' (title #1)
004008:0010 AV sync issue in stream 1 at 0:00:00 with duration of 41ms : audio gap was filled with silence
004047:0010 AV sync issue in stream 0 at 0:00:02.500 : secondary stream video frame timecode differs by +166.666ms
004047:0010 AV sync issue in stream 0 at 0:00:02.708 : secondary stream video frame timecode differs by -125ms
004047:0010 AV sync issue in stream 0 at 0:00:02.708 : secondary stream video frame timecode differs by -166.666ms
004047:0010 AV sync issue in stream 0 at 0:00:02.708 : secondary stream video frame timecode differs by -83.333ms
004047:0010 AV sync issue in stream 0 at 0:00:02.708 : secondary stream video frame timecode differs by +125ms
004047:0010 AV sync issue in stream 0 at 0:00:02.708 : secondary stream video frame timecode differs by +41.666ms
004047:0010 AV sync issue in stream 0 at 0:00:03.208 : secondary stream video frame timecode differs by -41.666ms
004047:0010 AV sync issue in stream 0 at 0:00:03.375 : secondary stream video frame timecode differs by +125ms
004047:0010 AV sync issue in stream 0 at 0:00:03.375 : secondary stream video frame timecode differs by +41.666ms
004047:0010 AV sync issue in stream 0 at 0:00:03.416 : secondary stream video frame timecode differs by -333.333ms
004047:0010 AV sync issue in stream 0 at 0:00:03.416 : secondary stream video frame timecode differs by -375ms
004047:0010 AV sync issue in stream 0 at 0:00:03.416 : secondary stream video frame timecode differs by -291.666ms
004047:0010 AV sync issue in stream 0 at 0:00:03.416 : secondary stream video frame timecode differs by -83.333ms
004047:0010 AV sync issue in stream 0 at 0:00:03.500 : secondary stream video frame timecode differs by +166.666ms
004047:0010 AV sync issue in stream 0 at 0:00:03.625 : secondary stream video frame timecode differs by -166.666ms
004047:0010 AV sync issue in stream 0 at 0:00:03.708 : secondary stream video frame timecode differs by -125ms
004047:0010 AV sync issue in stream 0 at 0:00:03.708 : secondary stream video frame timecode differs by -166.666ms
004047:0010 AV sync issue in stream 0 at 0:00:03.708 : secondary stream video frame timecode differs by -83.333ms
004047:0010 AV sync issue in stream 0 at 0:00:03.708 : secondary stream video frame timecode differs by +125ms
004047:0010 AV sync issue in stream 0 at 0:00:03.708 : secondary stream video frame timecode differs by +41.666ms
004047:0010 AV sync issue in stream 0 at 0:00:04.208 : secondary stream video frame timecode differs by -41.666ms
004047:0010 AV sync issue in stream 0 at 0:00:04.375 : secondary stream video frame timecode differs by +125ms
004047:0010 AV sync issue in stream 0 at 0:00:04.375 : secondary stream video frame timecode differs by +41.666ms
004047:0010 AV sync issue in stream 0 at 0:00:04.416 : secondary stream video frame timecode differs by -333.333ms
004047:0010 AV sync issue in stream 0 at 0:00:04.416 : secondary stream video frame timecode differs by -375ms
004047:0010 AV sync issue in stream 0 at 0:00:04.416 : secondary stream video frame timecode differs by -291.666ms
004047:0010 AV sync issue in stream 0 at 0:00:04.416 : secondary stream video frame timecode differs by -83.333ms
004047:0010 AV sync issue in stream 0 at 0:00:04.500 : secondary stream video frame timecode differs by +166.666ms
004047:0010 AV sync issue in stream 0 at 0:00:04.625 : secondary stream video frame timecode differs by -166.666ms
004047:0010 AV sync issue in stream 0 at 0:00:04.708 : secondary stream video frame timecode differs by -125ms
004047:0010 AV sync issue in stream 0 at 0:00:04.708 : secondary stream video frame timecode differs by -166.666ms
004047:0010 AV sync issue in stream 0 at 0:00:04.708 : secondary stream video frame timecode differs by -83.333ms
004047:0010 AV sync issue in stream 0 at 0:00:04.708 : secondary stream video frame timecode differs by +125ms
004047:0010 AV sync issue in stream 0 at 0:00:04.708 : secondary stream video frame timecode differs by +41.666ms
004047:0010 AV sync issue in stream 0 at 0:00:05.208 : secondary stream video frame timecode differs by -41.666ms
004047:0010 AV sync issue in stream 0 at 0:00:05.375 : secondary stream video frame timecode differs by +125ms
004047:0010 AV sync issue in stream 0 at 0:00:05.375 : too many video frames with invalid timecodes, future messages will be suppressed
004047:0010 AV sync issue in stream 0 at 0:00:05.416 : secondary stream video frame timecode differs by -333.333ms
004047:0010 AV sync issue in stream 0 at 0:00:05.416 : secondary stream video frame timecode differs by -375ms
004047:0010 AV sync issue in stream 0 at 0:00:05.416 : secondary stream video frame timecode differs by -291.666ms
004047:0010 AV sync issue in stream 0 at 0:00:05.416 : secondary stream video frame timecode differs by -83.333ms
THDSF: [truehd @ 0000017448B07030] End of stream indicated.
THDSF: [truehd @ 0000017448B07030] End of stream indicated.
THDSF: [truehd @ 0000017448B07030] End of stream indicated.
FFDEC000: [truehd @ 0000017446862760] End of stream indicated.
FFDEC000: [truehd @ 0000017446862760] End of stream indicated.
FFDEC000: [truehd @ 0000017446862760] End of stream indicated.
004047:0010 AV sync issue in stream 0 at 1:44:53.958 : video stream has 94455 frames with invalid timecodes
005005:0080 1 titles saved
RESET_9999
Posts: 2108
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

I only use tsmuxer for those GER discs and so far they were all in sync if I demux from the original m2ts and extract/convert to P8...
So it sounds like this one would not be ok but I can't check it out since I cannot find the original ISO online yet, I only see REMUX rip.

I'll check it out once I get the complete disc.
darrrkmanxxx
Posts: 59
Joined: Mon Apr 13, 2020 9:55 am

Re: Dolby Vision now possible through MP4 Mux.

Post by darrrkmanxxx »

Hey guys, is there a way to be able to tell if DV works properly on my device or not. I've downloaded a bunch of test files and they all trigger dolby vision but I'm not sure how to interpret them, especially the player/tv-led stuff (chroma weight)
Any guidance/help will be appreciated.
Chisum04
Posts: 10
Joined: Mon Feb 27, 2023 10:43 am

Re: Dolby Vision now possible through MP4 Mux.

Post by Chisum04 »

Regarding the saturation in "Strange Darling" (UK) there is a review on bluray.com citing an interview with Cinematographer Giovanni Ribisi, who "sought an explosive color saturation". I think he found it.
RESET_9999
Posts: 2108
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

darrrkmanxxx wrote:
Tue Dec 17, 2024 9:28 am
Hey guys, is there a way to be able to tell if DV works properly on my device or not. I've downloaded a bunch of test files and they all trigger dolby vision but I'm not sure how to interpret them, especially the player/tv-led stuff (chroma weight)
Any guidance/help will be appreciated.
as long as you see that the RPU levels are used (brightness changes), you're fine.
RESET_9999
Posts: 2108
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

Chisum04 wrote:
Tue Dec 17, 2024 10:53 am
Regarding the saturation in "Strange Darling" (UK) there is a review on bluray.com citing an interview with Cinematographer Giovanni Ribisi, who "sought an explosive color saturation". I think he found it.
Still 10 times more saturated than the SDR grade which doesn't make much sense.

https://slow.pics/c/SA2frBoy
darrrkmanxxx
Posts: 59
Joined: Mon Apr 13, 2020 9:55 am

Re: Dolby Vision now possible through MP4 Mux.

Post by darrrkmanxxx »

RESET_9999 wrote:
Tue Dec 17, 2024 11:52 am
darrrkmanxxx wrote:
Tue Dec 17, 2024 9:28 am
Hey guys, is there a way to be able to tell if DV works properly on my device or not. I've downloaded a bunch of test files and they all trigger dolby vision but I'm not sure how to interpret them, especially the player/tv-led stuff (chroma weight)
Any guidance/help will be appreciated.
as long as you see that the RPU levels are used (brightness changes), you're fine.
thanks, e.g. on Chroma Weight extreme values 0-4095 DV P8 cmv4.0.mp4 I see a lot of chnages, espcially in "Chroma weight 0" - it bascially created dark whole in the beak.
This is desirable, right?
It's on my Philips TV Oled+ internal player.
RESET_9999
Posts: 2108
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

yes
you should try the cmv2.9 version as well, on both of my 2022 TVs (LG , hisense) , it doesn't work.
darrrkmanxxx
Posts: 59
Joined: Mon Apr 13, 2020 9:55 am

Re: Dolby Vision now possible through MP4 Mux.

Post by darrrkmanxxx »

RESET_9999 wrote:
Tue Dec 17, 2024 1:12 pm
yes
you should try the cmv2.9 version as well, on both of my 2022 TVs (LG , hisense) , it doesn't work.
Thank you so much, I'll try that.
Another quick question:
In one of your yt videos (6 different things FEL Dolby Vision Profile 7 Can Do (P7 FEL is not just 12bits)) you mention baked FEL.
How is this done, through MakeMKV?
RESET_9999
Posts: 2108
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

You need an hdmi device that supports FEL decoding like one of these: https://discourse.coreelec.org/t/ce-ng- ... 05x4/50953
Otherwise, re-encoding is required to bake FEL in the BL. (workflow 8-2-1 in dovi_scripts)
darrrkmanxxx
Posts: 59
Joined: Mon Apr 13, 2020 9:55 am

Re: Dolby Vision now possible through MP4 Mux.

Post by darrrkmanxxx »

RESET_9999 wrote:
Tue Dec 17, 2024 1:27 pm
You need an hdmi device that supports FEL decoding like one of these: https://discourse.coreelec.org/t/ce-ng- ... 05x4/50953
Otherwise, re-encoding is required to bake FEL in the BL. (workflow 8-2-1 in dovi_scripts)
got you, I might get my hands on a Dune HD Premier 4K Pro this weekend. According to your docs Dune hase fake-tv led DV.
Is it the case only wehn using andoid or coreelec, too?
How should I verify working tv-led, chroma trims?
RESET_9999
Posts: 2108
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

You need the CoreELEC builds for TV-LED and FEL support.
Post Reply