I was going to give that a try, too, when I got home, but I can try First Man also. I'm wondering if it might be because the Doctor Sleep disc is also in HDR10+. The EL might be a little different in that case?RESET_9999 wrote: ↑Tue Mar 10, 2020 11:14 pmyep, I think Doctor Sleep EL is not processed. It gives me an error with V1 tool and with V2 tool , EL analyzing stays at 0%.
Dolby Vision now possible through MP4 Mux.
Re: Dolby Vision now possible through MP4 Mux.
Re: Dolby Vision now possible through MP4 Mux.
That's interesting, I didn't realize it's in HDR10+, though that explains the descriptor in mediainfo. The file did not give any errors in the tool, and it did finish to 100%.shawnc22 wrote: ↑Tue Mar 10, 2020 11:40 pmI was going to give that a try, too, when I got home, but I can try First Man also. I'm wondering if it might be because the Doctor Sleep disc is also in HDR10+. The EL might be a little different in that case?RESET_9999 wrote: ↑Tue Mar 10, 2020 11:14 pmyep, I think Doctor Sleep EL is not processed. It gives me an error with V1 tool and with V2 tool , EL analyzing stays at 0%.
Re: Dolby Vision now possible through MP4 Mux.
hey has anyone who uses MX Player on the Shield Pro tried just starting a video-track only dv mp4, and then pausing, going to menu - audio - open, then choosing your audio.thd atmos file from its folder? curious if this worked the whole time and we didn't have to figure out how to mux it in. I can do this on the firestick 4k fine, but only with dd+ or pcm 7.1 since it doesn't do hd-audio.
-
- Posts: 285
- Joined: Thu May 02, 2019 2:49 am
Re: Dolby Vision now possible through MP4 Mux.
I followed your instruction but .ts file does not play on my c9's internal media player.ATD555 wrote: ↑Tue Mar 10, 2020 2:37 pmYou should try using TSMuxer and just throw the original video file in it and remux to a .ts using this build of TSMuxer: https://drive.google.com/open?id=1Gq5TA ... B1io4OwHW9deadchip12 wrote: ↑Tue Mar 10, 2020 9:40 amLG Oled C9 via external hdd.
One question though: Gemini man dolby vision does not play at the correct 60 fps using the original method (remux two HEVCs layers into an MP4 container using mp4muxer). Will it play correctly using the new method (remux two HEVCs layers into an .ts container using yusesope's tool)?
Re: Dolby Vision now possible through MP4 Mux.
Just tried First Man and looks like everything went well. DV and Atmos triggered in plex and here's the mediainfo from the resulting TS:
Code: Select all
General
ID : 1 (0x1)
Complete name : Z:\TS\First Man\First Man.ts
Format : MPEG-TS
File size : 68.4 GiB
Duration : 2 h 20 min
Overall bit rate mode : Variable
Overall bit rate : 69.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.08.06, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 2 h 20 min
Bit rate : 65.6 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.330
Stream size : 64.6 GiB (94%)
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 : 285 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 : 2 h 20 min
Bit rate mode : Variable
Bit rate : 448 kb/s
Maximum bit rate : 4 533 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
Stream size : 452 MiB (1%)
Language : English
Service kind : Complete Main
Number of dynamic objects : 11
Bed channel count : 1 channel
Bed channel configuration : LFE
Re: Dolby Vision now possible through MP4 Mux.
Thanks for trying that. I tried it again, but still no luck. Are you demuxing the m2ts using tsMuxer?shawnc22 wrote: ↑Wed Mar 11, 2020 4:31 amJust tried First Man and looks like everything went well. DV and Atmos triggered in plex and here's the mediainfo from the resulting TS:
Code: Select all
General ID : 1 (0x1) Complete name : Z:\TS\First Man\First Man.ts Format : MPEG-TS File size : 68.4 GiB Duration : 2 h 20 min Overall bit rate mode : Variable Overall bit rate : 69.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.08.06, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible Codec ID : 36 Duration : 2 h 20 min Bit rate : 65.6 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.330 Stream size : 64.6 GiB (94%) 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 : 285 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 : 2 h 20 min Bit rate mode : Variable Bit rate : 448 kb/s Maximum bit rate : 4 533 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 Stream size : 452 MiB (1%) Language : English Service kind : Complete Main Number of dynamic objects : 11 Bed channel count : 1 channel Bed channel configuration : LFE
Re: Dolby Vision now possible through MP4 Mux.
yeah, same tsmuxer version that does the initial demuxing and the remuxing at the end.
Re: Dolby Vision now possible through MP4 Mux.
With Plex client on HTPC, should I use the TS dual layer or single layer method? Dual layer being easiest...
Re: Dolby Vision now possible through MP4 Mux.
I agree on everything except on these statements:
Regardless of the type of EL (fEL or mEL), in the case of a dvhe.04 or dvhe.07 profile, the Dolby Vision Composer accepts synchronized decoded BL and EL video frames and metadata information and uses metadata to reconstruct 12bit Dolby Vision video.
In support of this hypothesis, I took a look at the data in the header of a NAL RPU:
The vdr_bit_depth parameter specifies the bit depth of the reconstructed Dolby Vision video signal.
This is derived by vdr_bit_depth = vdr_bit_depth_minus8 + 8
vdr_bit_depth_minus8 is equal to 4 in both fEL and mEL stream (so vdr_bit_depth = 12)
I leave you the code to analyze the header of an RPU (HERE)
I have not converted the raw HEVC stream to m2ts because I have not followed the events related to tsMuxeR (I have not yet understood why a BL + EL + RPU stream is flagged as dvhe.08).
If someone wants to take care of it, find everything you need at the previous link.
My Dolby Vision are a series of hexadecimal codes that scroll across the screen
I believe that it is not possible to discard anything.mike admin wrote: ↑Tue Mar 10, 2020 8:16 pmDV streams may have different profiles and configurations.
Single layer: Video + RPU stream
Double layer: Video (base) layer + Video (extension) layer (difference between 12bit and 10bit picture) + RPU stream.
Profile 7 is always double-layer and may be authored in FEL (full EL) or MEL configuration (minimal EL). In MEL configuration the video extension layer contains all zero pictures (no 12-bit data) and could be safely discarded.
Regardless of the type of EL (fEL or mEL), in the case of a dvhe.04 or dvhe.07 profile, the Dolby Vision Composer accepts synchronized decoded BL and EL video frames and metadata information and uses metadata to reconstruct 12bit Dolby Vision video.
In support of this hypothesis, I took a look at the data in the header of a NAL RPU:
Code: Select all
############### MEL RPU ###############
forbidden_zero_bit: 0
nal_unit_type: 62
nuh_layer_id: 0
nuh_temporal_id_plus1: 1
rpu_type: 2
rpu_format: 18
vdr_rpu_profile: 1
vdr_rpu_level: 0
vdr_seq_info_present_flag: 1
chroma_resampling_explicit_filter_flag: 0
coefficient_data_type: 0
coefficient_log2_denom: 23
vdr_rpu_normalized_idc: 1
BL_video_full_range_flag: 0
BL_bit_depth_minus8: 2
EL_bit_depth_minus8: 2
vdr_bit_depth_minus_8: 4
spatial_resampling_filter_flag: 0
reserved_zero_3bits: 0
el_spatial_resampling_filter_flag: 1
disable_residual_flag: 0
vdr_dm_metadata_present_flag: 1
use_prev_vdr_rpu_flag: 0
vdr_rpu_id: 0
mapping_color_space: 0
mapping_chroma_format_idc: 0
num_pivots_minus_2: [0, 0, 0]
pred_pivot_value: [[0, 1023], [0, 1023], [0, 1023]]
nlq_method_idc: 0
num_x_partitions_minus1: 2046
num_y_partitions_minus1: 0
############### FEL RPU ###############
forbidden_zero_bit: 0
nal_unit_type: 62
nuh_layer_id: 0
nuh_temporal_id_plus1: 1
rpu_type: 2
rpu_format: 18
vdr_rpu_profile: 1
vdr_rpu_level: 0
vdr_seq_info_present_flag: 1
chroma_resampling_explicit_filter_flag: 0
coefficient_data_type: 0
coefficient_log2_denom: 23
vdr_rpu_normalized_idc: 1
BL_video_full_range_flag: 0
BL_bit_depth_minus8: 2
EL_bit_depth_minus8: 2
vdr_bit_depth_minus_8: 4
spatial_resampling_filter_flag: 0
reserved_zero_3bits: 0
el_spatial_resampling_filter_flag: 1
disable_residual_flag: 0
vdr_dm_metadata_present_flag: 1
use_prev_vdr_rpu_flag: 0
vdr_rpu_id: 0
mapping_color_space: 0
mapping_chroma_format_idc: 0
num_pivots_minus_2: [7, 0, 0]
pred_pivot_value: [[0, 128, 128, 128, 128, 128, 128, 128, 127], [0, 1023], [0, 1023]]
nlq_method_idc: 0
num_x_partitions_minus1: 2046
num_y_partitions_minus1: 0
This is derived by vdr_bit_depth = vdr_bit_depth_minus8 + 8
vdr_bit_depth_minus8 is equal to 4 in both fEL and mEL stream (so vdr_bit_depth = 12)
I leave you the code to analyze the header of an RPU (HERE)
I made two Terminator clips (fEL). I had difficulty cutting the movie so, for safety, I made two clips one of 20sec and one of 40 sec. Find everything HEREmike admin wrote: ↑Tue Mar 10, 2020 8:16 pmAlso, can anyone find a good sample for FEL stream of roughly the same duration - 23 seconds, about 100 MB? Please PM/email me if you have M2TS and I'll produce MKV out of it.
I have not converted the raw HEVC stream to m2ts because I have not followed the events related to tsMuxeR (I have not yet understood why a BL + EL + RPU stream is flagged as dvhe.08).
If someone wants to take care of it, find everything you need at the previous link.
At the moment I can't test anything because I don't have any device that supports Dolby Vision.
My Dolby Vision are a series of hexadecimal codes that scroll across the screen
Re: Dolby Vision now possible through MP4 Mux.
Is it possible that because it's being flagged as dvhe.08, the EL is being ignored on playback even though the DV flag is triggered? This could explain why somebody previously reported that the credit scene in power rangers did not look like it was in DV even though DV was on. Unfortunately can't do any eye comparison tests on my own as I don't have a DV-capable UHD player either
Re: Dolby Vision now possible through MP4 Mux.
Could be.shawnc22 wrote: ↑Wed Mar 11, 2020 3:55 pmIs it possible that because it's being flagged as dvhe.08, the EL is being ignored on playback even though the DV flag is triggered? This could explain why somebody previously reported that the credit scene in power rangers did not look like it was in DV even though DV was on.
The only profiles that support BL + EL + RPU are 4 and 7 (6 is no longer in use).
mp4muxer should be used for testing purposes.
Re: Dolby Vision now possible through MP4 Mux.
I am trying to use your tool to create BL + EL + RPU, i have extracted BL & EL hevc streams from my mkv using ffmpeg but the tool always exists out at
BL ANALYSYS: 100.0% EL ANALYSYS 0.0% BL_EL_RPU WRITING 89.8%
i tried demuxing with tsMuxer same result .With eac3to it worked , but the playback after muxing with mp4muxer is very dark and colors are washed out .
Using HDD via USB on B9
-
- Posts: 88
- Joined: Mon Sep 03, 2018 10:36 am
Re: Dolby Vision now possible through MP4 Mux.
Same with Power RangersArbigator wrote: ↑Wed Mar 11, 2020 12:07 amThat's interesting, I didn't realize it's in HDR10+, though that explains the descriptor in mediainfo. The file did not give any errors in the tool, and it did finish to 100%.shawnc22 wrote: ↑Tue Mar 10, 2020 11:40 pmI was going to give that a try, too, when I got home, but I can try First Man also. I'm wondering if it might be because the Doctor Sleep disc is also in HDR10+. The EL might be a little different in that case?RESET_9999 wrote: ↑Tue Mar 10, 2020 11:14 pm
yep, I think Doctor Sleep EL is not processed. It gives me an error with V1 tool and with V2 tool , EL analyzing stays at 0%.
Re: Dolby Vision now possible through MP4 Mux.
the mkv files mike posted when played on my oppo to my sony x940e, they only comes up as hdr10, not dolby vision.
when I play the dolby vision ts files on LG's website (https://4kmedia.org/lg-amaze-dolby-vision-uhd-4k-demo/) they come up as dolby vision
when I play the dolby vision ts files on LG's website (https://4kmedia.org/lg-amaze-dolby-vision-uhd-4k-demo/) they come up as dolby vision
-
- Posts: 4075
- Joined: Wed Nov 26, 2008 2:26 am
- Contact:
Re: Dolby Vision now possible through MP4 Mux.
Ok, I'm reading the Dolby "profiles and levels" spec:yusesope wrote: ↑Wed Mar 11, 2020 3:33 pmI believe that it is not possible to discard anything.
Regardless of the type of EL (fEL or mEL), in the case of a dvhe.04 or dvhe.07 profile, the Dolby Vision Composer accepts synchronized decoded BL and EL video frames and metadata information and uses metadata to reconstruct 12bit Dolby Vision video.
Code: Select all
2.1.1 Notes to profiles
For profile 4:
A new Dolby Vision certified device is able to decode a profile 4 MEL bitstream without instantiating a secondary HEVC decoder for the enhancement layer.
For profile 7:
The MEL can be used for profile 7 to minimize the processing requirements for the enhancement layer and therefore ensure broader use among UltraHD Blu-ray SoCs.
6.2 Annex II: Differentiating MEL and non-MEL bitstreams
Pictures contained in a Dolby Vision bitstream can be encoded as either MEL or non-MEL, not both.
If a Dolby Vision playback device supports Dolby Vision profile 4 and chooses not to instantiate a second HEVC decoder, then it must check for these values in the
reference processing unit of a Dolby Vision bitstream.
If a Dolby Vision playback device supports Dolby Vision profile 7, it can check for these values in the reference processing unit of a Dolby Vision bitstream.
Profile 4 - the doc explicitly states that the whole secondary decoder may be not instantiated at all (EL data discarded).
Profile 7 - the vague note that knowing about MEL can "minimize the processing requirements for the enhancement layer". I assume the same - no need to instantiate a second HEVC decoder, just generate same gray pictures as in profile 4.
And the fact that "dvdfab method" (BL+MEL RPU only, EL discarded) works, kind of proves that. Am I wrong?
Of course, EL is always 12 bit on blu-ray. The question is what exactly is in these 2 extra bits. My hypothesis - in MEL stream all pictures in EL are filled with the same value (zeroes). This is easy to verify though - one just has to decode entire EL from any MEL disc (Joker) and confirm that ALL frames in EL are indeed dark zero pictures. From the sizes of slice NALU it looks that way.