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

[-QfG-]

What? No.
The JSON is always reencoded into a binary representation which is a lot smaller, then added into the bitstream as SEI.
It's smaller than Dolby Vision in the actual video stream.

Thanks mate, ok here the correct answer. :thanks:

[olinko]

Sorry if this has been answered already but I'm really having a tough time with this.
the goal: make an MP4 Dolby Vision profile 8 file out of a MKV DV Profile 7 file (=because I have an LG OLED which doesn't accept MKV Dolby Vision, only MP4 profile 5 & 8 Dolby Vision).
1) I demuxed the MKV, didn't save the HDR BL or the DoVi EL, saved and converted the RPU to Profile 8.1 HDR, didn't do any cropping
2) I injected the .bin file and muxed it in MKV with the injector (0 delay, no change in FPS, no change in L6 metadata)
(2.1) I used fastflix to remove any VOB subtitles from the original MKV file (while leaving the video untouched) so I can use the MKVTOMP4 script)
3) I used to MKVTOMP4 to output an MP4 file and also changed the audio codec to AC-3 @640k (because LG OLEDs don't support lossless audio formats)

in the end, the video part was fine, the Dolby Vision was working but there was significant audio delay (or is it video delay, the audio is early for a second or two).

the question: Which part am I doing wrong? Is it because I used fastflix to remove the VOB and in the process screwed something up or do I really always need to account for a video delay in the resulting MP4?
If so, I'm assuming I need to fix that at step 2) above and set the delay for X amount of frames. How can I know how many frames I need to delay it by?

EDIT: reading back, I see that I need to use the file info script and get the json file of all the scene cuts... but how does that help me if I can only compare it to the finished MP4 after I've already injected it. What do I do with the JSON file? (I've also installed the DJV software you recommended, but also not sure what I'm supposed to do with it)

[GodzilaAvenger]

From my experience with Fastflix (and FFmpeg in general) the video and audio timestamps can get screwed, so maybe try removing those subtitles with mkvtoolnix and see if you get a better result. You can also use FFmpeg to rewrite the timestamps (with genpts I think).

The scene cut .json file is to check if the Dolby Vision RPU is in sync with the base HDR stream, which I don't think is relevant here. You can use DJV to check if at the frame numbers the .json file says there is a scene cut, there actually is a scene cut. Just note that DJV starts from frame 1, while RPUs start from 0.

[olinko]

From my experience with Fastflix (and FFmpeg in general) the video and audio timestamps can get screwed, so maybe try removing those subtitles with mkvtoolnix and see if you get a better result. You can also use FFmpeg to rewrite the timestamps (with genpts I think).

The scene cut .json file is to check if the Dolby Vision RPU is in sync with the base HDR stream, which I don't think is relevant here. You can use DJV to check if at the frame numbers the .json file says there is a scene cut, there actually is a scene cut. Just note that DJV starts from frame 1, while RPUs start from 0.

Thanks!

[von Suppé]

@olinko

Your source is P7 mkv. That means BL and EL+RPU are interleaved into one videotrack. You want to create P8 DoVi, which would be BL+RPU. There is no EL with P8.
1) I demuxed the MKV, didn't save the HDR BL or the DoVi EL...
The step I'm missing in your workflow is de-interleaving the mkv videotrack to retreive separate BL and EL+RPU streams. Note that only demuxing a P7 DV mkv leaves you with a videotrack that still holds interleaved BL and EL+RPU. So you do have to save BL (and indeed convert RPU into P8). I think this could be reason your file doesn't play right. Please correct me if I'm missing something.
It's only the BL you need to inject the P8-converted RPU into.

[von Suppé]

Not only for @olinko's post, I'm currently more getting into Dolby Vision in mp4. If I'm not mistaken gpac mp4box.exe is the cli-tool used for creating them. First off, can somebody tell me if there'd be an up-to-date (DoVi ready) GUI for it?
I want to learn how to create a P7 dualtrack mp4.
For arguments sake, suppose I have "BL.hevc", "EL.hevc" and "AUDIO.ac3". Can somebody tell me how the basic mp4box cli string would look like for muxing these into a P7-dualtrack mp4?
Another thing. I understand chapters are now possible in mp4. Hope somebody can explain how to add these.

