Dolby Vision now possible through MP4 Mux.

[yusesope]

@Yusesope
I did other tests and got your MKV_Patcher to work finally.
........................
This file plays as HDR in firestick and as DV in Ugoos/shield.

Out of curiosity, what was the problem with the patcher?
It should also work on Fire Stick.
When you have time, try the files you find at the bottom of this post.
Let me know!

i just realised....

when i mux hevc file from ys's tool with mkvtoolnix, makemkv recognizes this as dvhe.07.00, BL+RPU, but created mkv is dvhe.07.00, EL+RPU in mediainfo... this is known thing...

but when i ran THAT mkv through makemkv again, makemkv recognise the mkv correctly, as dvhe.07.06, BL+FEL+RPU, and outputted MKV is also correct... dvhe.07.06, BL+EL+RPU in mediainfo. so mkv_patcher is "not needed"... but requires more space and time.

If I were you, to be 100% sure, I'd pass the file to MakeMKV 15 more times ... you never know !
The main point is to save time and space ... that's what the patcher is for!

@yusesope
i was wondering more...

would it be possible to extract RPU metadata from the secondary HEVC stream on BD? that can be then used directly with x265 to encode directly to profile 5 or 8.1

I had already answered this question in the past (HERE).

@yusesope I followed your steps in the post above to the letter.
.........................................
However the resultant files play back in HDR10 on my Zidoo Z9X.

I have updated the POST of the 0.0.4 GAMMA version.
I think I have made some steps forward.
THESE samples were obtained with the latter version.
Do they trigger DV on your devices?
The files contain an ATMOS audio track that could create some incompatibility with those devices without decoder, e.g. LG TVs.

[DaMacFunkin]

I have another question.

Later i am gonna update my Plex to version 8.8 on my shield to see if the MKV files are gonna play in DV instead of HDR.

In the meantime i have another question

Has anybody here converted other movie files (TS of MP4) to MKV with Dolby Vision remaining as well as HD audio ?

I am trying for instance the following :

General
ID : 1 (0x1)
Complete name : V:\Movie\Movie.ts
Format : MPEG-TS
File size : 52.9 GiB
Duration : 1 h 38 min
Overall bit rate mode : Variable
Overall bit rate : 76.5 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.06.06, BL+EL+RPU, HDR10 compatible / SMPTE ST 2086
Codec ID : 6
Duration : 1 h 38 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 906 cd/m2
Maximum Frame-Average Light Level : 824 cd/m2

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : DTS XLL X
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Muxing mode : Stream extension
Codec ID : 134
Duration : 1 h 38 min
Bit rate mode : Variable
Channel(s) : Object Based
Channel layout : Object Based
Delay relative to video : -500 ms
Language : English

But no matter what i try, ffmpeg, makemkv or mkvtoolnix i keep getting a non Dolby Vision file according to Mediainfo.

Any Ideas?

Drop your TS file into Tsmuxer, select output as ISO and mux.
Re-rip new ISO with latest Makemkv.

[badrobot]

The iPhone 12 review from Verge says DoVi type 8.4

Could you plz upload the sample video file to mega.nz or google drive, I want to test it on shield tv 2019.

Thanks a lot for the info!
Looks like this profile is pretty new, not even specified in the Dolby Vision profiles/levels doc (which updated last year).

Here is a link of the original file:
https://drive.google.com/file/d/1JsFd_K ... sp=sharing

The video is not shot by me. I got it from another group on Bilibili (see "BV1rv411k7GL").

One more thing, are you Chinese? Mr Hong? I am from Mainland of China.

Yes, I'm also from mainland China.

Good News, this video sample can be recognized by Plex Media Server, and trigger Dolby Vision on Shield TV 2019.

截屏2020-10-22 下午11.56.00.png (197.58 KiB) Viewed 30391 times

[yusesope]

Here is a link of the original file:
https://drive.google.com/file/d/1JsFd_K ... sp=sharing

I took a look at the iPhone 12 video: the RPUs are structurally identical to the ones my algorithm (-mode 2) produces when choosing UHD-BD -> profile 8.1 conversion.

It doesn't mean they're perfect but I'm happy with the insight I got !

This could be important for two categories of devices:

• for the new LG CX which, according to various forums around the world, seems to have abandoned (with the new firmware) support for Dual Track Dual Layer MP4 profile 7 files.
• for ATV4K. I assume (I hope) that the Cupertino people will update the current ATV4Ks so that they can play the latest iPhone videos (although Apple is always full of surprises).

OT:
Do you guys use a VPN to be able to write here or upload files to Gdrive?

[ragico]

@Yusesope

