Dolby Vision now possible through MP4 Mux.

Please post here for issues related to UHD discs
chros
Posts: 102
Joined: Sun Sep 20, 2020 8:36 am

Re: Dolby Vision now possible through MP4 Mux.

Post by chros »

quietvoid wrote:
Sat Jul 24, 2021 6:58 pm
chros wrote:
Sat Jul 24, 2021 6:31 pm
This must be it then, can you share your apk? Thanks
I'm not sure if it's going to be a different package, so backup first..
https://mega.nz/file/MdETXSAR#vPtlIY-nm ... NcRsZLlTyk
Thanks, the .ts file plays back as DoVi with your Kodi build (it's installed as a separate package). (The mkv that I created by dragging the .ts file into recent mkvtoolnix still plays back as hdr10.)
And indeed there's no banding/posterization, so my theory was wrong: Firestick 4k also triggers tv-led DoVi with our 2018 LG.
(That's a different thing that FireOS screwed up audio passthrough from external apps (not streaming ones) completely, and I have occasional stutter with high bitrate streaming profile 5 mp4 files :) )
Last edited by chros on Sun Jul 25, 2021 10:52 am, edited 1 time in total.
chros
Posts: 102
Joined: Sun Sep 20, 2020 8:36 am

Re: Dolby Vision now possible through MP4 Mux.

Post by chros »

RESET_9999 wrote:
Sun Jul 25, 2021 4:48 am
but as you say, hard to tell if its the source or the conversion
Or madvr? :)
quietvoid
Posts: 373
Joined: Sun Apr 19, 2020 4:15 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by quietvoid »

chros wrote:
Sun Jul 25, 2021 10:43 am
(The mkv that I created by dragging the .ts file into recent mkvtoolnix still plays back as hdr10.)
Remuxing from TS is not supported, it won't copy the Dolby Vision config. Only MP4 or straight from the bitstream works currently.
RESET_9999 wrote:
Sun Jul 25, 2021 4:48 am
here are the clips if you want to check them yourself:
https://drive.google.com/file/d/1Lh7zmo ... sp=sharing,
https://drive.google.com/file/d/1Oqkvmz ... sp=sharing

but as you say, hard to tell if its the source or the conversion
Thanks, I'll try to see if I can get anything different by playing with the metadata.
RESET_9999
Posts: 2090
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

chros wrote:
Sun Jul 25, 2021 10:51 am
RESET_9999 wrote:
Sun Jul 25, 2021 4:48 am
but as you say, hard to tell if its the source or the conversion
Or madvr? :)
madVR?
exactly the same static settings were used and dynamic tone mapping was disabled. the difference is NOT caused by madVR.. plus as i said, I'm seeing the same difference in tv-led...

PQ comparison, no madvr involved: https://slow.pics/c/qZ8YCaN2
Last edited by RESET_9999 on Sun Jul 25, 2021 2:51 pm, edited 4 times in total.
Manixx2020beyound
Posts: 127
Joined: Thu Oct 08, 2020 5:19 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by Manixx2020beyound »

quietvoid wrote:
Sun Jul 25, 2021 1:59 pm
chros wrote:
Sun Jul 25, 2021 10:43 am
(The mkv that I created by dragging the .ts file into recent mkvtoolnix still plays back as hdr10.)
Remuxing from TS is not supported, it won't copy the Dolby Vision config. Only MP4 or straight from the bitstream works currently.
RESET_9999 wrote:
Sun Jul 25, 2021 4:48 am
here are the clips if you want to check them yourself:
https://drive.google.com/file/d/1Lh7zmo ... sp=sharing,
https://drive.google.com/file/d/1Oqkvmz ... sp=sharing

but as you say, hard to tell if its the source or the conversion
Thanks, I'll try to see if I can get anything different by playing with the metadata.
So Im wondering the p5 funky colors are not created in post only the final stages of doblyvision encoding
While pulling from the doblyvision 12bit master & xml data simultaneously true SDI
To create a profile 5 FULL color & Rpu
To my knowledge the 12bit master is not in done in doblyvision itcp protocol
& I’m sure the color conversion from 12bit master to p5 produces similar differences form the 12bit master as well.