As for -QfG-'s script, when dropping a P7 mkv on the DDVT_MKVTOMP4.cmd, the output remains singletrack duallayer.
For P7 in this script, I'd appreciate the option to be able to choose between singletrack-duallayer and dualtrack-duallayer mp4 output.

[Cr4z33]

OK I wanted to convert a profile 5 DV MKV to profile 8, but DDVT_DEMUXER.cmd says

Video Info = [Resolution = 3840x2020] [Codec = HEVC-10Bit-YUV-4:2:0] [Frames = 193212] [FPS = 23.976]
HDR Info = [n.a.]
No Dolby Vision Profile found.
Abort Operation now.


However if I check the file with MediaInfo it reports it's a Profile 5 Dolby Vision MKV.

General
Unique ID : 327762964378660514121416967602856727062 (0xF694D9CC7158980A84655DE51AA31216)
Complete name : L:\2160p\Gran.mkv
Format : Matroska
Format version : Version 4
File size : 23.6 GiB
Duration : 2 h 14 min
Overall bit rate : 25.1 Mb/s
Frame rate : 23.976 FPS
Encoded date : 2023-10-22 13:49:22 UTC
Writing application : mkvmerge v79.0 ('Funeral Pyres') 64-bit
Writing library : libebml v1.4.4 + libmatroska v1.7.1

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 14 min
Bit rate : 24.8 Mb/s
Width : 3 840 pixels
Height : 2 020 pixels
Display aspect ratio : 1.901
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.133
Stream size : 23.2 GiB (98%)
Language : Italian
Default : Yes
Forced : No

Audio
ID : 2
Format : E-AC-3
Format/Info : Enhanced AC-3
Commercial name : Dolby Digital Plus
Codec ID : A_EAC3
Duration : 2 h 14 min
Bit rate mode : Constant
Bit rate : 384 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 : 369 MiB (2%)
Title : E-AC3 iTA
Language : Italian
Service kind : Complete Main
Default : Yes
Forced : No

Text
ID : 3
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Duration : 2 h 4 min
Bit rate : 2 b/s
Frame rate : 0.013 FPS
Count of elements : 97
Stream size : 2.64 KiB (0%)
Title : FORCED
Language : Italian
Default : No
Forced : No



What can I do now? :confused:

[von Suppé]

I don't see anything referring to Dolby Vision.

If you'd mean the "Main 10@L5@High", this says something about certain parameters with which HEVC coding took place.

FYI this is a MediaInfo example outtake of a P5 DoVi file

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@Main
HDR format : Dolby Vision, Version 1.0, dvhe.05.09, BL+RPU
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision
Duration : 1 min 18 s
Bit rate : 27.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio: 16:9

etc...

[-QfG-]

v0.61.4 Online!

-v0.61.4
*FIXED wrong error message during RPU.bin creating in DEMUXER Script.
*FIXED Sourcecode REMOVER Script.

[Cr4z33]

I don't see anything referring to Dolby Vision.

If you'd mean the "Main 10@L5@High", this says something about certain parameters with which HEVC coding took place.

FYI this is a MediaInfo example outtake of a P5 DoVi file

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@Main
HDR format : Dolby Vision, Version 1.0, dvhe.05.09, BL+RPU
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision
Duration : 1 min 18 s
Bit rate : 27.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio: 16:9

etc...

Yes correct, but then why do I see the movie correctly in a Amazon Fire TV Stick 4K Max with Dolby Vision enabled and purple on any other not Dolby Vision compatible device? :D

I mean isn't this already a sign the movie IS in Dolby Vision? :confused:

[Atlantis]

It obviously was not tagged correctly. If it is Dolby Vision tagged, Media Info says Dolby Vision.

[von Suppé]

On a non-DoVi device the colors being purple/green would indeed suggest the file being DoVi P5. I think @Atlantis has a point. To which I notice both 23.976 framerates where one stating 23976/1000. Which suspects me ffmpeg being involved in flawed container muxing.
Try importing and remuxing the file with MKVToolNix. When muxing Dolby Vision mkv, always force-set "Default duration/FPS" to the proper value; in your case being 24000/1001p. See if the file turns out allright in MediaInfo.
Note that even when tagged properly, a P5 DoVi file always turns up purple/green on a non-DoVi device. P5 offers no fallback video like other profiles because of Dolby's proprietary colorspace being used.

