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

[GodzilaAvenger]

I know that. But my output has HDR10 as a base layer.

Are you sure that the DV is played and interpreted correcrly? Because as QfG said a P5 RPU is not compatible with a BT.2020 (HDR10) base layer. You can inject the RPU into the base layer but the result would be all mangled up as far as brightness and color accuracy are concerned.

What happens if you convert the P5 RPU to a P8 RPU using dovi_tool and inject that into the base layer? Can you spot any differences?

[SeeMoreDigital]

Here, I will upload it.Microsoft 'Windows Security' has detected a virus...

[-QfG-]

But my output has HDR10 as a base layer.

HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : hev1

HDR10 layers and P5 RPUs incompatible. Why not simply transform Profile 5 from RPU to Profile 8 and mux this correct RPU into HDR10 stream?

Also the mp4muxer.exe from @Fuso is clean, false positives from Windows Security:
https://www.virustotal.com/gui/file/39752334b8042eed3fa01311d168c5ab7609e88d8772298c0c49b4d1da47d1b3

Are you sure that the DV is played and interpreted correcrly? Because as QfG said a P5 RPU is not compatible with a BT.2020 (HDR10) base layer.

That says Dolby Laboratories, not QfG :D
https://professionalsupport.dolby.com/s/article/What-is-Dolby-Vision-Profile?language=en_US
page 13

For profile 5:
• VUI information is optional for a profile 5 bitstream. If VUI are present, as of this specification, there
are two options that may be used: 1,2,2,2,0 and 1,9,16,15,0. The values of 2 are compliant with the
VUI definition in ITU-T H.265, where the 2s represent unspecified.
• Within the Dolby Vision context, a profile 5 bitstream must use perceptual quantization with reshaping
for the transfer characteristic, even if setting the transfer characteristic value to 16, uses Dolby Vision
previously proprietary IPT color space (now known as IPT-PQ-C2) for color primaries, uses full range
for range, and, by default, uses center-left siting for chroma sample location.
As defined in SMPTE ST 2128:2023, IPT-PQ-C2, previously a Dolby Vision proprietary color space, is
similar to BT.2100 ICtCp, where I is similar to I, P similar to Cp, and T similar to Ct. As of the date of this
specification, the MPEG Joint Video Experts Team (JVET) working group has standardized the code
point for this previously proprietary color space, also known as IPT-PQ-C2, using code point 15

btw. little bugfix in DDVT:

-v0.64.3a
*FIXED Problems with files that contains "()" in filename.

[matey]

can anyone who had downloaded the mp4muxer from @fuso please let me know which version it is, i will be needed the linux arm64 version so I want to look for & download that version. thanks

[Fuso]

can anyone who had downloaded the mp4muxer from @fuso please let me know which version it is, i will be needed the linux arm64 version so I want to look for & download that version. thanks
MP4muxer version: v1.3.3 (build: Aug 6 2023)


The RPU is P8, I think the files that I "produce" are the so called "fake profile 5".

The source MKV has this info:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : V_MPEGH/ISO/HEVC

1. I demux the video and the audio with tsmuxer.
2. The extracted .hevc and .ec3 files I mux with the following line:
mp4muxer --dv-profile 5 --input-file 1.hevc --input-video-frame-rate 24000/1001 --input-file 1.ec3 --media-lang eng --output-file MOVIE.mp4
pause

The ouptut MOVIE.mp4 looks like that:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision

3. And since files with Codec ID: dvhe can't be playes on a Samsung TVs (I haven't tested other brands), I rename the MOVIE.mp4 to MOVIE.mkv and then use the QfG's script DDVT_MKVTOMP4

powered by quietvoids tools Copyright (c) 2021-2024 QfG

====================================
Dolby Vision Tool MKVtoMP4
====================================


== VIDEO INPUT =========================================================================================================

Filename = [MOVIE.mkv]
Video Info = [Resolution = 3840x1600] [Codec = HEVC-10Bit-YUV-4:2:0] [Frames = 199736] [FPS = 23.976]
HDR Info = [HDR, HDR10+, Dolby Vision Profile 5]

HDR10+ Metadata found.
Dolby Vision Profile 5 found.