We should test more uhd p8 conversion
To see what the consistency in the results are,
So far I like the hybrid p8 look, I don’t know how u guys feel about it seems to minus some of doblyvision flaws from their original proces
Last edited by Manixx2020beyound on Sun Jul 25, 2021 3:50 pm, edited 5 times in total.
RESET_9999
Posts: 2090
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

also, it looks like the weird lines (ringing???)mostly in the blue are caused by profile 5 DV decoding because I can see them in TV-LED DV as well while the p8 DV is clean like HDR10.

they dont seem to be present in the p5 source:
p5 clip, no capture no tonemapping VS p8 capture , no tonemapping: https://slow.pics/c/x0YGLSYn


there is also the metadata that are different in the RPU and the BL:

Image
Manixx2020beyound wrote:
Sun Jul 25, 2021 2:34 pm


We should test more uhd p8 conversion
To see what the consistency in the results are
i agree



@quietvoid, i was looking at the rpu and i noticed this, shouldnt the p8 file set to 0 here ?

Image

quietvoid wrote:
Sun Jul 25, 2021 1:59 pm

Remuxing from TS is not supported, it won't copy the Dolby Vision config. Only MP4 or straight from the bitstream works currently.
on my end, the only way I can get a DV MKV with your p5 to p8 conversion is by using Makemkv.

raw hevc with mkvtoolnix = no DV
mp4 dv with mkvtoolnix = no DV
ts DVwith mkvtoolnix = no DV

even when I simply remux the makemkv DV file with mkvtoolnix, i still lose DV metadata.
Last edited by RESET_9999 on Sun Jul 25, 2021 4:09 pm, edited 1 time in total.
chros
Posts: 102
Joined: Sun Sep 20, 2020 8:36 am

Re: Dolby Vision now possible through MP4 Mux.

Post by chros »

quietvoid wrote:
Sun Jul 25, 2021 1:59 pm
Remuxing from TS is not supported, it won't copy the Dolby Vision config. Only MP4 or straight from the bitstream works currently.
Thanks, I'll try out with the raw streams then.
RESET_9999 wrote:
Sun Jul 25, 2021 2:20 pm
madVR? ... the difference is NOT caused by madVR.. plus as i said, I'm seeing the same difference in tv-led...
Oh, I see, I missed that.
RESET_9999
Posts: 2090
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

ragico wrote:
Sat Jul 24, 2021 11:45 am
Hope that @quietvoid will make an easy tool to be used by ignorant people like me as @Yusesope did for his tools.
Thank you.
Perhaps this real content example will help you understand how to do it:



E.G. Disney+ movie Mulan DV web-dl metadata injected into bluray remux


1- extract HDR10 and DV hevc stream (tsmuxer, ffmpeg, mkvextract etc..)

2-
extract and convert profile 5 RPU to 8 with this command:

Code: Select all

dovi_tool.exe -m 3 extract-rpu DV.hevc
3- Sync/edit the rpu to match the HDR10 stream.
For this movie, you have to remove 24 frames before the RPU and add 70 frames at the end
EDIT: tool updated, no more needed to match the framecount. RPU still has to start at the same frame as the bluray remux.

so the JSON file to remove 24 frames will look like this

Code: Select all

{
    "remove": [
        "0-23"
    ]
}
*** how to find the frame difference here


if you had to add 23 frames:

Code: Select all

{
	"duplicate": [
		{
			"source": 0,
			"offset": 0,
			"length": 23
		}
	]
}


4- once the JSON is done, you edit the RPU with this cmd:

Code: Select all

dovi_tool.exe editor -i RPU.bin -j edited.json --rpu-out RPU-edited.bin
5- inject the edited RPU into the HDR10 hevc stream with this cmd:

Code: Select all

dovi_tool.exe inject-rpu -i HDR10.hevc --rpu-in RPU-edited.bin
6- that's it, the injected_output.hevc contains Profile 8 DV metadata

Code: Select all

Format                                   : MPEG-TS
File size                                : 50.9 GiB
Duration                                 : 1 h 55 min
Overall bit rate mode                    : Variable
Overall bit rate                         : 63.3 Mb/s
Maximum Overall bit rate                 : 35.5 Mb/s

Video
ID                                       : 4117 (0x1015)
Menu ID                                  : 1 (0x1)
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                                 : 36
Duration                                 : 1 h 55 min
Bit rate                                 : 58.9 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0 (Type 2)
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.296
Stream size                              : 47.4 GiB (93%)
Writing library                          : ATEME Titan File 3.9.6 (4.9.6.2)        
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.0001 cd/m2, max: 1000 cd/m2

