--dv-profile <arg> = Sets the Dolby Vision profile. This option is MANDATORY for
DoVi elementary stream: Valid profile values are:
4 - dvhe.04, BL codec: HEVC10; EL codec: HEVC10; BL compatibility: SDR/HDR.
5 - dvhe.05, BL codec: HEVC10; EL codec: N/A; BL compatibility: None.
7 - dvhe.07, BL codec: HEVC10; EL codec: HEVC10; BL compatibility: Blue-ray HDR10.
8 - dvhe.08, BL codec: HEVC10; EL codec: N/A; BL compatibility: SDR/HDR.
9 - dvav.09, BL codec: AVC; EL codec: N/A; BL compatibility: SDR/HDR
mp4muxer profile 6 has been removed on 12 Feb 20. The latest document DolbyVisionProfilesLevels_v1_3_2_2019_09_16.pdf mentions BL compatibility with SDR (VUI 1,1,1) only. I've asked Dolby mp4muxer developper on Github to clarify compatibility with CTA HDR10, and whether the document would be revised accordingly.
Answer from Dolby: "Profile 4 is a Dolby Vision specific dual layer format where the base layer is SDR ( BT.1886, ITU-R BT.709, YCbCr 4:2:0) and then the enhancement layer contains the Dolby Vision data. So its is only cross compatible with SDR and not HDR10. That is why the current profile and levels doc was updated to reflect that."
So Profile 6 is the only profile (besides 5 & 7) that we can create from the tools we have, but are not "officially" supported from Dolby anymore.
And we would need exoplayer to add this back in, and also Plex to make sure they use it to be fully compatible?
Okay.. I couldn't let go of Gemini Man on my LG C8.
It appears that when I use Dolby Lab's mp4muxer version 1.0.0 (v1.0.1 is broken) and I mux both the base and enhanced layer separately using --dv-profile 7 and ac3 audio. It DOES indeed play when I turn off all processing options on my TV (motion blah, noise reduction blah etc..).
It still stutters a very tiny bit though..(probably because the movie is 60fps).
But I can't achieve the same when I 'blend' both layers using yusesope's tool in mode 1 (BL+EL+RPU).
I tried to mux the resulting hevc with both mp4muxer (profile 4) and the latest tsmuxer nightly (which gives it profile 6).
In both muxes it skips every one-two seconds.
That makes me wonder whether the BL+EL+RPU 'merged' videos somehow differ from dual layer (profile 7) muxes.
Because I would imagine that blending them together with yusesope's tool would make it easier for the TV to decode since it's a single track..
Okay.. I couldn't let go of Gemini Man on my LG C8.
It appears that when I use Dolby Lab's mp4muxer version 1.0.0 (v1.0.1 is broken) and I mux both the base and enhanced layer separately using --dv-profile 7 and ac3 audio. It DOES indeed play when I turn off all processing options on my TV (motion blah, noise reduction blah etc..).
It still stutters a very tiny bit though..(probably because the movie is 60fps).
But I can't achieve the same when I 'blend' both layers using yusesope's tool in mode 1 (BL+EL+RPU).
I tried to mux the resulting hevc with both mp4muxer (profile 4) and the latest tsmuxer nightly (which gives it profile 6).
In both muxes it skips every one-two seconds.
That makes me wonder whether the BL+EL+RPU 'merged' videos somehow differ from dual layer (profile 7) muxes.
Because I would imagine that blending them together with yusesope's tool would make it easier for the TV to decode since it's a single track..
Have you also tried muxing yusecope's resulting hevc in profile 7 with mp4muxer?
Okay.. I couldn't let go of Gemini Man on my LG C8.
It appears that when I use Dolby Lab's mp4muxer version 1.0.0 (v1.0.1 is broken) and I mux both the base and enhanced layer separately using --dv-profile 7 and ac3 audio. It DOES indeed play when I turn off all processing options on my TV (motion blah, noise reduction blah etc..).
It still stutters a very tiny bit though..(probably because the movie is 60fps).
But I can't achieve the same when I 'blend' both layers using yusesope's tool in mode 1 (BL+EL+RPU).
I tried to mux the resulting hevc with both mp4muxer (profile 4) and the latest tsmuxer nightly (which gives it profile 6).
In both muxes it skips every one-two seconds.
That makes me wonder whether the BL+EL+RPU 'merged' videos somehow differ from dual layer (profile 7) muxes.
Because I would imagine that blending them together with yusesope's tool would make it easier for the TV to decode since it's a single track..
Have you also tried muxing yusecope's resulting hevc in profile 7 with mp4muxer?
Good one!
I haven't with v1.0.0, good one
I'll try and report back.
Forgive me if this has already been mentioned, but if profile 5 is single layer, then wouldn't it work in MKV format without any modifications? As far as I have read the only thing preventing DV in MKV is the lack of handling multiple layers. MKV is a lot for convenient for use over TS.
technically yes, but mkvtoolnix needs to add the proper dv descriptors first similar to what tsmuxer has done. right now it makes an mkv fine but loses the dv data in process.
Forgive me if this has already been mentioned, but if profile 5 is single layer, then wouldn't it work in MKV format without any modifications? As far as I have read the only thing preventing DV in MKV is the lack of handling multiple layers. MKV is a lot for convenient for use over TS.
technically yes, but mkvtoolnix needs to add the proper dv descriptors first similar to what tsmuxer has done. right now it makes an mkv fine but loses the dv data in process.
Forgive me if this has already been mentioned, but if profile 5 is single layer, then wouldn't it work in MKV format without any modifications? As far as I have read the only thing preventing DV in MKV is the lack of handling multiple layers. MKV is a lot for convenient for use over TS.
technically yes, but mkvtoolnix needs to add the proper dv descriptors first similar to what tsmuxer has done. right now it makes an mkv fine but loses the dv data in process.
This is basically just what mp4muxer does (for an mp4), that's why the actual .exe is so small.
Forgive me if this has already been mentioned, but if profile 5 is single layer, then wouldn't it work in MKV format without any modifications? As far as I have read the only thing preventing DV in MKV is the lack of handling multiple layers. MKV is a lot for convenient for use over TS.
technically yes, but mkvtoolnix needs to add the proper dv descriptors first similar to what tsmuxer has done. right now it makes an mkv fine but loses the dv data in process.
This is basically just what mp4muxer does (for an mp4), that's why the actual .exe is so small.
No Atmos in .mp4 so a profile 5 mkv with Atmos would be ideal.
This is basically just what mp4muxer does (for an mp4), that's why the actual .exe is so small.
Pretty much, though with .ts / .m2ts now working with dv I'm not sure we need mkv. I suppose PGS subtitles and proper chapter support is handy to some people (pgs to srt is such a simple conversion, and who even uses chapters? ).
This is basically just what mp4muxer does (for an mp4), that's why the actual .exe is so small.
Pretty much, though with .ts / .m2ts now working with dv I'm not sure we need mkv. I suppose PGS subtitles and proper chapter support is handy to some people (pgs to srt is such a simple conversion, and who even uses chapters? ).
I still use chapters! to the point of digging up an old plex metadata plugin to add them onto ts files during the import process
).