Be sure that there no picture based subtitles in your MKV file (PGS or VobSub)
Only textbased subtitles supported.

Please check your Audio Codec and the MP4 specifications. You can switch the
Audio Codec if the source is not compatible with MP4 container.

== MENU ================================================================================================================

1. Audio Codec : [Untouched]

S. START

Change Settings and press [S] to start Converting
Select a Letter 1,[S]tart

and the final ouput MOVIE.mp4:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding

I did try to mux directly to Codec ID: hev1 at step 2, but it didn't work with one of the following (or both) - --dv-bl-compatible-id, --hvc1flag.

I've asked many times before not only on this forum but no one could give me a solution for playing HDR10/HDR10+/DoVi hybrid files on both Samsung and LG (old and new). The whole shenanigans is needed because the old LGs can't play DoVi Profile 8 with Codec ID: hev1, it plays in regular HDR. But when the file is DoVi Profile 5 with Codec ID: hev1 it plays in Dolby Vision, and the same file plays on Samsung TV in HDR10/HDR10+, and if video is real Profile 5 will play in green and purple colors.
So I figured out for myself and so far I haven't noticed anything wrong when playing on all of the TVs.

[GodzilaAvenger]

That's really interesting, thanks for sharing!

[skydalimit]

I've got a Hybrid MP4 movie that contains HDR + DV Profile 7. I need to convert the DV to Profile 8 (keeping HDR). Do I use the Hybrid Script and add the same file twice, or do I need to use the Demuxer script and do extra steps?

[cool advertise]

@-QfG-
Bug (v0.64.3b).
If you try to demux with DDVT_DEMUXER, the single Enhancement Layer of a dolby vision profile 7, and want to convert it to profile 8 (cropping it) you will not get the rpu, but an error.
In previous versions it worked, but now it doesn't.

[mikeq]

So if I look at Jaws remux
MaxCLL in MediaInfo is 1000,259
and from the RPU summary:
RPU content Light Level (L1) is 9977,251
L6 Metadata is 4001,597

Why are these numbers all different?

[-QfG-]

-v0.64.3c
*FIXED Errors in demuxing combinations in DEMUXER script.
*FIXED Some errors in MediaInfo with DL files.
*FIXED L6 Error (L6 SWITCH) in Injector script.
*FIXED If changing FPS with Injector and EL is input, FPS from EL changed, too.
*ADDED Option in Injector script for writing RPU L6 Data as HDR bitstream data.
*Minor Bugfixes.

Bug (v0.64.3b).
If you try to demux with DDVT_DEMUXER, the single Enhancement Layer of a dolby vision profile 7, and want to convert it to profile 8 (cropping it) you will not get the rpu, but an error.
In previous versions it worked, but now it doesn't.

Thanks, fixed in 0.64.3c

[cool advertise]

Bug (v0.64.3b).
If you try to demux with DDVT_DEMUXER, the single Enhancement Layer of a dolby vision profile 7, and want to convert it to profile 8 (cropping it) you will not get the rpu, but an error.
In previous versions it worked, but now it doesn't.
Thanks, fixed in 0.64.3c

I just tried version 0.64.3c but the bug I described is still there.
I get an error instead of rpu.

[matey]

MP4muxer version: v1.3.3 (build: Aug 6 2023)


The RPU is P8, I think the files that I "produce" are the so called "fake profile 5".

The source MKV has this info:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : V_MPEGH/ISO/HEVC

1. I demux the video and the audio with tsmuxer.
2. The extracted .hevc and .ec3 files I mux with the following line:
mp4muxer --dv-profile 5 --input-file 1.hevc --input-video-frame-rate 24000/1001 --input-file 1.ec3 --media-lang eng --output-file MOVIE.mp4
pause

The ouptut MOVIE.mp4 looks like that:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision

3. And since files with Codec ID: dvhe can't be playes on a Samsung TVs (I haven't tested other brands), I rename the MOVIE.mp4 to MOVIE.mkv and then use the QfG's script DDVT_MKVTOMP4

powered by quietvoids tools Copyright (c) 2021-2024 QfG

====================================
Dolby Vision Tool MKVtoMP4
====================================


== VIDEO INPUT =========================================================================================================