[Atlantis]

Can you convert RPU to HDR10+ metadata and if yes what command to use?

[-QfG-]

Can you convert RPU to HDR10+ metadata and if yes what command to use?

Nope. Only HDR10+ Json to DV RPU.

[Atlantis]

Wow, ok. I thought it should be the other way around! Since HDR10+ is an open standard I thought it should be possible to convert to something open!

[mikraphne]

So, basically, all I am trying to do is pull the DV data from a REMUX, then inject it into an encode. Is this possible? I tried to use DDVT Demuxer to extract the RPU, which was successful. I then tried running the DDVT Injector to inject it into the encode of that same REMUX, but it creates a raw BL+RPU.hevc. I tried bringing that hevc file into MKVToolnix to convert it over to a .mkv and re-add all the audio tracks and subs, but the file looks to still be missing DV info. When I check the Medianfo, it is just the HDR10 data.

Are you able to push the DV RPU into another .mkv and just mux in the DV data, or am I looking at this all wrong?

[SeeMoreDigital]

Are you able to push the DV RPU into another .mkv and just mux in the DV data, or am I looking at this all wrong?Out of interest... What make/model of playback device and display do you have?

[von Suppé]

REMUX is a common phrase and it's possible the file contains Profile 7 DoVi.

I tried to use DDVT Demuxer to extract the RPU, which was successful.

The demuxer script tells you what profile is found after having analyzed the input. If P7 is found, you must set CONVERT RPU to PROFILE 8.1 HDR. Such is used to inject into a single HDR HEVC video. Note that if your recode has no black bars, you also have to set CROP RPU to YES.
I am assuming here the recode has the same frames & framecount as the source.

[mikraphne]

REMUX is a common phrase and it's possible the file contains Profile 7 DoVi.



The demuxer script tells you what profile is found after having analyzed the input. If P7 is found, you must set CONVERT RPU to PROFILE 8.1 HDR. Such is used to inject into a single HDR HEVC video. Note that if your recode has no black bars, you also have to set CROP RPU to YES.
I am assuming here the recode has the same frames & framecount as the source.

Yeah, that part seems to work, and it does export a .RPU to a temp folder. I guess I am confused on how to mix this .RPU into another file. I basically encoded the REMUX down to a smaller size and I am looking to mix the DV data into it.

[Atlantis]

When you watch the file in MediaInfo in basic mode, it does NOT show Dolby Vision. It only shows Dolby Vision if you go into detail in MediaInfo.

Also in Injector you can choose output to MKV.

[mikraphne]

When you watch the file in MediaInfo in basic mode, it does NOT show Dolby Vision. It only shows Dolby Vision if you go into detail in MediaInfo.

Also in Injector you can choose output to MKV.

Yeah, I am looking at Medianfo's Text view. I have one video track with just HDR10, and this was the .hevc that was output from DDTV Injector.

So, I think I am missing something..

[rco133]

Yeah, I am looking at Medianfo's Text view. I have one video track with just HDR10, and this was the .hevc that was output from DDTV Injector.

So, I think I am missing something..

Are you using an old version of mkvtoolnix?

I mux the BL+RPU file with mkvtoolnix frequently, and the resulting mkv file always shows DV and HDR10 info.

Also mediainfo must be recent version.

[-QfG-]

So, basically, all I am trying to do is pull the DV data from a REMUX, then inject it into an encode. Is this possible? I tried to use DDVT Demuxer to extract the RPU, which was successful. I then tried running the DDVT Injector to inject it into the encode of that same REMUX, but it creates a raw BL+RPU.hevc. I tried bringing that hevc file into MKVToolnix to convert it over to a .mkv and re-add all the audio tracks and subs, but the file looks to still be missing DV info. When I check the Medianfo, it is just the HDR10 data.

Are you able to push the DV RPU into another .mkv and just mux in the DV data, or am I looking at this all wrong?

Simply use the DDVT_Hybrid script for this. Open the script and paste the ENCODE in the First HDR Input Video. Second Step: Paste the REMUX now in the second DV Input Video. Check the Menu if all settings are correct. Now mux the DV RPU into the ENCODE. Done.

[Atlantis]

Output as MKV as I always do.

[-QfG-]

Yes. You can always use mkv output.

[von Suppé]

