Dolby Vision now possible through MP4 Mux.

[realbabilu]

Where do I get the frames that I have to enter?
Thank you very much and greetings.

This is not important if all you want is to extract the RPU. Just enter any number. I'll add an option to skip that in the next version.
By the way, you should update your version of the scripts
we are now at 1.3.1

maybe you can add HDR10 to DV also for mp4remuxed already, split stream to have hevc DV, and mp4remuxed again or not.
I must mp4demuxed or remuxed all to mkv first to get madVR in 1.3.0. but it is ok.
anyway it;s nice script you have. thank you.

just for curiousity: what is --dv-bl-compatible-id 1 or --dv-bl-compatible-id 2 for --dv-profile 8

[RESET_9999]

maybe you can add HDR10 to DV also for mp4remuxed already,

ok will add next version. good suggestion.

just for curiousity: what is --dv-bl-compatible-id 1 or --dv-bl-compatible-id 2 for --dv-profile 8

it tells if the base layer is compatible with SDR/HDR10/HLG/BD or none
but this function doesnt work with the mp4muxer I use.

[Jose1001]

Where do I get the frames that I have to enter?
Thank you very much and greetings.

This is not important if all you want is to extract the RPU. Just enter any number. I'll add an option to skip that in the next version.
By the way, you should update your version of the scripts
we are now at 1.3.1

Thank you very much friend, with version 1.3.1 everything works perfectly, I can now extract the RPU.bin and inject it into another source.
Greetings from Valencia (Spain)

[videoh]

Thanks for bringing DGDemux to our attention. It looks promising but one gotcha is that it has an option to keep the AC3 core with the THD (which we need for X800M2 compatibility) but using that disables the seamless gap processing. So to use the gap processing we'd have to re-add the AC3 core afterwards (presumably re-encoding from the gap-fixed THD), and then remux again so we'd still be at the mercy of tsMuxer bugs

For your information, recent versions of DGDemux have fixed this issue. When demuxing TrueHD, three files are created: *.thd, *.ac3, and *.thd+ac3. All three files have proper gaps correction. Also, the distribution includes a utility called thdmerge, that can be used to combine a *.thd and a *.ac3 into a *.thd+ac3.

I recommend using the latest version 61.

[phbart]

There's a FW update for the x700. Nothing regarding HDR or DV, though.

[rkjnsn]

Is there a good way to spot check whether a DV P5 video base layer and an HDR10 video have the same (or similar enough) light levels for the metadata to be compatible for the hybrid maker functionality?

[Jose1001]

Hello again, I still have a question.
Why is it that when I extract the RPU.bin with the DoVi_tools script from a dvhe.05.06 profile, and add it to a BDRemux with HDR, it creates a dvhe.05.06 BL+RPU + HDR10 compatible profile, and not a dvhe.08.06 profile?
Thanks and regards

[RESET_9999]

Hello again, I still have a question.
Why is it that when I extract the RPU.bin with the DoVi_tools script from a dvhe.05.06 profile, and add it to a BDRemux with HDR, it creates a dvhe.05.06 BL+RPU + HDR10 compatible profile, and not a dvhe.08.06 profile?
Thanks and regards

Because you can't just extract/inject the P5 RPU untouched into an HDR10 video. The rpu must be synced and converted to P8.
Check the tutorial videos.

Is there a good way to spot check whether a DV P5 video base layer and an HDR10 video have the same (or similar enough) light levels for the metadata to be compatible for the hybrid maker functionality?

Personally, I just compare the PQ images. I use MPV to export lossless png.
I might include a drag and drop mode for that in my next version.

Press S to get a lossless PQ PNG

Code: Select all

mpv.com --target-trc=pq --target-prim=bt.2020 --vo=gpu-next --gpu-context=d3d11  --screenshot-format=png --screenshot-png-compression=1 video.mkv

https://github.com/zhongfly/mpv-winbuild/releases

[rkjnsn]

Thanks! That's really helpful. I ended up doing

Code: Select all

mpv --vo=gpu-next --target-trc=pq --target-prim=bt.2020 bd://mpls/800 --bluray-device=[path to blu-ray folder]

in one maximized window and

Code: Select all

mpv --vo=gpu-next --target-trc=pq --target-prim=bt.2020 [path to DV MP4]

in another.

That way I could quickly jump to a few different points in the movie, find the equivalent frame in the other window, and then flip back and forth to verify the brightness was the same.

[Jose1001]

Hello again, I still have a question.
Why is it that when I extract the RPU.bin with the DoVi_tools script from a dvhe.05.06 profile, and add it to a BDRemux with HDR, it creates a dvhe.05.06 BL+RPU + HDR10 compatible profile, and not a dvhe.08.06 profile?
Thanks and regards

Because you can't just extract/inject the P5 RPU untouched into an HDR10 video. The rpu must be synced and converted to P8.
Check the tutorial videos.

Hello good afternoon and thank you very much for answering.
If by sync you mean putting the StaxRip checked difference frames between the HDR and DV track before extracting the RPU.bin from the DV P5, yes I do. If it doesn't sync like this I would be very grateful if you could tell me where I can find the tutorial video, because I have 5 tutorial videos but none for this function, and yesterday I started looking for it in the 449 pages of this post without finding it, thanks

[RESET_9999]

where I can find the tutorial video

they are in my Dovi Scripts google drive folder(in my signature).

[Jose1001]

where I can find the tutorial video

they are in my Dovi Scripts google drive folder(in my signature).

Hello RESET_999 if you mean the 6 videos you have, I already have them, I thought there was another video I hadn't seen to synchronize the RPU.bin.
My problem is that when I extract the RPU.bin from a 5 profile and then add it to a BDRemux, it creates a dvhe05.06 BL+RPU for me, and from what I have read it seems that the problem would be solved with this command:
"ffmpeg -i INPUT.mkv -c:v copy -vbsf hevc_mp4toannexb -f hevc - | dovi_tool -m 3 extract-rpu - -o RPU.bin". As I assume you know the "-m 3" makes a Profile 5 RPU compatible with Profile 8. I have looked for the command in DoVi_Scripts.bat editing it, to add the "-m 3" to the command, but have not found it.
I've been familiar with video editing for several decades, but CMD command lines have never been my thing.That's why I loved the dovi_scrpits and I am very grateful to you
Thank you very much for the help and greetings.

[uhdiznotenough4mee]

Nvm.

[RESET_9999]

Hello RESET_999 if you mean the 6 videos you have, I already have them

Well, if you really watched the video "P5 web-dl to Bluray remux.mkv", then you would know that you're not using the right mode/workflow.

As I said, the "Workflow.1= Read and extract RPU metadata" will export the RPU untouched. You have to use the "MODE.P5= Profile 5 to Profile 8 injector (HYBRID MAKER)"

[rkjnsn]

In case it's useful for anyone else, the following commands can be used to generate a list of shots from an RPU, which can be used to verify synchronization.

First, convert the RPU to json:

Code: Select all

dovi_tool export -i RPU.bin -o RPU.json

Second, use jq to get a list of frames that have the scene_refresh_flag set:

Code: Select all

jq "to_entries | .[] | select(.value.vdr_dm_data.scene_refresh_flag == 1) | .key" RPU.json > RPU-scene-frames.txt

The result with be a file with one (zero-based) frame number per line. Then I'll pick a few throughout the file, look at those frames in the video, and verify that each one is indeed the start of a new shot.