Filename = [MOVIE.mkv]
Video Info = [Resolution = 3840x1600] [Codec = HEVC-10Bit-YUV-4:2:0] [Frames = 199736] [FPS = 23.976]
HDR Info = [HDR, HDR10+, Dolby Vision Profile 5]

HDR10+ Metadata found.
Dolby Vision Profile 5 found.

Be sure that there no picture based subtitles in your MKV file (PGS or VobSub)
Only textbased subtitles supported.

Please check your Audio Codec and the MP4 specifications. You can switch the
Audio Codec if the source is not compatible with MP4 container.

== MENU ================================================================================================================

1. Audio Codec : [Untouched]

S. START

Change Settings and press [S] to start Converting
Select a Letter 1,[S]tart

and the final ouput MOVIE.mp4:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding

I did try to mux directly to Codec ID: hev1 at step 2, but it didn't work with one of the following (or both) - --dv-bl-compatible-id, --hvc1flag.

I've asked many times before not only on this forum but no one could give me a solution for playing HDR10/HDR10+/DoVi hybrid files on both Samsung and LG (old and new). The whole shenanigans is needed because the old LGs can't play DoVi Profile 8 with Codec ID: hev1, it plays in regular HDR. But when the file is DoVi Profile 5 with Codec ID: hev1 it plays in Dolby Vision, and the same file plays on Samsung TV in HDR10/HDR10+, and if video is real Profile 5 will play in green and purple colors.
So I figured out for myself and so far I haven't noticed anything wrong when playing on all of the TVs.

thanks for the detailed reply @fuso

just 1 clarification - for playing on old & new LG (2018 & 2023 models) the mp4 got after step 2 is enough to play in DV, right? the additional 2 steps you are doing is only for samsung tv's to play in HDR, correct?

[Fuso]

thanks for the detailed reply @fuso

just 1 clarification - for playing on old & new LG (2018 & 2023 models) the mp4 got after step 2 is enough to play in DV, right? the additional 2 steps you are doing is only for samsung tv's to play in HDR, correct?

If you just want to play DoVi on both old and new models LG only, there's no need for my method. Profile 8 DoVi mp4 with Codec ID set to dvhe is enough. And it's also the official way which meets the Dolby standarts.

@QfG is it possible to implement my way into the script of the DDVT_MKVTOMP4? You can add it to be set as an option [NO/YES] - something like Fake Profile 5 with explanation and also clarify that is expiremental.
I don't know if I'm the only one that needs this but it will be much easier to just convert MKV with HDR10/DoVi P8 to MP4 with HDR10/DoVi "P5" with Codec ID: hev1.
Also can you add an option to select the Codec ID - hev1 or dvhe for P8 mp4? That is what @matey needs in his case I think...

[-QfG-]

Yes, i can add in the next update a "Fake P5 Switch". That's no problem :)
The target file must have - DV Profile 5 Tag (but contains P8) / hev1 instead dvhe / mp4 container, correct?

Bug (v0.64.3b).
If you try to demux with DDVT_DEMUXER, the single Enhancement Layer of a dolby vision profile 7, and want to convert it to profile 8 (cropping it) you will not get the rpu, but an error.
In previous versions it worked, but now it doesn't.


I just tried version 0.64.3c but the bug I described is still there.
I get an error instead of rpu.

Have you this entries in line 1166?

:RPU_EXTRACT
if "!ELSTREAM!"=="" (
set "ELSTREAM=!INPUTSTREAM!"
%WHITE%
echo == DEMUXING ============================================================================================================
echo.
)
%CYAN%
echo Please wait. Demuxing DV Reference Processing Unit...
%WHITE%
"!DO_VI_TOOLpath!" %CROPSTRING% %CONVERTSTRING% extract-rpu "!ELSTREAM!" -o "!TARGET_FOLDER!\%INPUTFILENAMEO%_[RPU].bin"
if exist "!TARGET_FOLDER!\%INPUTFILENAMEO%_[RPU].bin" (
%GREEN%
echo Done.
echo.
) else (
%RED%
echo Error.
set "ERRORCOUNT=1"
echo.
)
goto :eof

if not, please reload the tool.