Tried your latest samples and all play in DV in shield/Ugoos
The Fel_to_Mel and Fel_to_8.1 play DV in Firestick with audio disabled (firestick do not support Atmos).
Also tried Fel_to_8.1 in ATV 4k and plays in HDR but, a quick conversion to profile 5 and it plays in DV.

Yusesope I have tried to use yr latest tool, but I am not brave enough.
I need yr instructions with a pratical example, for instance:

python-3.7.6.amd64\python.exe src\app.py -mux -exp \path\to\your\original\file.m2ts
can I write down D:\000125.m2ts? Is this example correct?

And Then:

src\Gpac\gpac.exe -i pipe://video:ext=hevc:audelim=true -o stdout:ext=ts:pes_pack=none | src\FFmpeg\ffmpeg_win_x64.exe -hide_banner -y -i - -i \path\to\your\original\file.m2ts -map 0:0 -map 1:2 -c copy -bsf:v hevc_metadata=aud=insert -metadata title="Movie Title_________________________________________________________________________" \path\to\your\output\file.mkv

Same as above? And I need "" for Movie Title?

[codeXRes]

I have another question.

Later i am gonna update my Plex to version 8.8 on my shield to see if the MKV files are gonna play in DV instead of HDR.

In the meantime i have another question

Has anybody here converted other movie files (TS of MP4) to MKV with Dolby Vision remaining as well as HD audio ?

I am trying for instance the following :

General
ID : 1 (0x1)
Complete name : V:\Movie\Movie.ts
Format : MPEG-TS
File size : 52.9 GiB
Duration : 1 h 38 min
Overall bit rate mode : Variable
Overall bit rate : 76.5 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.06.06, BL+EL+RPU, HDR10 compatible / SMPTE ST 2086
Codec ID : 6
Duration : 1 h 38 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 906 cd/m2
Maximum Frame-Average Light Level : 824 cd/m2

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : DTS XLL X
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Muxing mode : Stream extension
Codec ID : 134
Duration : 1 h 38 min
Bit rate mode : Variable
Channel(s) : Object Based
Channel layout : Object Based
Delay relative to video : -500 ms
Language : English

But no matter what i try, ffmpeg, makemkv or mkvtoolnix i keep getting a non Dolby Vision file according to Mediainfo.

Any Ideas?

Drop your TS file into Tsmuxer, select output as ISO and mux.
Re-rip new ISO with latest Makemkv.

Just to add to this, the output mkv file you get might be detected as dvhe.07.00, BL+RPU by Mediainfo. If that happens, open the mkv file in MakeMKV and just create a new file without any settings changes. The resulting mkv will be properly recognised as dvhe.07.06, BL+EL+RPU. I have no idea why this is happening though. Good luck.

[yusesope]

python-3.7.6.amd64\python.exe src\app.py -mux -exp \path\to\your\original\file.m2ts

can I write down D:\000125.m2ts? Is this example correct?

If the file is located in D:\000125.m2ts then you must write D:\000125.m2ts instead of \path\to\your\original\file.m2ts.
Are you sure the correct address is not D:\BDMV\STREAM\000125.m2ts?
A little trick: while copying the command line, stop at -exp, leave a space, and then drag and drop the m2ts file into the Command Prompt window you are using. Windows will automatically fill in the correct address of your file.

And Then:

src\Gpac\gpac.exe -i pipe://video:ext=hevc:audelim=true -o stdout:ext=ts:pes_pack=none | src\FFmpeg\ffmpeg_win_x64.exe -hide_banner -y -i - -i \path\to\your\original\file.m2ts -map 0:0 -map 1:2 -c copy -bsf:v hevc_metadata=aud=insert -metadata title="Movie Title_________________________________________________________________________" \path\to\your\output\file.mkv

Same as above? And I need "" for Movie Title?

The same applies to all "\path\to\your\......" strings marked in blue (the above trick works the same way).
And yes, you need the quotes ("") when setting the title metadata

[Buzzie]

I have another question.

Later i am gonna update my Plex to version 8.8 on my shield to see if the MKV files are gonna play in DV instead of HDR.

In the meantime i have another question

Has anybody here converted other movie files (TS of MP4) to MKV with Dolby Vision remaining as well as HD audio ?

I am trying for instance the following :

General
ID : 1 (0x1)
Complete name : V:\Movie\Movie.ts
Format : MPEG-TS
File size : 52.9 GiB
Duration : 1 h 38 min
Overall bit rate mode : Variable
Overall bit rate : 76.5 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.06.06, BL+EL+RPU, HDR10 compatible / SMPTE ST 2086
Codec ID : 6
Duration : 1 h 38 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 906 cd/m2
Maximum Frame-Average Light Level : 824 cd/m2

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : DTS XLL X
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Muxing mode : Stream extension
Codec ID : 134
Duration : 1 h 38 min
Bit rate mode : Variable
Channel(s) : Object Based
Channel layout : Object Based
Delay relative to video : -500 ms
Language : English