Audio #1
ID                                       : 4352 (0x1100)
Menu ID                                  : 1 (0x1)
Format                                   : MLP FBA AC-3 16-ch
Format/Info                              : Meridian Lossless Packing FBA with 16-channel presentation
Commercial name                          : Dolby TrueHD with Dolby Atmos
Muxing mode                              : Stream extension
Codec ID                                 : 131
Duration                                 : 1 h 55 min
Bit rate mode                            : Variable
Bit rate                                 : 640 kb/s
Maximum bit rate                         : 8 742 kb/s
Channel(s)                               : 8 channels
Channel layout                           : L R C LFE Ls Rs Lb Rb
Sampling rate                            : 48.0 kHz
Frame rate                               : 31.250 FPS (1536 SPF)
Compression mode                         : Lossless
Stream size                              : 527 MiB (1%)
Service kind                             : Complete Main
Number of dynamic objects                : 13
Bed channel count                        : 1 channel
Bed channel configuration                : LFE
Last edited by RESET_9999 on Thu Sep 02, 2021 10:47 pm, edited 7 times in total.
quietvoid
Posts: 373
Joined: Sun Apr 19, 2020 4:15 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by quietvoid »

RESET_9999 wrote:
Sun Jul 25, 2021 2:58 pm
@quietvoid, i was looking at the rpu and i noticed this, shouldnt the p8 file set to 0 here ?
No, even in profile 7 metadata signal_full_range_flag is always set to 1.
What might make a difference is changing both source_min_pq: 7 and source_max_pq: 3079.
Since limited (HDR10) is expected to be 62 and 3696.

RESET_9999 wrote:
Sun Jul 25, 2021 2:58 pm
on my end, the only way I can get a DV MKV with your p5 to p8 conversion is by using Makemkv.

raw hevc with mkvtoolnix = no DV
mp4 dv with mkvtoolnix = no DV
ts DVwith mkvtoolnix = no DV

even when I simply remux the makemkv DV file with mkvtoolnix, i still lose DV metadata.
You should be able to get Dolby Vision config when using MKVToolNix v58 or newer only.
And remuxing MakeMKV files was already copying the config a while ago..

As far as HDR10/ST2086 metadata, I will add a way to set specific values soon hopefully.
RESET_9999
Posts: 2090
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

quietvoid wrote:
Sun Jul 25, 2021 5:01 pm
You should be able to get Dolby Vision config when using MKVToolNix v58 or newer only.
And remuxing MakeMKV files was already copying the config a while ago..
yep, I have the latest version but it doesnt work with the p5 to p8 files. at least on my end.
Manixx2020beyound
Posts: 127
Joined: Thu Oct 08, 2020 5:19 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by Manixx2020beyound »

Bat vs sup p8 vs p5
Bat vs sup p8 vs p5
EABDFDB6-ACC6-4953-8626-A2CB97B98952.jpeg (942.96 KiB) Viewed 16344 times
Looks very close almost identical
Uploading test files
staknhalo
Posts: 161
Joined: Sun Oct 11, 2020 12:05 am

Re: Dolby Vision now possible through MP4 Mux.

Post by staknhalo »

anyone have problems making a p8.1 of cloverfield from p7 with all the tools?

they all just hang and never complete or spit out a 0mb file on this movie even though they work with other movies

Edit: does anyone have the old version of dolby muxer version 1.0? maybe that's my problem with this file I can only find the current 1.0.1 to try
RESET_9999
Posts: 2090
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

Manixx2020beyound wrote:
Sun Jul 25, 2021 6:40 pm
Looks very close almost identical
Uploading test files
looks like you have madVR dynamic clipping active for those pictures manix ...
this frame is interesting though. You can see a small green tint on the building that clearly comes from the HBO p5 (or manix dv to hdr10 settings).

p5 vs p8 vs HDR10 HBO vs HDR10 bluray:
https://slow.pics/c/lTiFdsxj
https://slow.pics/c/IoBZjQMN
ragico
Posts: 258
Joined: Fri Feb 15, 2019 1:09 am

Re: Dolby Vision now possible through MP4 Mux.

Post by ragico »