I'm getting confused about MediaInfo here.
Would someone please confirm me either right or wrong in thinking MediaInfo only shows Dolby Vision when in-container, and not in elementary stream? For DoVi, I've always presumed it relied on metadata written on container-level.

[rco133]

I'm getting confused about MediaInfo here.
Would someone please confirm me either right or wrong in thinking MediaInfo only shows Dolby Vision when in-container, and not in elementary stream? For DoVi, I've always presumed it relied on metadata written on container-level.

Mediainfo will not show any DV info until you have muxed the BL+RPU file into a mkv file.

At least that is what it does here.

[von Suppé]

My presumption was correct then. Thanks for confirming, rco133.

[SquallMX]

Is there a way to convert DV level 8.1 to level 7 for Blu-ray?

DDVT Tool can convert DV 8 to 7, but after that what should I do to create a compliant UHD Blu-ray disc with a MEL DV?

[Atlantis]

Is it possible to set the default output to mkv in Injector? I want to avoid to change it every time.

[dkangel]

Is it possible to set the default output to mkv in Injector? I want to avoid to change it every time.

You can change paths with DDVT_OPTIONS.cmd

[Atlantis]

What about output?

[dkangel]

it's the TARGET path

[von Suppé]

DoViBaker adds the EL information into the BL, essentially turning P7 into P8 without fully discarding the EL. At least that's what I think it does based on its GitHub repo.

Hope you don't mind putting this up here, -QfG-

I'm now doing a short test video with dovibaker. Where I understand the avisynth script takes not only video from BL and FEL, but also processes RPU and merge all in one videostream. Do some of you guys already have experience with recoding this? I'm using StaxRip. The avs script seems to play correct but video encoding errors out. I already asked at the StaxRip thread, but up to now haven't received answer so I'll put the screenshots here too. If somebody can see what I'm doing wrong, please tell me.

avs script:
LoadPlugin("F:\dovibaker\DoViBaker_x64.dll")
LoadPlugin("F:\dovibaker\DGDecodeNV.dll")
bl = DGSource("F:\dovibaker\BL.dgi")
el = DGSource("F:\dovibaker\EL.dgi")
SetFilterMTMode("DoViBaker",2)
DoViBaker(bl, el, rpu= "F:\dovibaker\RPU.bin")
ConvertToYUV420(matrix="2020")
ConvertBits(10)
Prefetch(8)


StaxRip error:

https://i.postimg.cc/nLbJdKdB/Stax-Rip-video-encoding-error.png

[Emulgator]

Just guessing... CPU cap/build mismatch ?
I would try a different x265 build.

[von Suppé]

Just guessing... CPU cap/build mismatch ?
I would try a different x265 build.

Took the one from MeGUI. Encoding as I speak. Have to wait for outrcome, but so far so good.

:thanks: Emulgator

[DiscoD]

Is there an extra process to convert hdr10+ to DV?

Never seems to work for me using the demuxer.

https://i.ibb.co/gzdLS1q/hdrtodverror.png (https://ibb.co/gzdLS1q)

[Mark_Venture]

Sorry, I'm a little late here, so I have a question I'm hoping someone would be kind enough to help with.

I have some videos that show:
ID/String : 1
Format/String : HEVC
Format/Info : High Efficiency Video Coding
Format_Profile : Main 10@L5.1@Main
HDR_Format/String : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible
CodecID : hvc1
CodecID/Info : High Efficiency Video CodingMy understanding is that this file should fall back to HDR10 IF the player or TV doesn't support DV. Is that correct?

When playing on my Roku R4670 or my FireTV 4K Max or Roku R4800 on a Sony Non-DV TV using Plex or Kodi (kodi on the firetv only of course), it seems the "fallback" isn't working as I get a greenish tint.

Files like this play fine:
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : hvc1
Codec ID/Info : High Efficiency Video CodingMy understanding (from elsewhere) is that this file is HDR10. Someone also suggested this file might also fall back to SDR if the player doesn't support HDR, but I don't know if that is true.

Am I reading this thread correctly that all I should need to do with the files in the first format, is drop the MP4 files onto the DDVT_REMOVER.cmd set Remove Dolby Vision Meta = Yes, and start. Then the output will be like the second file and should look right?

Is that correct?

[GodzilaAvenger]