But no matter what i try, ffmpeg, makemkv or mkvtoolnix i keep getting a non Dolby Vision file according to Mediainfo.

Any Ideas?

Drop your TS file into Tsmuxer, select output as ISO and mux.
Re-rip new ISO with latest Makemkv.

Thanks !! Muxing to ISO now and rerip after.

skip

Drop your TS file into Tsmuxer, select output as ISO and mux.
Re-rip new ISO with latest Makemkv.

Just to add to this, the output mkv file you get might be detected as dvhe.07.00, BL+RPU by Mediainfo. If that happens, open the mkv file in MakeMKV and just create a new file without any settings changes. The resulting mkv will be properly recognised as dvhe.07.06, BL+EL+RPU. I have no idea why this is happening though. Good luck.

Thanks for the heads up !!
dont know the difference but i will look at the files.
Thanks

[ragico]

python-3.7.6.amd64\python.exe src\app.py -mux -exp \path\to\your\original\file.m2ts

can I write down D:\000125.m2ts? Is this example correct?

If the file is located in D:\000125.m2ts then you must write D:\000125.m2ts instead of \path\to\your\original\file.m2ts.
Are you sure the correct address is not D:\BDMV\STREAM\000125.m2ts?
A little trick: while copying the command line, stop at -exp, leave a space, and then drag and drop the m2ts file into the Command Prompt window you are using. Windows will automatically fill in the correct address of your file.

And Then:

src\Gpac\gpac.exe -i pipe://video:ext=hevc:audelim=true -o stdout:ext=ts:pes_pack=none | src\FFmpeg\ffmpeg_win_x64.exe -hide_banner -y -i - -i \path\to\your\original\file.m2ts -map 0:0 -map 1:2 -c copy -bsf:v hevc_metadata=aud=insert -metadata title="Movie Title_________________________________________________________________________" \path\to\your\output\file.mkv

Same as above? And I need "" for Movie Title?

The same applies to all "\path\to\your\......" strings marked in blue (the above trick works the same way).
And yes, you need the quotes ("") when setting the title metadata

These are the commands that I applied.
1) python-3.7.6.amd64\python.exe src\app.py -mode 2 -mux -exp I:\BDMV\STREAM\00018.m2ts

2) src\Gpac\gpac.exe -i pipe://video:ext=hevc:audelim=true -o stdout:ext=ts:pes_pack=none | src\FFmpeg\ffmpeg_win_x64.exe -hide_banner -y -i - -i I:\BDMV\STREAM\00018.m2ts -map 0:0 -map 1:2 -c copy -bsf:v hevc_metadata=aud=insert -metadata title=
"Transformers_____________________________________"
D:\Transformers.mkv

And this is what I get:

test2.jpg (70.34 KiB) Viewed 30272 times

Where is my fault?

[HongyuS]

I took a look at the iPhone 12 video: the RPUs are structurally identical to the ones my algorithm (-mode 2) produces when choosing UHD-BD -> profile 8.1 conversion.

It doesn't mean they're perfect but I'm happy with the insight I got !

