Dolby Vision now possible through MP4 Mux.

[olevelo]

So are you saying that if we play back one of the profile 4 videos on a non-DV device we won't even get HDR10?

[Epedemic]

Profile 6 is a deprecated standard, so you're not going to find it in the latest dolby docs. The difference between 4 and 6 is in its backwards compatibility ID (SDR for 4 and HDR for 6). Purely specs-wise, the video tracks generated from yusecope's tool and makemkv should be either profile 6 or 7 since they are HDR10 compatible. But since most devices don't support profiles 6/7, they are forced to profile 4 in tsmuxer (either through an older version of tsmuxer or a modified nightly version). When playing back DV content on a supported device, the backwards compatibility ID doesn't matter, so it's not really a big deal to incorrectly label these files as 4 for the pure purpose of DV playback.

In terms of the Shield, yusecope has mentioned in the past that when exoplayer encounters an unsupported DV profile, it likely looks at the video stream and then chooses the best suitable supported profile to play the file. So for instance when it encounters a BL+EL+RPU track that's labeled profile 6 or 7, it will fallback to treating it as profile 4 and still play them just fine.

Thanks That clarified a lot for me.

[shawnc22]

So are you saying that if we play back one of the profile 4 videos on a non-DV device we won't even get HDR10?

With a fully-compliant profile 4 video, no, I don't believe you will get even HDR10 on a non-DV device. Take the LG DV demo from here for example:

https://4kmedia.org/lg-dolby-comparison-uhd-4k-demo/

This file in mediainfo is listed as:

Code: Select all

Dolby Vision, Version 1.0, dvhe.04.06, BL+EL+RPU

whereas the profile 4/6 files we have been generating is labeled as:

Code: Select all

Dolby Vision, Version 1.0, dvhe.04.06, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible

On my Xbox one X, the LG demo doesn't even trigger HDR, but the other files will. This then brings up the question whether devices are really looking at just the profile to determine playback capabilities or at the actual content of the video stream. This I honestly have no idea and could simply be a device-to-device question.

[VictorLemon]

I extract the BL and EL files through eac3to, the movie is Despicable Me (2010), to extract charge in eac3to the main mpls, since the movie is in several m2ts, it generates the BL and EL, I use the yusesope tool in its latest version and when the process is at 99.9% it gives me the following error.


Greetings

[yusesope]

I extract the BL and EL files through eac3to, the movie is Despicable Me (2010), to extract charge in eac3to the main mpls, since the movie is in several m2ts, it generates the BL and EL, I use the yusesope tool in its latest version and when the process is at 99.9% it gives me the following error.


Greetings

Don't worry, the file you got is complete (only one byte is missing).
The error is due to your input file: it is not complete at the end.

I will correct this in the future.

[VictorLemon]

I extract the BL and EL files through eac3to, the movie is Despicable Me (2010), to extract charge in eac3to the main mpls, since the movie is in several m2ts, it generates the BL and EL, I use the yusesope tool in its latest version and when the process is at 99.9% it gives me the following error.


Greetings

Don't worry, the file you got is complete (only one byte is missing).
The error is due to your input file: it is not complete at the end.

I will correct this in the future.

Thanks

[yusesope]

Got it, thanks for the clarification! It seems to me that a FEL->MEL conversion, and maybe followed by a conversion to IPTPQc2/IPT color space if profile 5 is desired, is kind of the “holy grail” for maximizing compatibility across devices. I know the Shield has been playing FEL titles fine, but I’ve always wondered if it’s doing it correctly since only profile 4 MEL is supposedly supported. FEL->MEL does seem like a daunting task, but maybe not as impossible as it once looked according to mike here?

the problem is not the conversion of the color space.
The problem is understanding how to generate new RPU metadata without distorting the color correction/grading work done in post production and the entire vision of the director.
With what we've discovered, you could take a video shot on your cell phone and insert random RPU metadata.
The video would be reproduced by activating Dolby Vision but the colors would be completely wrong!

Thanks

You are welcome

[deadchip12]

For Dolby Vision + Atmos:

Here's my success story for Gemini Man 2019 which is a 60fps movie which plays much more fluent.
I'm using Fedora 31 Linux but I've also posted windows links

