[DDVT Tool] Dolby Vision RPU Demuxing / Injecting / Editing.

[-QfG-]

-v0.46
*Shows RPU/EL Layer Information in Injector (Profile, CM Version, Frames)
*Updated dovi_tool to v1.5.4.

[fkid]

Originally Posted by -QfG-

-v0.46
*Shows RPU/EL Layer Information in Injector (Profile, CM Version, Frames)
*Updated dovi_tool to v1.5.4.

Thank you for continued development. Still see the minor typo on line 371 of INJECTOR.cmd

if "%P4Extract%%MUXINMP4%%HDR10P_exist%"=="TRUEYESYES" set "HEADER_FILENAME=%~n1_[HDR10+ INJECTED].mp4"

should be this I think?

if "%MP4Extract%%MUXINMP4%%HDR10P_exist%"=="TRUEYESYES" set "HEADER_FILENAME=%~n1_[HDR10+ INJECTED].mp4"

[SlimSwan]

Delete this post, my mistake.

[-QfG-]

if "%MP4Extract%%MUXINMP4%%HDR10P_exist%"=="TRUEYESYES" set "HEADER_FILENAME=%~n1_[HDR10+ INJECTED].mp4"

Thank you, i will fix it in the next update.

Original time is 1 h 5 min.
I use latest script.
FPS of video go to 25 I"dont know why?

Have you set "Mux in mkv" to "yes", or have you muxed the file by yourself?
In the last case, in mkvtoolnix by Video in the middle right box set the framerate manually to 24000/1001 and check the "Also Fix Bitstream" Button.
Or simply use the "Mux in MKV" Function from the tool.

EDIT:

-v0.46 Fixed
*Bugfixes

[Blue_MiSfit]

The above is clearly pirated content, and the post has been removed. You must not discuss pirated content on doom9.

[Bioba]

Hello,

I am writing to better understand what this tool does.

I read that it extracts and injects metadata for Dolby Vision, so I could extract the metadata from an untouched video file and then inject it into the same compressed video file?

Thanks to everyone who will explain me better :-)

[Rozin]

How can i replace a profile 5 dolby with its profile 8.1 version. Profile 5 video plays with pink green tint. That's why I'm trying to convert the profile version. Or someone could help me to play profile 5 files without any tints on a dolby profile 5 support less device

[nevcairiel]

You can't really convert profile 5 to profile 8.1, since it has no compatible base layer.

[-QfG-]

DV Profile 5 files uses the ITP Colorange instead of BT.2020. You can't edit this.

[Rozin]

Ok got it.But Is there any way to play profile 5 files on pc. Like tweaking potplayer settings or using madvr. They show pink, green shaded all over. Or do i have to buy $1000 oled tv to play a profile 5?

[quietvoid]

Originally Posted by Rozin

Ok got it.But Is there any way to play profile 5 files on pc. Like tweaking potplayer settings or using madvr. They show pink, green shaded all over. Or do i have to buy $1000 oled tv to play a profile 5?

Use mpv with --vo=gpu-next.

[Rozin]

Originally Posted by quietvoid

Use mpv with --vo=gpu-next.

What does this do? Passthrough profile 5 data or dropping it ? Please explain kind sir for I'm noob

[Rozin]

Originally Posted by nevcairiel

You can't really convert profile 5 to profile 8.1, since it has no compatible base layer.

Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU. This is the dolby encoded into the file . I can't do anything to convert to 8.1? BL means base layer ryt?

[rwill]

Originally Posted by Rozin

Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU. This is the dolby encoded into the file . I can't do anything to convert to 8.1? BL means base layer ryt?

I you manage to decode the Profile 5 to HDR10 and then convert the RPU to match that you could create a Profile 8.1 stream in theory. But chances are high that if your device does not support Profile 5 it also does not support Profile 8.1.

[Bioba]

Hi,

I did a test with a film, I extracted the RPU.bin file with the demuxer, compressed the film, I put the RPU file in the correct folder.

I tried to inject the DV but I get an error and the script closes immediately.

I took a screenshot.

[Rozin]

Originally Posted by rwill

I you manage to decode the Profile 5 to HDR10 and then convert the RPU to match that you could create a Profile 8.1 stream in theory. But chances are high that if your device does not support Profile 5 it also does not support Profile 8.1.

Actually my laptop is Legion 5 pro which has dolby vision specified in the lenovo website and the lap came with dolby app preinstalled with dolby video extensions. I know the display is lcd (But 10bit) and its not the right hardware for dovi, but a license is a license. i dont understand why profile5 is not being decoded. is lenovo selling a 'pseudo' dolby vision license. ?

[fkid]

Originally Posted by Bioba

Hi,

I did a test with a film, I extracted the RPU.bin file with the demuxer, compressed the film, I put the RPU file in the correct folder.

I tried to inject the DV but I get an error and the script closes immediately.

I took a screenshot.

This happens to me from time to time when file or folder has [] or () or some other characters in the path. It may be a limitation of running using explorer context menu? Any idea @-QfG-? I just temporarily rename the video file and/or folder to something short and simple, do the DEMUX/INJECT, then rename file/folder back.

[Bioba]

Originally Posted by fkid

This happens to me from time to time when file or folder has [] or () or some other characters in the path. It may be a limitation of running using explorer context menu? Any idea @-QfG-? I just temporarily rename the video file and/or folder to something short and simple, do the DEMUX/INJECT, then rename file/folder back.

Thanks!

[-QfG-]

Originally Posted by fkid

This happens to me from time to time when file or folder has [] or () or some other characters in the path. It may be a limitation of running using explorer context menu? Any idea @-QfG-? I just temporarily rename the video file and/or folder to something short and simple, do the DEMUX/INJECT, then rename file/folder back.

The problem by this solution is, if the tool renames anything and you close the tool during process, or there is any error during process, the tool don't renamed the folder / Files back.

EDIT:

-v0.47
*INJECTOR supports custom.json files (copy edited custom.json to video source dir).
custom json scripts processed first!
*INJECTOR New function "Match L6 Metadata".
L6 Metadata will be edited for matching HDR stream Metadata.
*INJECTOR creates now a small Logfile by muxing.
*FRAMEINFO shows more informations about the RPU.
*Updated dovi_tool to v1.5.5.

[fkid]

Originally Posted by -QfG-

The problem by this solution is, if the tool renames anything and you close the tool during process, or there is any error during process, the tool don't renamed the folder / Files back.

EDIT:

-v0.47
*INJECTOR supports custom.json files (copy edited custom.json to video source dir).
custom json scripts processed first!
*INJECTOR New function "Match L6 Metadata".
L6 Metadata will be edited for matching HDR stream Metadata.
*INJECTOR creates now a small Logfile by muxing.
*FRAMEINFO shows more informations about the RPU.
*Updated dovi_tool to v1.5.5.

Thank you for the update! Just curious, under what scenario is the new feature used? *INJECTOR New function "Match L6 Metadata".