RESET_9999 wrote:
Sun Jul 25, 2021 4:56 pm
ragico wrote:
Sat Jul 24, 2021 11:45 am
Hope that @quietvoid will make an easy tool to be used by ignorant people like me as @Yusesope did for his tools.
Thank you.
Perhaps this real content example will help you understand how to do it:



E.G. Disney+ movie Mulan DV web-dl metadata injected into bluray remux


1- extract both HDR10 and DV hevc stream

2-
extract and convert profile 5 RPU to 8 with this command:

Code: Select all

dovi_tool.exe -m 3 extract-rpu DV.hevc
3- Sync/edit the rpu to match the frame count of the HDR10 stream.
For this movie, you have to remove 23 frames before the RPU and add 71 frames at the end
so the JSON file would look like this:

Code: Select all

{
    "remove": [
        "0-22"
    ],
    "duplicate": [
        {
            "source": 165632,
            "offset": 165632,
            "length": 71
        }
    ]
}
4- once the JSON is done, you edit the RPU with this cmd:

Code: Select all

dovi_tool.exe editor -i RPU.bin -j edited.json --rpu-out RPU-edited.bin
5- inject the edited RPU into the HDR10 hevc stream with this cmd:

Code: Select all

dovi_tool.exe inject-rpu -i HDR10.hevc --rpu-in RPU-edited.bin
6- that's it, the injected_output.hevc contains Profile 8 DV metadata

Code: Select all

Format                                   : MPEG-TS
File size                                : 50.9 GiB
Duration                                 : 1 h 55 min
Overall bit rate mode                    : Variable
Overall bit rate                         : 63.3 Mb/s
Maximum Overall bit rate                 : 35.5 Mb/s

Video
ID                                       : 4117 (0x1015)
Menu ID                                  : 1 (0x1)
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                                 : 36
Duration                                 : 1 h 55 min
Bit rate                                 : 58.9 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0 (Type 2)
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.296
Stream size                              : 47.4 GiB (93%)
Writing library                          : ATEME Titan File 3.9.6 (4.9.6.2)        
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.0001 cd/m2, max: 1000 cd/m2

Audio #1
ID                                       : 4352 (0x1100)
Menu ID                                  : 1 (0x1)
Format                                   : MLP FBA AC-3 16-ch
Format/Info                              : Meridian Lossless Packing FBA with 16-channel presentation
Commercial name                          : Dolby TrueHD with Dolby Atmos
Muxing mode                              : Stream extension
Codec ID                                 : 131
Duration                                 : 1 h 55 min
Bit rate mode                            : Variable
Bit rate                                 : 640 kb/s
Maximum bit rate                         : 8 742 kb/s
Channel(s)                               : 8 channels
Channel layout                           : L R C LFE Ls Rs Lb Rb
Sampling rate                            : 48.0 kHz
Frame rate                               : 31.250 FPS (1536 SPF)
Compression mode                         : Lossless
Stream size                              : 527 MiB (1%)
Service kind                             : Complete Main
Number of dynamic objects                : 13
Bed channel count                        : 1 channel
Bed channel configuration                : LFE
Thank you for your help. Pls what is JSON and how to use it? And how I know about the frames to be removed/added etc. for a given a film?
RESET_9999
Posts: 2090
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

the json file is a simple text file in which you copy/paste the script of step 3. ( you change the number according to the movies you're syncing)

first, you have to find the frame difference between the two videos. Personally, I use MPC-BE and find the same frame for both videos, press ''control-g'' and calculate the frame number difference. You can navigate frame by frame with ''control left/right arrow'' when the video is paused.

Another method that could be easier for you is to open both videos with staxrip ''video comparison'' (tool/advanced) and navigate to the same frame.
I prefer mpc because you don't have to load the video like you have to do with staxrip. if your pc/gpu is powerful enough you could open two instances of MPC.
then the framecount of both rpu and hdr10 video must match. so you calculate how many frames you have to remove or add at the end of the rpu. (include the frame you added or removed from the start of the rpu) ... just math at this point.

EDIT: it is no more needed to calculate the framecount since the latest update. You only need to calculate the frame difference so the rpu is in sync with the bluray remux.


Image

this is the json for SOUL
Image
Last edited by RESET_9999 on Thu Aug 19, 2021 2:04 am, edited 8 times in total.
Post Reply