Re: Dolby Vision now possible through MP4 Mux.
Posted: Fri Oct 02, 2020 4:12 pm
What's the benefit of Single Track Single Layer Profile 8.1?
MakeMKV support forum
https://forum.makemkv.com/forum/
I have the version of tsmuxer linked in the instructions. Is that not the correct one?Tomas wrote: Fri Oct 02, 2020 3:09 pmHi, if you want to do .TS to play DV you have to have a modified TS muxer. If you want, I can throw it at you. Otherwise, I did an ISO Blu-ray and then made an mkv in makeMKV and I played DV on Zidoo z9x.blenky wrote: Fri Oct 02, 2020 1:27 pmI'm testing this on my Zidoo z9X with the UHD of 1917. If I create the file as per instructions using Mp4muxer (by using Tsmuxer it only plays in HDR10) the resultant video file plays in DV. However if I then use tsmuxer to add that file and the audio stream from 1917 the output only plays in HDR10.
What am doing wrong?
Screen shot of tsmuxer attached and media info on resultant file
tsmuxer.JPG
Code: Select all
General ID : 1 (0x1) Complete name : D:\Newsbin\dv\1917_mp4.m2ts Format : BDAV Format/Info : Blu-ray Video File size : 71.8 GiB Duration : 1 h 58 min Overall bit rate mode : Variable Overall bit rate : 86.4 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.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible Codec ID : 36 Duration : 1 h 58 min Bit rate : 82.5 Mb/s 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 Bits/(Pixel*Frame) : 0.415 Stream size : 68.6 GiB (95%) 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.0001 cd/m2, max: 1000 cd/m2 Maximum Content Light Level : 1000 cd/m2 Maximum Frame-Average Light Level : 168 cd/m2 Audio ID : 4352 (0x1100) Menu ID : 1 (0x1) Format : AC-3 MLP FBA 16-ch Format/Info : Audio Coding 3 + Meridian Lossless Packing FBA with 16-channel presentation Commercial name : Dolby TrueHD with Dolby Atmos Muxing mode : Stream extension Codec ID : 131 Duration : 1 h 58 min Bit rate mode : Variable Bit rate : 448 kb/s Maximum bit rate : 7 158 kb/s Channel(s) : 8 channels Channel layout : L R C LFE Ls Rs Lb Rb Sampling rate : 48.0 kHz Frame rate : 31.250 FPS (1536 SPF) Compression mode : Lossy Delay relative to video : -2 s 836 ms Stream size : 381 MiB (1%) Language : English Service kind : Complete Main Number of dynamic objects : 11 Bed channel count : 1 channel Bed channel configuration : LFE Text ID : 4768 (0x12A0) Menu ID : 1 (0x1) Format : PGS Codec ID : 144 Language : English
I've tried the new -mode 2 with a FEL title (Atomic Blonde) and it plays on the Firestick 4K, while previous default (profile 7) just plays a black screen. So that's good news.yusesope wrote: Fri Oct 02, 2020 1:00 pm Another weekend is about to begin so you have a little time to try "the things" I write![]()
![]()
!
This time it's up to profile 8.1!
I have updated the POST we refer to during this testing phase.
Find all the instructions there.
This update "fixes" what was previously called "-mode 2".
The new lines of code should allow you to convert a UHD-BD (both MEL and FEL) in a file Single Track Single Layer profile 8.1 (STSL dvhe.08.0x, BL + RPU, HDR10 compatible).
All devices, especially TVs with proprietary OS, capable of playing profile 8 files (and which have so far encountered problems with DV) could benefit from this update.
Before starting, to find out if your device is able to correctly reproduce profile 8, use the test files that Dolby provides on THIS page
Happy testing!
Code: Select all
mp4muxer -i path\to\BL_EL_RPU.hevc --dv-profile 8 -o path\to\TEST_FILE.mp4I tested them + 1 small conversion on oppo clone, all of them plays fine! Thank you!!!yusesope wrote: Fri Oct 02, 2020 1:00 pmThe new lines of code should allow you to convert a UHD-BD (both MEL and FEL) in a file Single Track Single Layer profile 8.1 (STSL dvhe.08.0x, BL + RPU, HDR10 compatible).
...
All devices, especially TVs with proprietary OS, capable of playing profile 8 files (and which have so far encountered problems with DV) could benefit from this update.
Before starting, to find out if your device is able to correctly reproduce profile 8, use the test files that Dolby provides on THIS page
Please I wanted to ask there no longer need to be used after MUX_AND_CONVERT_TO_PROFILE_81, use DEMUX step?yusesope wrote: Fri Oct 02, 2020 1:00 pm Another weekend is about to begin so you have a little time to try "the things" I write![]()
![]()
!
This time it's up to profile 8.1!
I have updated the POST we refer to during this testing phase.
Find all the instructions there.
This update "fixes" what was previously called "-mode 2".
The new lines of code should allow you to convert a UHD-BD (both MEL and FEL) in a file Single Track Single Layer profile 8.1 (STSL dvhe.08.0x, BL + RPU, HDR10 compatible).
All devices, especially TVs with proprietary OS, capable of playing profile 8 files (and which have so far encountered problems with DV) could benefit from this update.
Before starting, to find out if your device is able to correctly reproduce profile 8, use the test files that Dolby provides on THIS page
Happy testing!
Tried it in a Sony Xf90 and the default player doesn't play the demos, the exoplayer played it but has the same problem with the profile 7, red tones everywhereyusesope wrote: Fri Oct 02, 2020 1:00 pm Another weekend is about to begin so you have a little time to try "the things" I write![]()
![]()
!
This time it's up to profile 8.1!
I have updated the POST we refer to during this testing phase.
Find all the instructions there.
This update "fixes" what was previously called "-mode 2".
The new lines of code should allow you to convert a UHD-BD (both MEL and FEL) in a file Single Track Single Layer profile 8.1 (STSL dvhe.08.0x, BL + RPU, HDR10 compatible).
All devices, especially TVs with proprietary OS, capable of playing profile 8 files (and which have so far encountered problems with DV) could benefit from this update.
Before starting, to find out if your device is able to correctly reproduce profile 8, use the test files that Dolby provides on THIS page
Happy testing!
Code: Select all
mp4muxer -i path\to\BL_EL_RPU.hevc --dv-profile 8 --dv-bl-compatible-id 1 -o path\to\TEST_FILE.mp4
mp4muxer -i path\to\BL_EL_RPU.hevc --dv-profile 8 --dv-bl-compatible-id 2 -o path\to\TEST_FILE.mp4
I've tested notrious MI:Fallout scene on Shield TV and ... nope, still reddish blocks.
Code: Select all
python-3.7.6.amd64\python.exe src\app.py -mux -mode 2hello, in your mediainfo in your audio track you have:blenky wrote: Fri Oct 02, 2020 6:32 pm Managed to get 8.1 working on Zidoo z9X by using tsmuxer to combine with Atmos audio from UHD to create ISO. Then created MKV with MakeMKV. Only thing is audio is out of sync. Need to offset audio ahead by about half a second.
Playback gets juddery after about 5 minutes - unwatchable at that point
afss, post: 134440, member: 19783 wrote:BTW, I have placed this question on another thread, but in case Mark (or somebody else) knows the answer. How can we find out what the player is actually doing, while using LLDV ? I mean, I think I have properly converted a MEL DV bluray to MKV, and when I play it back on the Z10 pro, I am unable to verify if the conversion was sucessfull and the player is actually using the DV data on the file, or if it is simply treating it as HDR10.
On the OPPO 203, for instance, the info window shows how the source file is being interpreted as (DV, HDR10, SDR). Maybe there is a way somewhere to verify what the player is doing on the Zidoo as well.
Markswift2003, post: 134446, member: 21473 wrote:This is something I'm a bit unclear on too - As far as I know, the player natively supports Profiles 5, 8 & 9 which are all single base layers plus RPU (Reference Processing Unit = metadata interleaved in the video stream).
But as we know, Profile 7 encoding is now leaning more towards MEL than FEL and with the Enhancement Layer omitted, that is simply a standard 10-bit HDR10 stream with a Dolby RPU interleaved (plus HDR10 SEI for backwards compatibility).
So when VS10 is playing out P7 MEL it's either HDR10 with HDR10 SEI converted into P5 or it's HDR10 with Dolby RPU converted into P5 which would basically be a colour map from BT.2020 to IPT since the RPU is the same for both. It all comes down to how the PQ curve is produced on the output - in other words, the tone map.
Unless of course you do as we are doing and introduce BT.2020 primaries in the Dolby block in the EDID, in which case there's no colour map needed so nothing really changes.
I'd like to think it's the latter but as always Dolby are playing their cards very close to their chest and I can't find any technical docs regarding how VS10 deals with this but it would make sense that the RPU is used.
As usual, amazing work yusesope! Thanks a lot!yusesope wrote: Fri Oct 02, 2020 1:00 pm Another weekend is about to begin so you have a little time to try "the things" I write![]()
![]()
!
This time it's up to profile 8.1!
I have updated the POST we refer to during this testing phase.
Find all the instructions there.
This update "fixes" what was previously called "-mode 2".
The new lines of code should allow you to convert a UHD-BD (both MEL and FEL) in a file Single Track Single Layer profile 8.1 (STSL dvhe.08.0x, BL + RPU, HDR10 compatible).
All devices, especially TVs with proprietary OS, capable of playing profile 8 files (and which have so far encountered problems with DV) could benefit from this update.
Before starting, to find out if your device is able to correctly reproduce profile 8, use the test files that Dolby provides on THIS page
Happy testing!