Dolby Vision now possible through MP4 Mux.

[shawnc22]

they didn't remove it, just changed the location:
https://professional.dolby.com/siteasse ... _09_16.pdf

yes, it is called xxx_64bit, but not xxx_64bit_mutithread. Two completely different things.

also for shield, you don't need to use Dolby's mp4muxer.
you can use your tsMuxer (04.06 fix). put output of yusecope's tool there and add sound, that's it.
for profile 8 you can try nightly release tsMuxer from 16-th March 2020.
https://bintray.com/justdan96/tsMuxer/t ... 1-36#files

No, don’t do this. If you’re making BL+EL+RPU files, stick with the 04.06 version of tsmuxer you’ve been using. Profile 8 is not the correct profile to use for these files.

[box4m]

your powerful CPU means nothing if program uses only one thread. Since it is run from CMD, then most probably it is.

AFAIK you can create an mp4 with TrueHD, but I am not sure any existent player can play TrueHD from mp4. That's why people are using tsMuxer to mix output from yusecope's tool and TrueHD+Atmos.
try to create a profile 8, that should work on Shield TV.

I will try profile 8 thanks.
Regarding only using one thread, ye maybe, but its called mp4muxer_64bit

edit: where can i read about the profiles btw? dolby seems to have removed the pdf?

they didn't remove it, just changed the location:
https://professional.dolby.com/siteasse ... _09_16.pdf

yes, it is called xxx_64bit, but not xxx_64bit_mutithread. Two completely different things.

also for shield, you don't need to use Dolby's mp4muxer.
you can use your tsMuxer (04.06 fix). put output of yusecope's tool there and add sound, that's it.
for profile 8 you can try nightly release tsMuxer from 16-th March 2020.
https://bintray.com/justdan96/tsMuxer/t ... 1-36#files

tsmuxer finishes in 0seconds when trying to mux to .ts "finished with error code -1", not sure if there are logs?

[MastaG]

A little unrelated to this topic.
But I'm trying to demux the blu-ray discs of westworld season 1 and 2.
But there's so many files on those discs.
How do I know which playlist contains a certain episode?

[planet_hoarder]

they didn't remove it, just changed the location:
https://professional.dolby.com/siteasse ... _09_16.pdf

yes, it is called xxx_64bit, but not xxx_64bit_mutithread. Two completely different things.

also for shield, you don't need to use Dolby's mp4muxer.
you can use your tsMuxer (04.06 fix). put output of yusecope's tool there and add sound, that's it.
for profile 8 you can try nightly release tsMuxer from 16-th March 2020.
https://bintray.com/justdan96/tsMuxer/t ... 1-36#files

No, don’t do this. If you’re making BL+EL+RPU files, stick with the 04.06 version of tsmuxer you’ve been using. Profile 8 is not the correct profile to use for these files.

Dolby's white paper says profile 4 needs two layers. yusecope tool combines two layers into one - BL+EL+RPU.hevc
even readme from latest broken mp4muxer says so:

Code: Select all

           "To multiplex Dolby vision BL+EL+RPU file into a .mp4 file with EC-3 audio track:\n"
           "   mp4muxer -i ves_bl_el_rpu.265 -i audio.ec3 -o output.mp4 --dv-profile 8 \n" 
           "            --dv-bl-compatible-id 2 --mpeg4-comp-brand mp42,iso6,isom,msdh,dby1 --overwrite \n"
           "   Note: For the Dolby vision profile 8, dv-bl-compatible-id is necessary. \n\n"

afaik, profile 4 and 7 (and dropped 6) needs second physical layer. At least when I create profile 4 from tsMuxer, it stutters on my LG OLED.
when I create profile 4,6 or 7 from old mp4muxer_64bit, plays perfectly.
when I create profile 8 from tsMuxer with output BL_EL_RPU.hevc from yusecope's tool - plays in DV on my TV.
too bad latest release of dolby's mp4muxer is faulty (created profile 8 plays in HDR), otherwise would have been a nice additional tool.

NOW. the biggest question is how to spot a difference between DV profiles (4,7,8) on the screen.
I wonder, if profile 8 is basically combined 4 and 6, with traces of 7 and older 2,3; then it is an ultimate DV profile for all. I just want to know if there is any difference.

[planet_hoarder]

A little unrelated to this topic.
But I'm trying to demux the blu-ray discs of westworld season 1 and 2.
But there's so many files on those discs.
How do I know which playlist contains a certain episode?

try create mkv episodes using makemkv. otherwise, no idea

[shawnc22]

