Page 562 of 756
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 9:10 am
by Trees
quietvoid wrote: Fri Jun 09, 2023 11:37 am
Trees wrote: Thu Jun 08, 2023 8:25 pm
Quick question, when using dovi_tool mode 3 to extract the RPU from a P5 file, is any from the RPU data lost? I'm asking because the other day, I read someone claiming both chroma and luma data being lost when using mode 3; apparently, only dynamic metadata is being carried over from the P5 files to the P8.1 files.
Is this true? Just curious.
Yes, the mapping metadata contained in profile 5 is not usable in profile 8.1.
It wouldn't make sense to keep it.
Very interesting. I never knew extracting the RPU and injecting it in to a remux was a lossy progress. I thought it truly was the best of both worlds. It seems P5 DV is still absolute best, as it's in the IPTPQc2 colour space and includes both chroma and luma mapping; it's just lacking the bit rate of a Blu-ray.
Which begs the next question; seeing as the IPTPQc2 has been reverse engineered by gifted folk, as it can be decoded by MPV to be properlt played back, is it possible to convert the Blu-ray high bit-rate stream to the IPTPQc2 colour space and inject the lossless RPU to
truly get best of both worlds?
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 11:13 am
by quietvoid
Trees wrote: Tue Jun 20, 2023 9:10 amVery interesting. I never knew extracting the RPU and injecting it in to a remux was a lossy progress. I thought it truly was the best of both worlds. It seems P5 DV is still absolute best, as it's in the IPTPQc2 colour space and includes both chroma and luma mapping; it's just lacking the bit rate of a Blu-ray.
Which begs the next question; seeing as the IPTPQc2 has been reverse engineered by gifted folk, as it can be decoded by MPV to be properlt played back, is it possible to convert the Blu-ray high bit-rate stream to the IPTPQc2 colour space and inject the lossless RPU to
truly get best of both worlds?
Why do you believe the metadata is any better for quality? It's literally only required to decode the colours into regular PQ/BT.2020.
It doesn't improve the quality at all on playback. The process is only lossy in that it loses the original metadata, the quality is unaffected.
And any reencoding of a Blu-ray into IPT would be worse as transcoding is lossy.
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 1:40 pm
by TheEqualizer
Good afternoon, tell me what sequence of script points you need to use to analyze the finished mkv file, you need to get a screenshot similar to what is created automatically when converting HDR10+ to DV, is it possible? I can't find a similar scenario, thank you
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 2:03 pm
by RESET_9999
TheEqualizer wrote: Tue Jun 20, 2023 1:40 pm
Good afternoon, tell me what sequence of script points you need to use to analyze the finished mkv file, you need to get a screenshot similar to what is created automatically when converting HDR10+ to DV, is it possible? I can't find a similar scenario, thank you
To plot DV (graph screenshot), the workflow is 6-2-4.
For just a quick info summary about the RPU metadata in any file: 2-3
to check the metadata of any frame, input an RPU in: 2-3 or 2-2
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 2:07 pm
by TheEqualizer
RESET_9999 wrote: Tue Jun 20, 2023 2:03 pm
To plot DV (graph screenshot), the workflow is 6-2-4.
For just a quick info summary about the RPU metadata in any file: 2-3
to check the metadata of any frame, input an RPU in: 2-3 or 2-2
Thank you very much
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 2:13 pm
by lolipeid47
quietvoid wrote: Tue Jun 20, 2023 11:13 am
Trees wrote: Tue Jun 20, 2023 9:10 amVery interesting. I never knew extracting the RPU and injecting it in to a remux was a lossy progress. I thought it truly was the best of both worlds. It seems P5 DV is still absolute best, as it's in the IPTPQc2 colour space and includes both chroma and luma mapping; it's just lacking the bit rate of a Blu-ray.
Which begs the next question; seeing as the IPTPQc2 has been reverse engineered by gifted folk, as it can be decoded by MPV to be properlt played back, is it possible to convert the Blu-ray high bit-rate stream to the IPTPQc2 colour space and inject the lossless RPU to
truly get best of both worlds?
Why do you believe the metadata is any better for quality? It's literally only required to decode the colours into regular PQ/BT.2020.
It doesn't improve the quality at all on playback. The process is only lossy in that it loses the original metadata, the quality is unaffected.
And any reencoding of a Blu-ray into IPT would be worse as transcoding is lossy.
Excellent answer thx

Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 2:46 pm
by TheEqualizer
RESET_9999 wrote: Tue Jun 20, 2023 2:03 pm
To plot DV (graph screenshot), the workflow is 6-2-4.
For just a quick info summary about the RPU metadata in any file: 2-3
to check the metadata of any frame, input an RPU in: 2-3 or 2-2
Unfortunately an error appears and the plot is not created
6-2-4
https://ibb.co/zHTqKMN
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 2:58 pm
by RESET_9999
looks like your file doesn't have DV or you're using an old dovi_tool(not scripts) version.
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 3:16 pm
by TheEqualizer
RESET_9999 wrote: Tue Jun 20, 2023 2:58 pm
looks like your file doesn't have DV or you're using an old dovi_tool(not scripts) version.
Is this the latest version?
https://github.com/quietvoid/dovi_tool/ ... /tag/2.0.3
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 3:17 pm
by RESET_9999
yes but if your tool pack had the old dovi_tool, it means many other tools are missing or outdated... the latest version of the scripts will not work properly.
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 3:43 pm
by TheEqualizer
RESET_9999 wrote: Tue Jun 20, 2023 3:17 pm
yes but if your tool pack had the old dovi_tool, it means many other tools are missing or outdated... the latest version of the scripts will not work properly.
Yes, it already works, I replaced dovi-tools in the tool package, tell me, and a more recent version of the package can be obtained by a link in private messages, since I realized that you no longer publish to the public
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 6:04 pm
by valington
RESET_9999 wrote: Tue Jun 20, 2023 2:03 pm
TheEqualizer wrote: Tue Jun 20, 2023 1:40 pm
Good afternoon, tell me what sequence of script points you need to use to analyze the finished mkv file, you need to get a screenshot similar to what is created automatically when converting HDR10+ to DV, is it possible? I can't find a similar scenario, thank you
To plot DV (graph screenshot), the workflow is 6-2-4.
For just a quick info summary about the RPU metadata in any file: 2-3
to check the metadata of any frame, input an RPU in: 2-3 or 2-2
DUNE HD REAL VISION shows DT DL with full blu ray 4k dolby vision and ST DL with bdremux mkv 7 profile dolby vision is it true dolvy visiob or not ?
Re: Dolby Vision now possible through MP4 Mux.
Posted: Tue Jun 20, 2023 8:37 pm
by RESET_9999
valington wrote: Tue Jun 20, 2023 6:04 pm
DUNE HD REAL VISION shows DT DL with full blu ray 4k dolby vision and ST DL with bdremux mkv 7 profile dolby vision is it true dolvy visiob or not ?
It's true DV but without FEL support meaning only the dynamic metadata in the RPU is used.
Re: Dolby Vision now possible through MP4 Mux.
Posted: Thu Jun 22, 2023 4:25 am
by MartyMcNuts
@RESET_9999,
I am having trouble with the script (using 1.8.3) 2-2 to extract the RPU. I've done this heaps of times over the past couple of weeks, mind you, this is the first attempt since a major Windows 11 update the other day. I haven't changed anything. Here is the log.
Input #0, mpegts, from 'F:\Movies\The_Transformers_The_Movie\BDMV\STREAM\00006.m2ts':
Duration: 01:25:00.83, start: 600.000000, bitrate: 97757 kb/s
Program 1
Stream #0:0[0x1011]: Video: hevc (Main 10) (HDMV / 0x564D4448), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x2160 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn
Stream #0:1[0x1100]: Audio: dts (DTS-HD MA) ([134][0][0][0] / 0x0086), 48000 Hz, stereo, s32p (24 bit)
Stream #0:2[0x1101]: Audio: dts (DTS-HD MA) ([134][0][0][0] / 0x0086), 48000 Hz, 5.1(side), s32p (24 bit)
Stream #0:3[0x1102]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, stereo, fltp, 192 kb/s
Stream #0:4[0x12a0]: Subtitle: hdmv_pgs_subtitle ([144][0][0][0] / 0x0090)
Stream #0:5[0x12a1]: Subtitle: hdmv_pgs_subtitle ([144][0][0][0] / 0x0090)
Stream #0:6[0x1015]: Video: hevc (Main 10) (HDMV / 0x564D4448), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn
Automatic encoder selection failed for output stream #0:0. Default encoder for format hevc (codec none) is probably disabled. Please choose an encoder manually.
Error selecting an encoder for stream 0:0
Error: No frames parsed!
Error: No NALU start codes found in the file. Maybe not a valid RPU?
Error: No NALU start codes found in the file. Maybe not a valid RPU?
FINDSTR: Cannot open H:\DoVi_Scripts_1.8.3_TOOLS\TEMP_folder7\test.xml
Error: No NALU start codes found in the file. Maybe not a valid RPU?
Error: No NALU start codes found in the file. Maybe not a valid RPU?
Parsing RPU file...
Error: No NALU start codes found in the file. Maybe not a valid RPU?
Parsing RPU file...
Error: No NALU start codes found in the file. Maybe not a valid RPU?
L5 Left offset: L5_is_missing_you_should_edit...
L5 Right offset: L5_is_missing_you_should_edit...
L5 Top offset: L5_is_missing_you_should_edit...
L5 Bottom offset: L5_is_missing_you_should_edit...
HDR10 BL MDL: min: 0.0001 cd/m2, max: 1000 cd/m2
HDR10 BL MDP: Display P3
Resolution: 3840 x 2160
FrameRate: 23.976fps
Duration: 5100.804seconds
the script has completed...
Press any key to continue . . .
Re: Dolby Vision now possible through MP4 Mux.
Posted: Thu Jun 22, 2023 11:10 am
by RESET_9999
It looks like the DV layer stream ID is wrong (6 instead of 1). You'll have to demux that one manually.