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

rco133 · 28th October 2023, 16:58

Quote:

Originally Posted by 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.

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é · 28th October 2023, 18:55

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

SquallMX · 30th October 2023, 00:04

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 · 30th October 2023, 17:19

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

dkangel · 31st October 2023, 10:44

Quote:

Originally Posted by Atlantis

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 · 31st October 2023, 16:45

What about output?

dkangel · 1st November 2023, 11:16

it's the TARGET path

von Suppé · 1st November 2023, 11:55

Quote:

Originally Posted by GodzilaAvenger

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:

Code:

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:

Emulgator · 1st November 2023, 19:06

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

von Suppé · 2nd November 2023, 06:31

Quote:

Originally Posted by Emulgator

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.

Emulgator

DiscoD · 5th November 2023, 18:04

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

Never seems to work for me using the demuxer.

Mark_Venture · 6th November 2023, 03:28

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:

Code:

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 Coding

My 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:

Code:

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 Coding

My 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 · 6th November 2023, 08:25

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

DiscoD · 7th November 2023, 05:38

Quote:

Originally Posted by 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:

Code:

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 Coding

My 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:

Code:

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 Coding

My 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 · 7th November 2023, 10:38

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.

Grimm · 12th November 2023, 21:08

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 · 23rd November 2023, 14:53

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:

Code:

 == 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 · 24th November 2023, 07:13

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 · 24th November 2023, 10:27

Quote:

Originally Posted by 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).

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é · 25th November 2023, 09:11

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.

1st November 2023, 19:06	#789 \| Link
Emulgator Big Bit Savings Now ! Join Date: Feb 2007 Location: close to the wall Posts: 1,656	Just guessing... CPU cap/build mismatch ? I would try a different x265 build. __________________ "To bypass shortcuts and find suffering...is called QUALity" (Die toten Augen von Friedrichshain) "Data reduction ? Yep, Sir. We're that issue working on. Synce invntoin uf lingöage..."

6th November 2023, 03:28	#792 \| Link
Mark_Venture Registered User Join Date: Jan 2010 Posts: 234	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: Code: 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 Coding My 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: Code: 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 Coding My 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?

12th November 2023, 21:08	#796 \| Link
Grimm Registered User Join Date: Jun 2022 Posts: 4	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. Last edited by Grimm; 12th November 2023 at 21:32.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

28th October 2023, 18:55	#782 \| Link
von Suppé Registered User Join Date: Dec 2013 Posts: 639	My presumption was correct then. Thanks for confirming, rco133.

30th October 2023, 00:04	#783 \| Link
SquallMX Special SeeD Join Date: Nov 2002 Location: Mexico Posts: 340	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?

30th October 2023, 17:19	#784 \| Link
Atlantis Registered User Join Date: Feb 2002 Posts: 775	Is it possible to set the default output to mkv in Injector? I want to avoid to change it every time.

31st October 2023, 16:45	#786 \| Link
Atlantis Registered User Join Date: Feb 2002 Posts: 775	What about output?

1st November 2023, 11:16	#787 \| Link
dkangel Registered User Join Date: Jun 2023 Posts: 12	it's the TARGET path

5th November 2023, 18:04	#791 \| Link
DiscoD Registered User Join Date: Aug 2022 Posts: 7	Is there an extra process to convert hdr10+ to DV? Never seems to work for me using the demuxer.

6th November 2023, 08:25	#793 \| Link
GodzilaAvenger Registered User Join Date: Jul 2022 Posts: 126	DDVT_REMOVER removes the DV metadata, so yes, you should end up with an HDR10 file.

7th November 2023, 10:38	#795 \| Link
ivanb Registered User Join Date: May 2023 Posts: 27	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.

24th November 2023, 07:13	#798 \| Link
GodzilaAvenger Registered User Join Date: Jul 2022 Posts: 126	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).

25th November 2023, 09:11	#800 \| Link
von Suppé Registered User Join Date: Dec 2013 Posts: 639	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.