DDVT_REMOVER removes the DV metadata, so yes, you should end up with an HDR10 file.

[DiscoD]

Sorry, I'm a little late here, so I have a question I'm hoping someone would be kind enough to help with.

I have some videos that show:
ID/String : 1
Format/String : HEVC
Format/Info : High Efficiency Video Coding
Format_Profile : Main 10@L5.1@Main
HDR_Format/String : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible
CodecID : hvc1
CodecID/Info : High Efficiency Video CodingMy understanding is that this file should fall back to HDR10 IF the player or TV doesn't support DV. Is that correct?

When playing on my Roku R4670 or my FireTV 4K Max or Roku R4800 on a Sony Non-DV TV using Plex or Kodi (kodi on the firetv only of course), it seems the "fallback" isn't working as I get a greenish tint.

Files like this play fine:
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : hvc1
Codec ID/Info : High Efficiency Video CodingMy understanding (from elsewhere) is that this file is HDR10. Someone also suggested this file might also fall back to SDR if the player doesn't support HDR, but I don't know if that is true.

Am I reading this thread correctly that all I should need to do with the files in the first format, is drop the MP4 files onto the DDVT_REMOVER.cmd set Remove Dolby Vision Meta = Yes, and start. Then the output will be like the second file and should look right?

Is that correct?

Make sure the devices are set to HDR only and not to any type of Dolby Vision Playback(LLDV,Automatic,etc) , I have those Roku's and my Files fallback to HDR fine with them. My files are MKV running through plex direct play but they always fallback to HDR.

[ivanb]