afaik, profile 4 and 7 (and dropped 6) needs second physical layer. At least when I create profile 4 from tsMuxer, it stutters on my LG OLED.
when I create profile 4,6 or 7 from old mp4muxer_64bit, plays perfectly.
when I create profile 8 from tsMuxer with output BL_EL_RPU.hevc from yusecope's tool - plays in DV on my TV.
too bad latest release of dolby's mp4muxer is faulty (created profile 8 plays in HDR), otherwise would have been a nice additional tool.

NOW. the biggest question is how to spot a difference between DV profiles (4,7,8) on the screen.
I wonder, if profile 8 is basically combined 4 and 6, with traces of 7 and older 2,3; then it is an ultimate DV profile for all. I just want to know if there is any difference.

already have had this discussion once before:

https://makemkv.com/forum/viewtopic.php ... 165#p88345

and from one of the tsmuxer dev's:

https://makemkv.com/forum/viewtopic.php ... 180#p88398

[planet_hoarder]

afaik, profile 4 and 7 (and dropped 6) needs second physical layer. At least when I create profile 4 from tsMuxer, it stutters on my LG OLED.
when I create profile 4,6 or 7 from old mp4muxer_64bit, plays perfectly.
when I create profile 8 from tsMuxer with output BL_EL_RPU.hevc from yusecope's tool - plays in DV on my TV.
too bad latest release of dolby's mp4muxer is faulty (created profile 8 plays in HDR), otherwise would have been a nice additional tool.

NOW. the biggest question is how to spot a difference between DV profiles (4,7,8) on the screen.
I wonder, if profile 8 is basically combined 4 and 6, with traces of 7 and older 2,3; then it is an ultimate DV profile for all. I just want to know if there is any difference.

already have had this discussion once before:

https://makemkv.com/forum/viewtopic.php ... 165#p88345

and from one of the tsmuxer dev's:

https://makemkv.com/forum/viewtopic.php ... 180#p88398

yeah, the theory makes sense, but I'd like to know if there is a visual difference.
if the EL makes picture in 12 bit, then it's a waste, since no TV has 12 bit panel. Means BL+RPU is more than enough for Dolby Vison.
Also dolby's whitepaper says profile 8 is not finalized. Maybe that's why profile 8 with BL+EL+RPU works for LG internal player, when profile 5 doesn't work at all.
mp4muxer_64bit always creates mp4 two tracks BL and EL+RPU (at least for profile 4,6,7 that works on LG internal player), where EL+RPU gets the dolby vision profile and BL stays HDR10.
Maybe that's why mp4's in profile 5 is not working and profile 8 plays in HDR for me. I need to create them again and check MediaInfo.

[box4m]

Weird question i guess but, anyone know of a player for androidtv/shield that can either playback 23.976p movies @ 24p, speed them up.
Or if you know of an application that could speedup the video and audio without stripping the DV data?

[flashback8]

Weird question i guess but, anyone know of a player for androidtv/shield that can either playback 23.976p movies @ 24p, speed them up.
Or if you know of an application that could speedup the video and audio without stripping the DV data?

AFAIK, all you have to do is run everything through MKVToolnix and manually set the frame rate. However, you'll still have to adjust the audio speed via other means.

[MastaG]

afaik, profile 4 and 7 (and dropped 6) needs second physical layer. At least when I create profile 4 from tsMuxer, it stutters on my LG OLED.
when I create profile 4,6 or 7 from old mp4muxer_64bit, plays perfectly.
when I create profile 8 from tsMuxer with output BL_EL_RPU.hevc from yusecope's tool - plays in DV on my TV.
too bad latest release of dolby's mp4muxer is faulty (created profile 8 plays in HDR), otherwise would have been a nice additional tool.

NOW. the biggest question is how to spot a difference between DV profiles (4,7,8) on the screen.
I wonder, if profile 8 is basically combined 4 and 6, with traces of 7 and older 2,3; then it is an ultimate DV profile for all. I just want to know if there is any difference.

already have had this discussion once before:

https://makemkv.com/forum/viewtopic.php ... 165#p88345

and from one of the tsmuxer dev's:

https://makemkv.com/forum/viewtopic.php ... 180#p88398

yeah, the theory makes sense, but I'd like to know if there is a visual difference.
if the EL makes picture in 12 bit, then it's a waste, since no TV has 12 bit panel. Means BL+RPU is more than enough for Dolby Vison.
Also dolby's whitepaper says profile 8 is not finalized. Maybe that's why profile 8 with BL+EL+RPU works for LG internal player, when profile 5 doesn't work at all.
mp4muxer_64bit always creates mp4 two tracks BL and EL+RPU (at least for profile 4,6,7 that works on LG internal player), where EL+RPU gets the dolby vision profile and BL stays HDR10.
Maybe that's why mp4's in profile 5 is not working and profile 8 plays in HDR for me. I need to create them again and check MediaInfo.

