Dolby Vision now possible through MP4 Mux.

[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 63704 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!

[Tomas]

Thanks for the reply.
I checked the versions
Plex Player is latest version : 8.7.2.20952
Plex server is also latest version : 1.20.3.3437
After re-anilysing the file it showed the DoVi data. But playing the file was still in HDR

You need the latest 8.8 version of plex. If you weren’t on the beta, i think the public releases just came out today.

Thanks....gonna download that one tonight and see if it works.

EDIT: Update Plex app to 8.8 and worked indeed. Thanks!!

Hello, I downloaded the version PLEX 8.8.0.21167, but when I release mkv, it doesn't start in Dolby Vision, but in HDR. Can you advise what it could be?
Media info:
Video
ID: 1
ID in the original source medium: 4113 (0x1011)
Format: HEVC
Format / Info: High Efficiency Video Coding
Profile format: Main 10 @ L5.1 @ High
HDR format: Dolby Vision, Version 1.0, dvhe.07.06, BL + EL + RPU, Blu-ray compatible / SMPTE ST 2094 App 4, Version 1, HDR10 + Profile B compatible
Codec ID: V_MPEGH / ISO / HEVC
Duration: 1 h 56 min
Bit rate: 78.4 Mbps
Width: 3,840 pixels
Height: 2,160 pixels
Aspect ratio: 16: 9
Frame rate mode: Constant
Frame rate: 23,976 (24000/1001) FPS
Color space: YUV
Chroma subsampling: 4: 2: 0 (Type 2)
Bit depth: 10 bits
Bits / (Pixel * Frame): 0.394
Stream size: 63.6 GiB (94%)
Language: English
Default: No.
Forced: No.
Color range: Limited
Color primaries: BT.2020
Transfer characteristics: PQ
Matrix coefficients: BT.2020 non-constant
Mastering display color primaries: Display P3
Mastering display luminance: min: 0.0050 cd / m2, max: 4000 cd / m2
Maximum Content Light Level: 1000 cd / m2
Maximum Frame-Average Light Level: 755 cd / m2
Original source medium: Blu-ray

[HongyuS]

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!

Tried your new sample, but it does not trigger DoVi on macOS Big Sur.
It plays in HDR10 mode, and works fine. Good job. Guess Apple does not support profile 8.1 after all (but still don't know why QuickTime can play the incorrect profile 8.1 files).

Another interesting phenomenon is that your Terminator sample can be edited with Apple's Photos app, as well as latest version of iMovie on iOS. So I tried to re-encode the video with iMovie, and I got THIS file (DoVi profile 8.4 compatible with HLG, 30FPS, 1080p).

This proves that the latest version of your tool works perfectly with Apple devices! The RPU data is 100% compatible with Apple's Dolby certificated encoder!!!
Please share a Mac version of your tool, or just the source code, so I can test it on my machine!

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!

Thanks for your reminding! You are right. I also double checked the iPhone 12 Pro sample, can confirm that profile 8 does not use "dv**" FourCC.

I also tried to change "dvh1" to "hvc1" of the MBox profile 8.1 sample. The resulting file can be played in QuickTime (contrast still wrong), but cannot be played on my iPad. This is what I could't understand. It should be at least backward compatible with HDR10, like your Terminator sample.

However, change FourCC in profile 5 file ("dvhe" -> "dvh1") works (for both HD and UHD samples)!

[ragico]

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.

Thanks Yusesope again. Followed your advices and made an entire movie in prof 8.1 which plays DV in Firestick.
My remaining problem is how to choose the italian audio track from the m2ts. I know for you would be easy but for me is impossible to do.
Anyway you are simply an extraordinary man.

EDIT:
After many trials and hours I am capable to make the mkv with audio and subs chosen by me.
From scratch to the final mkv it takes less than 1 hour. Excellent, Master Yusesope, your Gamma version of the Tool works very well.

[Buzzie]

You need the latest 8.8 version of plex. If you weren’t on the beta, i think the public releases just came out today.

Thanks....gonna download that one tonight and see if it works.

EDIT: Update Plex app to 8.8 and worked indeed. Thanks!!

Hello, I downloaded the version PLEX 8.8.0.21167, but when I release mkv, it doesn't start in Dolby Vision, but in HDR. Can you advise what it could be?
Media info:
Video
ID: 1
ID in the original source medium: 4113 (0x1011)
Format: HEVC
Format / Info: High Efficiency Video Coding
Profile format: Main 10 @ L5.1 @ High
HDR format: Dolby Vision, Version 1.0, dvhe.07.06, BL + EL + RPU, Blu-ray compatible / SMPTE ST 2094 App 4, Version 1, HDR10 + Profile B compatible
Codec ID: V_MPEGH / ISO / HEVC
Duration: 1 h 56 min
Bit rate: 78.4 Mbps
Width: 3,840 pixels
Height: 2,160 pixels
Aspect ratio: 16: 9
Frame rate mode: Constant
Frame rate: 23,976 (24000/1001) FPS
Color space: YUV
Chroma subsampling: 4: 2: 0 (Type 2)
Bit depth: 10 bits
Bits / (Pixel * Frame): 0.394
Stream size: 63.6 GiB (94%)
Language: English
Default: No.
Forced: No.
Color range: Limited
Color primaries: BT.2020
Transfer characteristics: PQ
Matrix coefficients: BT.2020 non-constant
Mastering display color primaries: Display P3
Mastering display luminance: min: 0.0050 cd / m2, max: 4000 cd / m2
Maximum Content Light Level: 1000 cd / m2
Maximum Frame-Average Light Level: 755 cd / m2
Original source medium: Blu-ray

Did you update the media server also to the latest version?? 1.20.xxx

[Tomas]

Thanks....gonna download that one tonight and see if it works.

EDIT: Update Plex app to 8.8 and worked indeed. Thanks!!

Hello, I downloaded the version PLEX 8.8.0.21167, but when I release mkv, it doesn't start in Dolby Vision, but in HDR. Can you advise what it could be?
Media info:
Video
ID: 1
ID in the original source medium: 4113 (0x1011)
Format: HEVC
Format / Info: High Efficiency Video Coding
Profile format: Main 10 @ L5.1 @ High
HDR format: Dolby Vision, Version 1.0, dvhe.07.06, BL + EL + RPU, Blu-ray compatible / SMPTE ST 2094 App 4, Version 1, HDR10 + Profile B compatible
Codec ID: V_MPEGH / ISO / HEVC
Duration: 1 h 56 min
Bit rate: 78.4 Mbps
Width: 3,840 pixels
Height: 2,160 pixels
Aspect ratio: 16: 9
Frame rate mode: Constant
Frame rate: 23,976 (24000/1001) FPS
Color space: YUV
Chroma subsampling: 4: 2: 0 (Type 2)
Bit depth: 10 bits
Bits / (Pixel * Frame): 0.394
Stream size: 63.6 GiB (94%)
Language: English
Default: No.
Forced: No.
Color range: Limited
Color primaries: BT.2020
Transfer characteristics: PQ
Matrix coefficients: BT.2020 non-constant
Mastering display color primaries: Display P3
Mastering display luminance: min: 0.0050 cd / m2, max: 4000 cd / m2
Maximum Content Light Level: 1000 cd / m2
Maximum Frame-Average Light Level: 755 cd / m2
Original source medium: Blu-ray

Did you update the media server also to the latest version?? 1.20.xxx

Yes

[dmartinvera00]

Doing the first post, will that be enough to have the best version? Or was there some advance in the entire discussion. I already tried with matrix and transformers, and everything ok with the tv

[Buzzie]

Hello, I downloaded the version PLEX 8.8.0.21167, but when I release mkv, it doesn't start in Dolby Vision, but in HDR. Can you advise what it could be?

REMOVED earlier mediainfo

Did you update the media server also to the latest version?? 1.20.xxx

Yes

Do other DV movies play with DV?

[Tomas]

Did you update the media server also to the latest version?? 1.20.xxx

Yes

Do other DV movies play with DV?

Yes, the Dolby Vision movie works when I go over the modified Kodi.