I just tried -mode 2 on my iPad Pro (latest iOS 14 Beta), contrast ratio looks wrong. But can confirm it was a bug of Apple, cuz profile 8.1 sample from MBox have the same issue. (Due to copyright limitations, I cannot share the samples with anyone, but you can download them from MysteryBox's website)

However, sample made by yusesope's "-mode 2" triggers crash on macOS Big Sur, while encoding sample from MBox does not. So there are still room for improvements.

OT:
Do you guys use a VPN to be able to write here or upload files to Gdrive?

Yes. VPN is essential to access "real" internet in China

[HongyuS]

I took a look at the iPhone 12 video: the RPUs are structurally identical to the ones my algorithm (-mode 2) produces when choosing UHD-BD -> profile 8.1 conversion.

It doesn't mean they're perfect but I'm happy with the insight I got !

I’m also wondering that - is it possible to extract the RPU data which can be used by the x265 encoder?

Since all streaming services are using profile 5, it would be much more convenient if we can re-encode the video to profile 5. Looks like profile 5 have the best cross-platform capability by now.

[dapope]

EDIT: Seems to be some sort of glitch with Tsmuxer. Using Tsmuxer to remux the file as .m2ts and not .ts works and is recognised by the LG.

-

I'm having an audio problem in my quest for Dolby Vision on my LG CX internal player. I use headphones so I've been converting the DTS-HD MA track to a stereo WAV. Put simply I demux using Tsmuxer, merge HEVC files using 8.1.bat, convert the audio using eac3to and then remux using Tsmuxer. I have the Back to the Future 4K set. The first movie worked fine using this process. However movies 2 and 3 fail to recognise the LPCM audio track. Mediainfo displays that the track is there and all the attributes are identical to the first movie which works perfectly. I really have no idea what could be going wrong or how to fix it!

[badrobot]

I took a look at the iPhone 12 video: the RPUs are structurally identical to the ones my algorithm (-mode 2) produces when choosing UHD-BD -> profile 8.1 conversion.

It doesn't mean they're perfect but I'm happy with the insight I got !

I just tried -mode 2 on my iPad Pro (latest iOS 14 Beta), contrast ratio looks wrong. But can confirm it was a bug of Apple, cuz profile 8.1 sample from MBox have the same issue. (Due to copyright limitations, I cannot share the samples with anyone, but you can download them from MysteryBox's website)

However, sample made by yusesope's "-mode 2" triggers crash on macOS Big Sur, while encoding sample from MBox does not. So there are still room for improvements.

OT:
Do you guys use a VPN to be able to write here or upload files to Gdrive?

Yes. VPN is essential to access "real" internet in China

I have tried MBOX demo video files on my iPad Pro, it seems that P5 can be identified as DoVi by infuse 6, but P8.1 can not.
Result:P5 play as DoVi, P8.1 play as HDR, I have uploaded these screenshots.

https://screenshotcomparison.com/comparison/7316

[HongyuS]

I have tried MBOX demo video files on my iPad Pro, it seems that P5 can be identified as DoVi by infuse 6, but P8.1 can not.
Result:P5 play as DoVi, P8.1 play as HDR, I have uploaded these screenshots.

https://screenshotcomparison.com/comparison/7316

I forgot to mention one very important info: Apple require the video track fourcc ID to be “dvh1” for Dolby Vision. So you need to change it manually using a Hex editor. (More info: the sample I recommended to you is “dvhe”, which cannot be played by QuickTime/Apple TV app)

Furthermore, Infuse only supports profile 5. If you want to test profile 8.x, you need to copy the the m4v file to the “Files” app, and preview with it. (And you must use iPadOS 14.1 or 14.2 beta 4, or later versions, in order to support profile 8.x)

[yusesope]

2) src\Gpac\gpac.exe -i pipe://video:ext=hevc:audelim=true -o stdout:ext=ts:pes_pack=none | src\FFmpeg\ffmpeg_win_x64.exe -hide_banner -y -i - -i I:\BDMV\STREAM\00018.m2ts -map 0:0 -map 1:2 -c copy -bsf:v hevc_metadata=aud=insert -metadata title=
"Transformers_____________________________________"
D:\Transformers.mkv

The first command line is fine, in the second there are two invisible mistakes!
You entered two "newline" characters (sei andato a capo due volte): one immediately after title= and the other after the underscores and the quotation mark (before the address of the output file).
Look HERE.

The command line is a single long line and the only spacing character allowed is the space.
You can help yourself with THIS online tool for removing line breaks.

the second command line should be (look at the parts in red):

src\Gpac\gpac.exe -i pipe://video:ext=hevc:audelim=true -o stdout:ext=ts:pes_pack=none | src\FFmpeg\ffmpeg_win_x64.exe -hide_banner -y -i - -i I:\BDMV\STREAM\00018.m2ts -map 0:0 -map 1:2 -c copy -bsf:v hevc_metadata=aud=insert -metadata title="Transformers_____________________________________" D:\Transformers.mkv

No space between title= and the next quotation mark.
A simple space between the last quotation mark and the address of the output file.

However, sample made by yusesope's "-mode 2" triggers crash on macOS Big Sur, while encoding sample from MBox does not. So there are still room for improvements.

The mysterybox sample (the one with profile 8.1) is FHD (1920 × 1080): did we download the same file?
Mine are UHD (3840 x 2160): it would be an unequal comparison !

Would you tell me exactly which sample produced by my tool you tried? It is important to know because "-mode 2" has undergone some changes over time!
I leave you a SAMPLE (video only - profile 8.1 derived from a FEL) obtained with the latest version of my tool and adapted to meet what I believe are the needs of macOS Big Sur. I don't know if it will be played but it doesn't hurt to try!

I forgot to mention one very important info: Apple require the video track fourcc ID to be “dvh1” for Dolby Vision. So you need to change it manually using a Hex editor. (More info: the sample I recommended to you is “dvhe”, which cannot be played by QuickTime/Apple TV app)

The 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!