[Fuso]

Yes, i can add in the next update a "Fake P5 Switch". That's no problem :)
The target file must have - DV Profile 5 Tag (but contains P8) / hev1 instead dvhe / mp4 container, correct?


Yes. The ouput mp4 file must look like this:
Video
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : hev1

[-QfG-]

-v0.64.3d
*ADDED Function in MKVtoMP4 script for creating "fake" Profile 5 files.

Function is only available if input file is Profile 8.

[Fuso]

Function is only available if input file is Profile 8.

Just tried it but it's not working. Output file has lost the HDR10 info:
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU
Codec ID : hev1

and can't be even played.
MPC-HC error:
File Source (Async.)::Output

Media Type 0:
--------------------------
Unknown

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Stream {E436EB83-524F-11CE-9F53-0020AF0BA770}
subtype: Unknown GUID Name {08E22ADA-B715-45ED-9D20-7B87750301D4}
formattype: TIME_FORMAT_NONE {00000000-0000-0000-0000-000000000000}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 1
cbFormat: 0


Media Type 1:
--------------------------
Unknown

AM_MEDIA_TYPE:
majortype: MEDIATYPE_Stream {E436EB83-524F-11CE-9F53-0020AF0BA770}
subtype: TIME_FORMAT_NONE {00000000-0000-0000-0000-000000000000}
formattype: TIME_FORMAT_NONE {00000000-0000-0000-0000-000000000000}
bFixedSizeSamples: 1
bTemporalCompression: 0
lSampleSize: 1
cbFormat: 0




The temp.mp4 file has this info:
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : dvhe
and the temp.mp4 plays fine.

[cool advertise]

Have you this entries in line 1166?
if not, please reload the tool.

Tried the new v0.64.3d version, now everything works correctly, thank you -QfG-.
:)

[Fuso]

Ok, so ffmpeg.exe is the one that breaks the process. I took the older version (from v0.63.1) and now everything is working as it should.

[KarthikTdk]

Hi @All ,
Can any one know where,I can get 1k to 4k resolutions or more than that of YUV video Format of 4:2:0 chroma sampling .
Thank you
Karthik.

[-QfG-]

Ok, so ffmpeg.exe is the one that breaks the process. I took the older version (from v0.63.1) and now everything is working as it should.

wtf... ok, will fix this on the next release :).

EDIT:

Have tried FFMPEG 6 (v0.63.1) and FFMPEG 5, every time same mistake.
Can u give me your FFMPEG please?

[Fuso]