So it's a bit confusing then.
Let's say I would like to remux some dual layer bluray discs to a single pid video file without discarding the enhanced layer (which turns it into 12bit video).
I'd demux the base layer and enhanced layer from the blu-ray disc and then I will use yusesope's tool to create a single pid video file (BL + EL + RPU / mode 1).
So I have my single pid hevc file (BL+EL+RPU).

I can either store it into a mp4 container using Dolby's mp4muxer, or use TSmuxer which has the ability to store HD audio as well into a TS container.

Which profile should I assign to the single pid video file inside this container?

[planet_hoarder]

already have had this discussion once before:

https://makemkv.com/forum/viewtopic.php ... 165#p88345

and from one of the tsmuxer dev's:

https://makemkv.com/forum/viewtopic.php ... 180#p88398

yeah, the theory makes sense, but I'd like to know if there is a visual difference.
if the EL makes picture in 12 bit, then it's a waste, since no TV has 12 bit panel. Means BL+RPU is more than enough for Dolby Vison.
Also dolby's whitepaper says profile 8 is not finalized. Maybe that's why profile 8 with BL+EL+RPU works for LG internal player, when profile 5 doesn't work at all.
mp4muxer_64bit always creates mp4 two tracks BL and EL+RPU (at least for profile 4,6,7 that works on LG internal player), where EL+RPU gets the dolby vision profile and BL stays HDR10.
Maybe that's why mp4's in profile 5 is not working and profile 8 plays in HDR for me. I need to create them again and check MediaInfo.

So it's a bit confusing then.
Let's say I would like to remux some dual layer bluray discs to a single pid video file without discarding the enhanced layer (which turns it into 12bit video).
I'd demux the base layer and enhanced layer from the blu-ray disc and then I will use yusesope's tool to create a single pid video file (BL + EL + RPU / mode 1).
So I have my single pid hevc file (BL+EL+RPU).

I can either store it into a mp4 container using Dolby's mp4muxer, or use TSmuxer which has the ability to store HD audio as well into a TS container.

Which profile should I assign to the single pid video file inside this container?

Good question.
It depends which is playback device. If you can playback lossless audio (with proper speakers) with DV, then use tsMuxer. Otherwise mp4muxer_64bit is the best tool.

If you use mp4muxer_64bit, then you don't need yusecope's tool at all. It can create perfect DV mp4. If your device supports Profile 7, then use it.