Tools:
- ffmpeg - compiled from latest git (Windows build: https://ffmpeg.zeranoe.com/builds/)
- yusesope - tool V3: https://www.makemkv.com/forum/viewtopic ... 335#p85413
- eac3to portable version with wine - https://www.videohelp.com/software/eac3to
- tsmuxer modified for DV by a5180007/justdan96 - compiled from his github https://github.com/justdan96/tsMuxer (Windows build: https://bintray.com/justdan96/tsMuxer/t ... UI-Nightly) (Original forum thread: http://forum.doom9.org/showthread.php?t=176668&page=31)
Use the latest nightly tsMuxerGUI from this link, it's more recent compared the one posted a few pages back! and a5180007 also added support for eac3 dolby digital plus! (only 5.1)

First I demux the original bluray (will only work if I compile the latest FFMpeg git from source):

Code: Select all

ffmpeg -i bluray:/path/to/my/bluray -map 0:0 -c copy ./BL.hevc -map 0:1 -c copy ./EL.hevc -map 0:2 -c:a copy -strict -2 ./atmos.mp4

Now I have:
BL.hevc - Base Layer
EL.hevc - Enhanced Layer
atmos.mp4 - Dolby TrueHD Atmos audio

Now I use yusescope V3 tool to create a single layer DV file:

Code: Select all

python src/bl_el_rpu_builder.py -bl ./BL.hevc -el ./EL.hevc -of gemini_dv.hevc -mode 1

Now I also have:
gemini_dv.hevc - Full movie Single Layer DV

Now I use eac3to Gui to convert the atmos.mp4 to a compatible truehd+ac3 track for use with TSMuxeR:

Code: Select all

wine UsEac3To.exe

- Click Input File and select atmos.mp4
- Under Track Input and Output format change "ac3" to "thd+ac3" then click Add
- In the bottom click RUN CL and wait
When finished you will have a "atmos.mp4_.thd+ac3" file, rename this to "atmos.ac3"

Now launch justdan96's version of TsMuxerGUI then add your movie file: "gemini_dv.hevc" and audio file: "atmos.ac3".

So I have tried this method for Gemini man and Sonic 2019 and both of them freeze every 2 seconds during playback. My tv is lg oled c9. The files were stored in an external hdd connected to the tv via usb. All other souble layered dolby vision mp4 files created using the original method in the first post of this thread play fine. Maybe my tv can't properly play .ts file/single layered dolby vision file?

[Epedemic]

For Dolby Vision + Atmos:

Here's my success story for Gemini Man 2019 which is a 60fps movie which plays much more fluent.
I'm using Fedora 31 Linux but I've also posted windows links

Tools:
- ffmpeg - compiled from latest git (Windows build: https://ffmpeg.zeranoe.com/builds/)
- yusesope - tool V3: https://www.makemkv.com/forum/viewtopic ... 335#p85413
- eac3to portable version with wine - https://www.videohelp.com/software/eac3to
- tsmuxer modified for DV by a5180007/justdan96 - compiled from his github https://github.com/justdan96/tsMuxer (Windows build: https://bintray.com/justdan96/tsMuxer/t ... UI-Nightly) (Original forum thread: http://forum.doom9.org/showthread.php?t=176668&page=31)
Use the latest nightly tsMuxerGUI from this link, it's more recent compared the one posted a few pages back! and a5180007 also added support for eac3 dolby digital plus! (only 5.1)

First I demux the original bluray (will only work if I compile the latest FFMpeg git from source):

Code: Select all

ffmpeg -i bluray:/path/to/my/bluray -map 0:0 -c copy ./BL.hevc -map 0:1 -c copy ./EL.hevc -map 0:2 -c:a copy -strict -2 ./atmos.mp4

Now I have:
BL.hevc - Base Layer
EL.hevc - Enhanced Layer
atmos.mp4 - Dolby TrueHD Atmos audio

Now I use yusescope V3 tool to create a single layer DV file:

Code: Select all

python src/bl_el_rpu_builder.py -bl ./BL.hevc -el ./EL.hevc -of gemini_dv.hevc -mode 1

Now I also have:
gemini_dv.hevc - Full movie Single Layer DV

Now I use eac3to Gui to convert the atmos.mp4 to a compatible truehd+ac3 track for use with TSMuxeR:

Code: Select all

wine UsEac3To.exe

- Click Input File and select atmos.mp4
- Under Track Input and Output format change "ac3" to "thd+ac3" then click Add
- In the bottom click RUN CL and wait
When finished you will have a "atmos.mp4_.thd+ac3" file, rename this to "atmos.ac3"

Now launch justdan96's version of TsMuxerGUI then add your movie file: "gemini_dv.hevc" and audio file: "atmos.ac3".

So I have tried this method for Gemini man and Sonic 2019 and both of them freeze every 2 seconds during playback. My tv is lg oled c9. The files were stored in an external hdd connected to the tv via usb. All other souble layered dolby vision mp4 files created using the original method in the first post of this thread play fine. Maybe my tv can't properly play .ts file/single layered dolby vision file?

Well, i'm not sure, but it sounds like what my E6 did when i accidentially fed it a .mp4 with a Atmos thd+ac3 file renamed to .ac3 waaaay back.... My suggestion: Try with a clean ac3 file and see if that helps, and then figure out how to do a proper thd+ac3 track afterwards (or put both in and switch between them and see if one or both works)

[darrrkmanxxx]

For Dolby Vision + Atmos:

Here's my success story for Gemini Man 2019 which is a 60fps movie which plays much more fluent.
I'm using Fedora 31 Linux but I've also posted windows links

Tools:
- ffmpeg - compiled from latest git (Windows build: https://ffmpeg.zeranoe.com/builds/)
- yusesope - tool V3: https://www.makemkv.com/forum/viewtopic ... 335#p85413
- eac3to portable version with wine - https://www.videohelp.com/software/eac3to
- tsmuxer modified for DV by a5180007/justdan96 - compiled from his github https://github.com/justdan96/tsMuxer (Windows build: https://bintray.com/justdan96/tsMuxer/t ... UI-Nightly) (Original forum thread: http://forum.doom9.org/showthread.php?t=176668&page=31)
Use the latest nightly tsMuxerGUI from this link, it's more recent compared the one posted a few pages back! and a5180007 also added support for eac3 dolby digital plus! (only 5.1)

First I demux the original bluray (will only work if I compile the latest FFMpeg git from source):

Code: Select all

ffmpeg -i bluray:/path/to/my/bluray -map 0:0 -c copy ./BL.hevc -map 0:1 -c copy ./EL.hevc -map 0:2 -c:a copy -strict -2 ./atmos.mp4

Now I have:
BL.hevc - Base Layer
EL.hevc - Enhanced Layer
atmos.mp4 - Dolby TrueHD Atmos audio

Now I use yusescope V3 tool to create a single layer DV file:

Code: Select all

python src/bl_el_rpu_builder.py -bl ./BL.hevc -el ./EL.hevc -of gemini_dv.hevc -mode 1

Now I also have:
gemini_dv.hevc - Full movie Single Layer DV

Now I use eac3to Gui to convert the atmos.mp4 to a compatible truehd+ac3 track for use with TSMuxeR:

Code: Select all

wine UsEac3To.exe

- Click Input File and select atmos.mp4
- Under Track Input and Output format change "ac3" to "thd+ac3" then click Add
- In the bottom click RUN CL and wait
When finished you will have a "atmos.mp4_.thd+ac3" file, rename this to "atmos.ac3"

Now launch justdan96's version of TsMuxerGUI then add your movie file: "gemini_dv.hevc" and audio file: "atmos.ac3".

So I have tried this method for Gemini man and Sonic 2019 and both of them freeze every 2 seconds during playback. My tv is lg oled c9. The files were stored in an external hdd connected to the tv via usb. All other souble layered dolby vision mp4 files created using the original method in the first post of this thread play fine. Maybe my tv can't properly play .ts file/single layered dolby vision file?

Well, i'm not sure, but it sounds like what my E6 did when i accidentially fed it a .mp4 with a Atmos thd+ac3 file renamed to .ac3 waaaay back.... My suggestion: Try with a clean ac3 file and see if that helps, and then figure out how to do a proper thd+ac3 track afterwards (or put both in and switch between them and see if one or both works)

Why don't just demux TrueHD track with tsmuxer? It's perfectly recognised, when muxing back with DV hevc file.

[deadchip12]

For Dolby Vision + Atmos:

Here's my success story for Gemini Man 2019 which is a 60fps movie which plays much more fluent.
I'm using Fedora 31 Linux but I've also posted windows links

Tools:
- ffmpeg - compiled from latest git (Windows build: https://ffmpeg.zeranoe.com/builds/)
- yusesope - tool V3: https://www.makemkv.com/forum/viewtopic ... 335#p85413
- eac3to portable version with wine - https://www.videohelp.com/software/eac3to
- tsmuxer modified for DV by a5180007/justdan96 - compiled from his github https://github.com/justdan96/tsMuxer (Windows build: https://bintray.com/justdan96/tsMuxer/t ... UI-Nightly) (Original forum thread: http://forum.doom9.org/showthread.php?t=176668&page=31)
Use the latest nightly tsMuxerGUI from this link, it's more recent compared the one posted a few pages back! and a5180007 also added support for eac3 dolby digital plus! (only 5.1)

First I demux the original bluray (will only work if I compile the latest FFMpeg git from source):

Code: Select all

ffmpeg -i bluray:/path/to/my/bluray -map 0:0 -c copy ./BL.hevc -map 0:1 -c copy ./EL.hevc -map 0:2 -c:a copy -strict -2 ./atmos.mp4

Now I have:
BL.hevc - Base Layer
EL.hevc - Enhanced Layer
atmos.mp4 - Dolby TrueHD Atmos audio

Now I use yusescope V3 tool to create a single layer DV file:

Code: Select all

python src/bl_el_rpu_builder.py -bl ./BL.hevc -el ./EL.hevc -of gemini_dv.hevc -mode 1

Now I also have:
gemini_dv.hevc - Full movie Single Layer DV

Now I use eac3to Gui to convert the atmos.mp4 to a compatible truehd+ac3 track for use with TSMuxeR:

Code: Select all

wine UsEac3To.exe

- Click Input File and select atmos.mp4
- Under Track Input and Output format change "ac3" to "thd+ac3" then click Add
- In the bottom click RUN CL and wait
When finished you will have a "atmos.mp4_.thd+ac3" file, rename this to "atmos.ac3"

Now launch justdan96's version of TsMuxerGUI then add your movie file: "gemini_dv.hevc" and audio file: "atmos.ac3".

So I have tried this method for Gemini man and Sonic 2019 and both of them freeze every 2 seconds during playback. My tv is lg oled c9. The files were stored in an external hdd connected to the tv via usb. All other souble layered dolby vision mp4 files created using the original method in the first post of this thread play fine. Maybe my tv can't properly play .ts file/single layered dolby vision file?

Well, i'm not sure, but it sounds like what my E6 did when i accidentially fed it a .mp4 with a Atmos thd+ac3 file renamed to .ac3 waaaay back.... My suggestion: Try with a clean ac3 file and see if that helps, and then figure out how to do a proper thd+ac3 track afterwards (or put both in and switch between them and see if one or both works)

I don't think the problem lies with the audio track because when I tried excluding the audio track the file still stuttered during playback.

[Domo0826]

I have compiled a TsMuxer that forces dvhe.05.06 profile. It works nice where 08.06 played choppy in my Lg. You can find it here http://katfile.com/1uvd80v1b0zd/tsMuxer ... ).zip.html

First of all, hello everyone. Recently I bought a LG C9 and I've been reading this thread for hours. I managed to get a MEL Dolby Vision film working well in my LG internal player with eac3to, yusesope 0.0.4 and then newest nightly tsmuxer. But when I do the same thing with a FEL film (Top Gun 4K Remastered) it stutters terribly (while triggering DV). So I tried your tsMuxeR that forces profile 05.06. and it plays without stutter, but the enhancement layer is completely off. It's treated as an 8K one I think, and I only see the top left cropped part of it, on top of the base layer stream. Any idea how to fix this?

[shawnc22]

If your only playback device is an LG internal player, stick with the mp4 method mentioned in the first few pages of this thread. TSMuxer is a means to get lossless Atmos+DV into a container; you’re gaining nothing from this if your player is the TV. Stuttering with certain titles is a known issue when played back on the LG player.

[Domo0826]

If your only playback device is an LG internal player, stick with the mp4 method mentioned in the first few pages of this thread. TSMuxer is a means to get lossless Atmos+DV into a container; you’re gaining nothing from this if your player is the TV. Stuttering with certain titles is a known issue when played back on the LG player.

I want multiple audio tracks and I have no clue how to do it with mp4. I'd love to know, if anyone could help me. Also I prefer DTS-HD MA over a Core 640 AC3 (for English). Also when I tried the mp4muxer (might be an old one, but it worked with a MEL flm before) method, the file wouldn't play at all .
What I did:

- eac3to demux BL and EL and ac3
- mp4muxer mux those 3 together with dv profile 7

Has there been any recent updates to this method? It's the only one I know that worked for me. I read about some mp4box method but that destroyed the DV metadata, somehow.
Also, how exactly do I add more audio tracks? Because when I tried Birds of Prey (MEL) with one track, played amazingly. When I tried adding another track, it wouldn't play at all.

Thanks for any advice on this.

[Trujax]

I have compiled a TsMuxer that forces dvhe.05.06 profile. It works nice where 08.06 played choppy in my Lg. You can find it here http://katfile.com/1uvd80v1b0zd/tsMuxer ... ).zip.html

First of all, hello everyone. Recently I bought a LG C9 and I've been reading this thread for hours. I managed to get a MEL Dolby Vision film working well in my LG internal player with eac3to, yusesope 0.0.4 and then newest nightly tsmuxer. But when I do the same thing with a FEL film (Top Gun 4K Remastered) it stutters terribly (while triggering DV). So I tried your tsMuxeR that forces profile 05.06. and it plays without stutter, but the enhancement layer is completely off. It's treated as an 8K one I think, and I only see the top left cropped part of it, on top of the base layer stream. Any idea how to fix this?

Sorry, my modification only forces profile 05.06, the processing is the one programmed by tsmuxer. Changing that is beyond my understanding.