Hey guys, just wanted to drop a quick note that the new VTCLab Media Analyzer (https://media-analyzer.pro) can now show RPU headers in HEVC streams. Could be handy in some cases.

https://i.ibb.co/zVpfxZG/Screenshot-2023-11-07-at-16-23-06.png (https://ibb.co/zVpfxZG)

[Grimm]

Hello, I would like to ask you to add the option to set automatic start in the DDVT_OPTIONS file. Because when using demuxer and mkttomp4 I never change anything there anyway and pressing "S" becomes unnecessary
and I would like to ask you to add the option to set the default value for the mux stream in mkv yes/no item in the DDVT_OPTIONS file


Finally, I would like to ask you to add the option to create a file in the same directory as the source file without creating a separate folder. Because then you have to cut the rpu file and paste it into the source file for the injector to work, then when you convert it from mkv to mp4 it creates another folder again and that's how we get 2-3 additional folders....
In my opinion, the rpu file should be created right next to the source file so that you can immediately use the injector without having to deal with copying.

[techdiver]

Hi Guys,

I recently stumbled across this tool and started using it to great success. For the most part I just run DDVT_DEMUXER.cmd on my source file with DV Profile 7 and it extract it as Profile 8 and then I use DDVT_INJECTOR.cmd to combine the base and DV layer back in. Then I use MKVToolNix to combine back into mkv which works great.

I came across an issue I hadn't seen before last night whereby after the initial scan step of DDVT_INJECTOR.cmd I saw the following:


== VIDEO INPUT =========================================================================================================
Filename = [2001.A.Space.Odyssey.1968.2160p.BluRay.REMUX.HEVC.DV.HDR10.DTS-HD.MA.5.1.mkv]
Video Info = [Resolution = 3840x2160] [Codec = HEVC-10Bit-YUV-4:2:0] [Frames = 214088] [FPS = 23.976]
HDR Info = [HDR, Dolby Vision Profile 7 Single Layer]
Borders = [LEFT=0 px], [TOP=208 px], [RIGHT=0 px], [BOTTOM=208 px] [NOT MATCH WITH RPU]

== RPU INPUT ===========================================================================================================
Filename = [RPU.bin]
RPU Info = [DV Profile = 8] [CM Version = 2.9] [Frames = 214088]
Borders = [LEFT=0 px], [TOP=207 px], [RIGHT=0 px], [BOTTOM=207 px] [NOT MATCH WITH VIDEO]


Now I just let the process Start and everything worked fine, but I'm wondering whether I've produced a "bad" file at the end?

[GodzilaAvenger]

It depends on the playback device, since some just discard the border values (L5 metadata, there is considerable conversation about it earlier in this thread which you can use the search tool to find). Also, the values are only off by 1 pixel so it won't be noticeable. It is also sometimes the case that ffmpeg outputs the wrong border values (the upper value).

[techdiver]

It depends on the playback device, since some just discard the border values (L5 metadata, there is considerable conversation about it earlier in this thread which you can use the search tool to find). Also, the values are only off by 1 pixel so it won't be noticeable. It is also sometimes the case that ffmpeg outputs the wrong border values (the upper value).

Thanks very much for the reply. I'm playing them on android tv devices (nvidia shield, Sony OLED, etc).

I'll have a search back through the thread.

Thanks.

[von Suppé]

As @GodzilaAvenger said, there's not to much worry about 1 pixel difference. If the values shown at the videosection were to be correct, that is.

On the other hand, why not just change RPU's L5 values to the exact amount of pixels of video's black borders? This can be done with "EDIT ACTIVE AREA" in the INJECTOR script.
The black borders detection tool can drop a stitch. I always get video's exact border sizes by manually determining them from a (cherry-picked) screenshot in an image editor.

[techdiver]

Cheers for the replies guys.

Another one that I have thought about is adding DV metadata from one release to say a ripped bluray remux. In some cases the duration of each mkv is different as as such I assume that a straight run of the hybrid script would not work correctly. I tested this and saw that for HDR10+ is was saying that since the timestamps are off it will ignore the metadata at the end of the file. But in the case where the difference is at the start of the file is there anything that can be done? I'm assuming no?

[girod2033]

Hello.

When using "DDVT_MKVTOMP4.cmd" in version v0.61.4, information about HDR was lost; in version v0.60 there is no such problem.

https://i.ibb.co/LQnRnj4/Dolby-Vision-Tool-v0-60.png (https://ibb.co/vsZqZy2)

https://i.ibb.co/Z2gh7pr/Dolby-Vision-Tool-v0-61-4.png (https://ibb.co/CP9nD3y)

[dbgt7]

About cropping:

1. There are any Retail Untouched RPUs without cropping informations. The tool says in this case :NO CROPPING INFORMATIONS FOUND. You can leave this RPUs untouched, but it is recommended to set the valid Borders.
I think, that no cropping informations in the RPU is the same how 0 entries. But i have no proof for this statement.

2. IMAX Format: You can do 3 Things:


Set all borders to 0 (this is the way that i use)
Set all borders to the lowest entry (Example: IMAX Scenes Borders 42/42, Normal Scenes Borders 272,272 -> set Borders to 42/42
For Freaks xd - Create a custom.json file and set all borders manually for IMAX / Normal frames. Good Luck :) In this case, don't forget to turn off border manipulation via the tool himself.


3. BORDERLESS VIDEO: If the video is cropped or full 16:9 without Black Bars, set all boreder entries to 0!

In my Tests i have no problems with RPUs with borders entries of 0 with cropped content. BUT ! I have trouble with RPUs with Border entries other than 0 by cropped (borderless) content!

In all cases it is recommended to set the correct borders in the RPU for maximal compatibility with the hardware players.

Does this still applies? So if i have a movie with mixed IMAX and normal widescreen content, do i set borders to 0? DDVT says top and bottom video border are 208 px and rpu top and bottom borders are 207 px.

Do i need to crop video borders to 0? or crop rpu? or both??

[GodzilaAvenger]

Cheers for the replies guys.

Another one that I have thought about is adding DV metadata from one release to say a ripped bluray remux. In some cases the duration of each mkv is different as as such I assume that a straight run of the hybrid script would not work correctly. I tested this and saw that for HDR10+ is was saying that since the timestamps are off it will ignore the metadata at the end of the file. But in the case where the difference is at the start of the file is there anything that can be done? I'm assuming no?

When adding DV or HDR10+ metadata you have to make sure that it's synced with the video stream, otherwise there'll be annoying artifacts (jumps in brightness). This is especially true when using sources from different medium, like digital vs. Blu-ray, as those are usually not synced because of some initial logo or something.

To check if the metadata is synced with the file you can use the FILEINFO script to get the scene cuts (frame numbers where scenes change, frame numbers starting from 0), and match that with the frame number in the actual video (I like using djv, though be careful since in it frame numbers start from 1, not 0). You can then apply the positive or negative delay in the INJECTOR script (I haven't used the HYBRID script but if it has a delay option you can use that too).