Just tried with the latest ffmpeg build (https://github.com/BtbN/FFmpeg-Builds/releases) (ffmpeg-master-latest-win64-gpl) and it's working. I replaced both ffmpeg.exe and ffprobe.exe.

[-QfG-]

Thanks @Fuso, it works now with your linked FFMPEG build. i have reuploaded v0.63.4d with this build. No version change. Simply reupload.

[cool advertise]

@-QfG-
Still having problems with v0.64.3d.
This time with a dolby vision profile 8, BL+RPU, in an .mkv file. Demuxing like this gives an error and an rpu.bin of 0 bytes.

[-QfG-]

@-QfG-
Still having problems with v0.64.3d.
This time with a dolby vision profile 8, BL+RPU, in an .mkv file. Demuxing like this gives an error and an rpu.bin of 0 bytes.

Will be fixed in next update, Solution is:

Open and edit DDVT_DEMUXER.cmd and change line 1028 to:

if "%BL%%REMHDR10P%%SAVHDR10P%%RPU%"=="NONONONO" (

Also it must likes so in the section:

if "!VIDEO_COUNT!"=="1" (
if "%BL%%REMHDR10P%%SAVHDR10P%%RPU%"=="NONONONO" (
%CYAN%
echo.
echo Please wait. Demuxing EL...

All problems comes now through the implantation of Dual Layer support, sorry for this.

EDIT: Fixed Script as Attach File for Download.

[cool advertise]

EDIT: Fixed Script as Attach File for Download.

It works now, with the new DDVT_DEMUXER.rar attached.
:thanks:

[skydalimit]

I've got a Hybrid MP4 movie that contains HDR + DV Profile 7. I need to convert the DV to Profile 8 (keeping HDR). Do I use the Hybrid Script and add the same file twice, or do I need to use the Demuxer script and do extra steps?

I was able to figure this out. For anyone interested, here are the steps:

1. Run DDVT_DEMUXER on the MP4 file that contains the HDR + DV Profile 7. This will demux the DV P7 and convert it to P8. The output will be an RPU.BIN file.
2. Run DDVT_REMOVER on the MP4 file that contains the HDR + DV Profile 7. Make sure "Remove Dolby Vision" = Yes. This will remove the DV P7. The output will be a "No DV.mp4" file.
3. Run DDVT_INJECTOR on the "No DV.mp4" file and select the RPU.BIN file from the output of step 1. This will remux the "No DV.mp4" with the DV P8 (RPU.BIN), creating a Hybrid HDR+DV P8 mp4.

[-QfG-]

If it is a Dual Layer MP4 with P7 the steps right. If it is a Single Layer P7 MP4, you can skip step (2.), the P8 RPU will overwrite the P7 EL layer.

Do I use the Hybrid Script and add the same file twice, or do I need to use the Demuxer script and do extra steps?

If your MP4 file contains a Single Layer P7, you can do it so, thats the fastest way.

[aussiebro]

Thanks for the application I was able to make a few hybrids out of a few Amazon web dls that are hdr10+.

[-QfG-]

Started test phase for 0.64.4. Many reworks in the scripts.

-v0.64.4* TEST PHASE
*ADDED Function to plot HDR Metadata in FileInfo script (fork from reset_9999)
*REWORKED MANY Scripts

[Fuso]

Is it possible to keep the chapters when converting MKV to MP4?

[-QfG-]

No, mp4 has no chapter support.

[Fuso]

But...

General
Complete name : D:\Torrents\Movies\Conclave.2024.2160p.WEB-DL.DV-TheEqualizer\Conclave.2024.2160p.WEB-DL.DV-TheEqualizer.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/dby1/iso2/mp41)
File size : 13.3 GiB
Duration : 2 h 0 min
Overall bit rate mode : Variable
Overall bit rate : 15.8 Mb/s
Frame rate : 23.976 FPS
Movie name : Conclave (2024) by TheEqualizer
Tagged date : 2024-12-03 10:47:43 UTC
Writing application : Lavf60.3.100
Cover : Yes

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding
Duration : 2 h 0 min
Bit rate : 14.3 Mb/s
Width : 3 832 pixels
Height : 1 600 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.098
Stream size : 12.1 GiB (91%)
Title : Conclave
Language : English
Tagged date : 2024-12-03 10:47:43 UTC
Menus : 10
Codec configuration box : hvcC+dvcC

Audio #1
ID : 3
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : ac-3
Duration : 2 h 0 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 551 MiB (4%)
Title : MVO | TVShows
Language : Russian
Service kind : Complete Main
Default : Yes
Alternate group : 1
Tagged date : 2024-12-03 10:47:43 UTC
Menus : 10

Audio #2
ID : 4
Format : E-AC-3 JOC
Format/Info : Enhanced AC-3 with Joint Object Coding
Commercial name : Dolby Digital Plus with Dolby Atmos
Codec ID : ec-3
Duration : 2 h 0 min
Bit rate mode : Constant
Bit rate : 768 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 662 MiB (5%)
Title : Original | Amazon
Language : English
Service kind : Complete Main
Default : No
Alternate group : 1
Tagged date : 2024-12-03 10:47:43 UTC
Menus : 10
Complexity index : Not present / 16
Number of dynamic objects : 15
Bed channel count : 1 channel
Bed channel configuration : LFE

Text #1
ID : 5
Format : Timed Text
Muxing mode : sbtl
Codec ID : tx3g
Duration : 1 h 59 min
Bit rate mode : Variable
Bit rate : 5 b/s
Frame rate : 0.247 FPS
Stream size : 4.70 KiB (0%)
Title : Forced | Un Chat Andalou
Language : Russian
Default : Yes
Forced : Yes / No
Alternate group : 3
Count of events : 889
Menus : 10

Text #2
ID : 6
Format : Timed Text
Muxing mode : sbtl
Codec ID : tx3g
Duration : 1 h 50 min
Bit rate mode : Variable
Bit rate : 89 b/s
Frame rate : 0.378 FPS
Stream size : 72.4 KiB (0%)
Title : Full | Un Chat Andalou
Language : Russian
Default : No
Forced : No
Alternate group : 3
Count of events : 1255
Menus : 10

Text #3
ID : 7
Format : Timed Text
Muxing mode : sbtl
Codec ID : tx3g
Duration : 1 h 59 min
Bit rate mode : Variable
Bit rate : 10 b/s
Frame rate : 0.201 FPS
Stream size : 9.10 KiB (0%)
Title : Forced | Amazon
Language : English
Default : No
Forced : No
Alternate group : 3
Count of events : 721
Menus : 10

Text #4
ID : 8
Format : Timed Text
Muxing mode : sbtl
Codec ID : tx3g
Duration : 1 h 50 min
Bit rate mode : Variable
Bit rate : 47 b/s
Frame rate : 0.324 FPS
Stream size : 38.4 KiB (0%)
Title : Full | Amazon
Language : English
Default : No
Forced : No
Alternate group : 3
Count of events : 1074
Menus : 10

Text #5
ID : 9
Format : Timed Text
Muxing mode : sbtl
Codec ID : tx3g
Duration : 1 h 53 min
Bit rate mode : Variable
Bit rate : 55 b/s
Frame rate : 0.386 FPS
Stream size : 45.5 KiB (0%)
Title : SDH | Amazon
Language : English
Default : No
Forced : No
Alternate group : 3
Count of events : 1317
Menus : 10

Menu #1
ID : 10
Format : Timed Text
Codec ID : text
Duration : 2 h 0 min
Language : English
Bit rate mode : CBR
Menu For : 1,3,4,5,6,7,8,9
00:00:00.000 : Chapter 01
00:04:47.620 : Chapter 02
00:09:35.492 : Chapter 03
00:17:46.608 : Chapter 04
00:25:48.173 : Chapter 05
00:33:13.576 : Chapter 06
00:41:42.752 : Chapter 07
00:49:17.791 : Chapter 08
00:55:01.843 : Chapter 09
01:01:06.249 : Chapter 10
01:07:25.795 : Chapter 11
01:12:54.624 : Chapter 12
01:18:13.985 : Chapter 13
01:26:02.537 : Chapter 14
01:29:51.725 : Chapter 15
01:35:00.909 : Chapter 16
01:41:31.633 : Chapter 17
01:46:22.382 : Chapter 18
01:50:43.268 : Chapter 19
01:53:41.363 : Chapter 20
Bit rate mode : Constant

Menu #2
00:00:00.000 : Chapter 01
00:04:47.620 : Chapter 02
00:09:35.492 : Chapter 03
00:17:46.608 : Chapter 04
00:25:48.173 : Chapter 05
00:33:13.576 : Chapter 06
00:41:42.752 : Chapter 07
00:49:17.791 : Chapter 08
00:55:01.843 : Chapter 09
01:01:06.249 : Chapter 10
01:07:25.795 : Chapter 11
01:12:54.624 : Chapter 12
01:18:13.985 : Chapter 13
01:26:02.537 : Chapter 14
01:29:51.725 : Chapter 15
01:35:00.909 : Chapter 16
01:41:31.633 : Chapter 17
01:46:22.382 : Chapter 18
01:50:43.268 : Chapter 19
01:53:41.363 : Chapter 20

[-QfG-]

-v0.64.4 Online
*XML Support (Injector / Demuxer)
*REWORKED MANY Scripts
*ADDED Function to plot HDR Metadata in FileInfo script (fork from reset_9999)
*ADDED Mass Converting with MKVtoMP4 (Folder Support)
*UPDATED Python to v3.13
*Minor Bugfixes.

If you using the Shell Extensions please reinstall the extensions via Options script, for MKVtoMP4 folder support .

[tijgert]

Hello all,

Running into a new situation here:
Source UHD with DV is 3840x1600 (letterboxed), destination UHD that needs DV is 3840x2160 (black bars).
When injecting the RPU it says video input matches with output RPU but RPU input does NOT match with video.

I also read that:
Originally Posted by Boulder View Post
My assumption is that whenever the final result doesn't have any black borders, you use the cropping option for the RPU.

So, does that mean that since the final result here WILL have black borders I do NOT need to crop?
I 'fear' the RPU will not be applied to the middle where the picture is but starts at the top so that the black bars will get DV.
Or WILL it be centered?

edit:
Made a json file where it specifies the crop, but it doesn't take over the values.

https://tweakers.net/fotoalbum/image/dS4WxK1AENkxiLXKpblnIztl.jpg

[-QfG-]

-v0.64.5
ADDED -Injector- Support for Custom JSON files without injecting DV / HDR10+. Not supported for DV Profile 7. Skip DV and HDR10+ Input for processing JSON files directly.
FIXED -Options- Errors with Shell Extensions and W11.
FIXED -Options- Wrong TAB entry in DDVT_Options.ini [Line JSON_PROCESS] (if you have the TAB bug, please delete the complete line in ini file and save options again).
FIXED -MediaInfo- Removed HDR Metadata Tab for non HDR files.
*UPDATED mkvtoolnix to v 89.0.0.0.
*Minor Bugfixes.

Source UHD with DV is 3840x1600 (letterboxed), destination UHD that needs DV is 3840x2160 (black bars).
When injecting the RPU it says video input matches with output RPU but RPU input does NOT match with video.

This is correct. Your SOURCE (INPUT) RPU has letterboxes 0,0,0,0 inside. Your SOURCE (INPUT) Video is letterboxed 0,280,0,280. SOURCE RPU and SOURCE VIDEO = NOT MATCH!
Your OUTPUT RPU has corrected AA with 0,280,0,280. The some borders how your INPUT VIDEO file has = OUTPUT RPU and INPUT VIDEO = MATCH

Simply press now [S] and the RPU will be fixed automatically during the injecting process. You need NO JSON file for setting cropping values for all frames in RPU.
After muxing you can proof the file with DDVT_MediaInfo and check the borders in RPU.

[tijgert]

After muxing you can proof the file with DDVT_MediaInfo and check the borders in RPU.

Excellent, it worked. I am getting a greater understanding of these matters. Thanks.

[Mickkk]

Perhaps it has been already discussed, but I cannot solve the following problem. I have a hybrid MKV video (DV + HDR10) 3840X1608. My old LG C8 shows the file in HDR10 with black bars - all OK. So to play DV, I converted the file into m2ts - now my LG shows it in DV, all OK, BUT the top & bottom bars are no longer black, they are grayish.

So I extracted the RPU & adjusted the top/bottom borders manually to 276 & injected them back into the video. Nothing changed - the bars are still not black, but grey.
Is there a solution? Please help.

Forgot to mention: I play the video with OPPO clone

BTW Great tool! Many thanks!!

[Mickkk]

I have an older LG TV, and the only way I could play a DV was to convert with tsmuxer, but the "seeking" during playback was horrible.

But then I found an app that was my "Saviour", and it's not DDVT.




Can you send me the name of the app please? I too struggle with my older LG TV

[Fuso]

Can you send me the name of the app please? I too struggle with my older LG TV

What's the model of your LG?
You can use the DDVT_MKVTOMP4 with Option 2 (Fake P5) enabled.

[Mickkk]

What's the model of your LG?
You can use the DDVT_MKVTOMP4 with Option 2 (Fake P5) enabled.

LG C8. I have tried the Fake P5 option also. To my surprise it did not work, I just get a black screen with sound. Somebody in this thread stated that old LG's have problems with new MP4 containers.

Converting MKV to M2TS works fine for me for files 3840x2160. If the video stream is "thinner" (like 3840X1600) then I get grey (not black) bars - this is very annoying if watching in a dark room. I understand that it is happening because DV metadata is not limited just to the video size, it is applied to the whole screen. I want to find a way to change this

[JackNicko]

Hello all,

Running into a new situation here:
Source UHD with DV is 3840x1600 (letterboxed), destination UHD that needs DV is 3840x2160 (black bars).
When injecting the RPU it says video input matches with output RPU but RPU input does NOT match with video.

I also read that:
Originally Posted by Boulder View Post
My assumption is that whenever the final result doesn't have any black borders, you use the cropping option for the RPU.

So, does that mean that since the final result here WILL have black borders I do NOT need to crop?
I 'fear' the RPU will not be applied to the middle where the picture is but starts at the top so that the black bars will get DV.
Or WILL it be centered?

edit:
Made a json file where it specifies the crop, but it doesn't take over the values.



Hey, I have a question about your post. I sent you a private message about this. I would appreciate an answer! Thx.

[-QfG-]

Perhaps it has been already discussed, but I cannot solve the following problem. I have a hybrid MKV video (DV + HDR10) 3840X1608. My old LG C8 shows the file in HDR10 with black bars - all OK. So to play DV, I converted the file into m2ts - now my LG shows it in DV, all OK, BUT the top & bottom bars are no longer black, they are grayish.

So I extracted the RPU & adjusted the top/bottom borders manually to 276 & injected them back into the video. Nothing changed - the bars are still not black, but grey.
Is there a solution? Please help.

Forgot to mention: I play the video with OPPO clone

BTW Great tool! Many thanks!!

The active Area 0,276,0,276 is wrong if the input video is cropped and has no borders. set the Active Area to 0,0,0,0 in this case. Active borders must set for the real resolution of video file, not the aspect ratio. Also the OPPO and his clone have problems with cropped content. I recommend Ugoos AM6b+ / Dune Homatics 4K R Plus Media Player with CoreELEC CPM builds. You have full FEL support with this Media Box and no problems with cropped content. The player plays MKV P7 FEL Single layer files without re-containering, too.

So, does that mean that since the final result here WILL have black borders I do NOT need to crop?

It's easy, simply ignore resolution/AR from DV input file. Important is the resolution and the black borders of the HDR target file where you inject the RPU. If your target file is an UHD with 3840x2160 and has 276px Black borders Top/Bottom and your input file with the DV content has 3840x1600 without black borders, set the Active Area to 0,276,0,276.

[-QfG-]

-v0.65.2
-FIXED Errors with FFMPEG and bitstream demuxing/pipelining (clipping and wrong colors on some movies)
*Minor Bugfixes.

[pejok]

Hi all,

I get below errors when using HYBRID script. Last version without this errors is 0.64.2.
There are no errors with exact same video files in DEMUXER or INJECTOR -> It demux and inject without any issues and final video file is OK.
It occurs with every video file, when i try to use HYBRID script. Source video file for demuxing has both RPU and HDR10+ .json as well.
Where should be the problem or what should i try to set up/change on my side?

OS: Win 11 Pro, 24H2

Thank you very much. Excellent tool :)

[-QfG-]

@pejok Problem fixed, please download this file and overwrite the hybrid script with this file:
https://github.com/DonaldFaQ/DDVT/blob/Scripts/DDVT_HYBRID.cmd

[pejok]

@-QfG- thank you, no errors so far :) but maybe last bug as i noticed is, while testing and trying to do hybrid with HDR10 only file + DV&HDR10+ file:

- tool correctly fetch all info about the files
- i have set also to inject HDR10+
- start the script -> DV extracted -> HDR10+ -> Scenecuts fixed -> DV injected -> muxing final video file
- injecting of HDR10+ completely ignored
- final video file contains DV + HDR10 only (not HDR10+)

[-QfG-]

You're right, sorry forgot to process this switch. Fixed now, simply update the script.
https://github.com/DonaldFaQ/DDVT/blob/Scripts/DDVT_HYBRID.cmd

[pejok]

Perfectly working again. THANK YOU ! :)

[Fuso]

LG C8. I have tried the Fake P5 option also. To my surprise it did not work, I just get a black screen with sound. Somebody in this thread stated that old LG's have problems with new MP4 containers.

Converting MKV to M2TS works fine for me for files 3840x2160. If the video stream is "thinner" (like 3840X1600) then I get grey (not black) bars - this is very annoying if watching in a dark room. I understand that it is happening because DV metadata is not limited just to the video size, it is applied to the whole screen. I want to find a way to change this

Strange. I have an LG B8 and the files play without any issue when they are converted to "fake" Profile 5.