with tsMuxer, I was only able to make work nightly release from 16th March. It creates profile 8 from BL_EL_RPU.hevc (yusecope's tool), and triggers DV on my LG OLED. Any other profile (4 or 6) from tsMuxer was not properly working for me.
Maybe because profile 8 is still work in progress and it just plays everything.

[MastaG]

yeah, the theory makes sense, but I'd like to know if there is a visual difference.
if the EL makes picture in 12 bit, then it's a waste, since no TV has 12 bit panel. Means BL+RPU is more than enough for Dolby Vison.
Also dolby's whitepaper says profile 8 is not finalized. Maybe that's why profile 8 with BL+EL+RPU works for LG internal player, when profile 5 doesn't work at all.
mp4muxer_64bit always creates mp4 two tracks BL and EL+RPU (at least for profile 4,6,7 that works on LG internal player), where EL+RPU gets the dolby vision profile and BL stays HDR10.
Maybe that's why mp4's in profile 5 is not working and profile 8 plays in HDR for me. I need to create them again and check MediaInfo.

So it's a bit confusing then.
Let's say I would like to remux some dual layer bluray discs to a single pid video file without discarding the enhanced layer (which turns it into 12bit video).
I'd demux the base layer and enhanced layer from the blu-ray disc and then I will use yusesope's tool to create a single pid video file (BL + EL + RPU / mode 1).
So I have my single pid hevc file (BL+EL+RPU).

I can either store it into a mp4 container using Dolby's mp4muxer, or use TSmuxer which has the ability to store HD audio as well into a TS container.

Which profile should I assign to the single pid video file inside this container?

Good question.
It depends which is playback device. If you can playback lossless audio (with proper speakers) with DV, then use tsMuxer. Otherwise mp4muxer_64bit is the best tool.

If you use mp4muxer_64bit, then you don't need yusecope's tool at all. It can create perfect DV mp4. If your device supports Profile 7, then use it.

with tsMuxer, I was only able to make work nightly release from 16th March. It creates profile 8 from BL_EL_RPU.hevc (yusecope's tool), and triggers DV on my LG OLED. Any other profile (4 or 6) from tsMuxer was not properly working for me.
Maybe because profile 8 is still work in progress and it just plays everything.

I noticed the same, but I think the reason for the stutters in profile 4 and 6 is because the TV's internal player is not capable of handling the full enhanced layer of such high bitrate movies.
I think when using profile 8 it's discarding the enhanced layer and only processing the metadata.. like using BL+RPU (mode 2).

[planet_hoarder]

So it's a bit confusing then.
Let's say I would like to remux some dual layer bluray discs to a single pid video file without discarding the enhanced layer (which turns it into 12bit video).
I'd demux the base layer and enhanced layer from the blu-ray disc and then I will use yusesope's tool to create a single pid video file (BL + EL + RPU / mode 1).
So I have my single pid hevc file (BL+EL+RPU).

I can either store it into a mp4 container using Dolby's mp4muxer, or use TSmuxer which has the ability to store HD audio as well into a TS container.

Which profile should I assign to the single pid video file inside this container?

Good question.
It depends which is playback device. If you can playback lossless audio (with proper speakers) with DV, then use tsMuxer. Otherwise mp4muxer_64bit is the best tool.

If you use mp4muxer_64bit, then you don't need yusecope's tool at all. It can create perfect DV mp4. If your device supports Profile 7, then use it.

with tsMuxer, I was only able to make work nightly release from 16th March. It creates profile 8 from BL_EL_RPU.hevc (yusecope's tool), and triggers DV on my LG OLED. Any other profile (4 or 6) from tsMuxer was not properly working for me.
Maybe because profile 8 is still work in progress and it just plays everything.

I noticed the same, but I think the reason for the stutters in profile 4 and 6 is because the TV's internal player is not capable of handling the full enhanced layer of such high bitrate movies.
I think when using profile 8 it's discarding the enhanced layer and only processing the metadata.. like using BL+RPU (mode 2).

No LG tv is able to playback dual layer DV profile 7 with FEL over 8MB/s. Only 60fps (Gemini Man) gave a problem.
profile 8 cannot discard anything - I create using mode 1 so it is BL+EL+RPU output

[MastaG]

Good question.
It depends which is playback device. If you can playback lossless audio (with proper speakers) with DV, then use tsMuxer. Otherwise mp4muxer_64bit is the best tool.

If you use mp4muxer_64bit, then you don't need yusecope's tool at all. It can create perfect DV mp4. If your device supports Profile 7, then use it.

with tsMuxer, I was only able to make work nightly release from 16th March. It creates profile 8 from BL_EL_RPU.hevc (yusecope's tool), and triggers DV on my LG OLED. Any other profile (4 or 6) from tsMuxer was not properly working for me.
Maybe because profile 8 is still work in progress and it just plays everything.

I noticed the same, but I think the reason for the stutters in profile 4 and 6 is because the TV's internal player is not capable of handling the full enhanced layer of such high bitrate movies.
I think when using profile 8 it's discarding the enhanced layer and only processing the metadata.. like using BL+RPU (mode 2).

No LG tv is able to playback dual layer DV profile 7 with FEL over 8MB/s. Only 60fps (Gemini Man) gave a problem.
profile 8 cannot discard anything - I create using mode 1 so it is BL+EL+RPU output

Great, then I'll hack up the source to put profile 8 for everything

[shawnc22]

I noticed the same, but I think the reason for the stutters in profile 4 and 6 is because the TV's internal player is not capable of handling the full enhanced layer of such high bitrate movies.
I think when using profile 8 it's discarding the enhanced layer and only processing the metadata.. like using BL+RPU (mode 2).

No LG tv is able to playback dual layer DV profile 7 with FEL over 8MB/s. Only 60fps (Gemini Man) gave a problem.
profile 8 cannot discard anything - I create using mode 1 so it is BL+EL+RPU output

Great, then I'll hack up the source to put profile 8 for everything

If you're playing it back on the Shield, I honestly don't think it matters what profile you put it in. It seems to me that as long as the software (Plex, MXPlayer, MrMC, etc) can recognize the DV stream, it will pass it on to the hardware decoder. I have looked at the Plex exoplayer logs when attempting to play a profile 6 video that is considered deprecated and has no confirmed support. The logs show that the software doesn't recognize the dvhe.06.0x codec (it does for dvhe.04.0x), but still acknowledges that it contains a DV stream, so it passes it onto the hardware decoder for playback.

From a pure dolby specs standpoint, a single PID BL+EL+RPU stream that has HDR10 backwards compatibility should be either 6 or 7 (our case here). It should not be profile 8 as the latest dolby profiles specsheet clearly states that it is a single layer profile.