Clearly the file you're using as source has incorrect metadata order.
Nothing you can do other than having access to the original retail source for the HDR10+ metadata.
Best way is convert to dvhe 08.06 or hdr10 compatible with rpu. the profile 8.1 is compatible with mkv / mp4 container for hdr10 tv.proximus wrote: ↑Wed Aug 31, 2022 1:04 amHello,
First of all excuse me for my English, I'm not English speaking at the base
I need your help .. I read many many pages on this forum but I remain in misunderstanding:
I'm trying to extract DV data from an MKV file, like this: Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible
and reinject them into an MKV file that only contains HDR10 data, like this: SMPTE ST 2086, HDR10 compatible
Can someone give me the step by step I need to do? With what software or scripts, step by step like I was 8 years old lol
I've been trying to do this for months
Thanks a lot !
Code: Select all
== SETTINGS ==
SAVE HDR BL : [NO]
SAVE DoVI EL : [NO]
SAVE RPU : [YES]
CONVERT RPU : [PROFILE 8.1 HDR]
CROP RPU : [YES]
Code: Select all
== VIDEO INPUT ==
Video Info = [Resolution = 3836x1600] [Codec = HEVC-10Bit-YUV-4:2:0] [Frames = 145630] [FPS = 23.976]
HDR Info = [Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible]
Borders = [LEFT=0 px], [TOP=0 px], [RIGHT=0 px], [BOTTOM=0 px] [MATCH WITH RPU]
== RPU INPUT ==
Filename = [RPU.bin]
RPU Info = [DV Profile = 8] [CM Version = 2.9] [Frames = 145630]
Borders = [LEFT=0 px], [TOP=0 px], [RIGHT=0 px], [BOTTOM=0 px] [MATCH WITH VIDEO]
Code: Select all
Video Info = [Resolution = 3836x1600] [Codec = HEVC-10Bit-YUV-4:2:0] [Frames = 145630] [FPS = 23.976]
HDR Info = [Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible]
Remove Dolby Vision Metadata : [YES]
Hi, I added P7 support in Mode.I (1) in DoVi_Scripts_1.5.4.
Possibly, I never work with output or temp path that contains space or special characters so I never really test that.
I could be wrong but I don't think it's possible if you don't have the original EL.
mp4muxer --dv-profile 5 --input-file BL.hevc --input-file audio.ec3 --dvh1flag 0 --output-file output.mp4staknhalo wrote: ↑Fri Sep 02, 2022 9:35 pmAnyone here make DVH1 P5 mp4 on Windows for iOS playback? What are you using for generation with the DVH1 flag? mp4muxer doesn't do it right? Or does it have a flag for it? Not at my desktop ATM with all my stuff so can't easily check.
DVH1 still works on Android/Windows - so for the few P5 I have (because mostly P8 or P7) I'm gonna make them DVH1 (from DVHE) just for 'maximum compatibility).
thank youRESET_9999 wrote: ↑Fri Sep 02, 2022 10:26 pmmp4muxer --dv-profile 5 --input-file BL.hevc --input-file audio.ec3 --dvh1flag 0 --output-file output.mp4
Don't use mp4muxer to change dvhe->dvh1 for iOS device.staknhalo wrote: ↑Sat Sep 03, 2022 2:30 amthank youRESET_9999 wrote: ↑Fri Sep 02, 2022 10:26 pmmp4muxer --dv-profile 5 --input-file BL.hevc --input-file audio.ec3 --dvh1flag 0 --output-file output.mp4
yusesope wrote: ↑Fri Oct 23, 2020 10:45 amThe correct codec ID (for profile 8.1) should be "hvc1" in place of "hev1". But be careful, these boxes are not random: they indicate to the decoder how the information for the initialization of the latter is stored within the file. Changing the header with a hex editor isn't always enough!