I think the Shield is good with reading single track+dual layer dv profile 4, and single track+single layer profile 5 and 8 videos. Dual track+dual layer profile 7 videos have always been the problem, hence yusecope's tool to merge the tracks but keep the layers still separate (or the -mode 2 option to also merge the layers). The issue somebody was having was with an Apple TV 4k not reading a ST+SL file in prof 8, but when the same video track is remuxed in 5, it'd work perfectly. Probably an issue with the Apple TV not supporting prof 8jcdr428 wrote: Sun Mar 29, 2020 9:31 pm I understand that the Shield reads only DV marked as profile 5. However Blu-ray profile 7 dual tracks changed to single tracks should be profile 8 and not profile 5, as the BL is BT.2100 and not Dolby IPT colorspace. The Shield SoC seems to be able to read any DV as long as it is marked profile 5, so this is something that should be addressed by NVidia in a firmware rather than allowing to disseminate non-compliant DV files.
Dolby Vision now possible through MP4 Mux.
-
shawnc22
- Posts: 637
- Joined: Tue Jan 21, 2020 7:40 am
Re: Dolby Vision now possible through MP4 Mux.
-
Angryunibrow
- Posts: 104
- Joined: Wed Nov 06, 2019 11:26 pm
Re: Dolby Vision now possible through MP4 Mux.
Do you know what the last version was before the change that you think might work, I'm looking for an easier way to do profile 7. mp4muxer takes to longjcdr428 wrote: Sun Mar 29, 2020 9:31 pmThe version that says "PayPal" in the corner is 2.6.12 / proprietary. The versions on github are opensource, under active development with UHD/HDR/DV.Angryunibrow wrote: Sun Mar 29, 2020 3:59 pmThank you for the link, and maybe I miss spoke but I thought there were 2 versions of tsmuxer and the GitHub "version" was the one we needed over the version that says"PayPal" in the corner.
Are they the same now?Maybe the TV does not read HDMV descriptors, as opposed to the BD players. As stated previously, I had pushed the standard HEVC video descriptors for DV, but was asked to come back to HDMV descriptors due to PGS, ac3+thd and ac3+eac3 BD tracks not working anymore.Angryunibrow wrote: Sun Mar 29, 2020 6:08 pm It appears, unless i'm doing something wrong the LG Plex app can't play back a Dolby Vision .ts file created.
I made a Profile 7 just using the 640kb core audio so I know it would direct play but the TV does not trigger Dolby Vision, just HDR
Only thing I noticed was tsmuxer makes it Profile 7.05, while mp4muxer makes it 7.06
Not sure if that is the reason, or its just the the TV needs an .mp4 file instead of .ts - but the file did play just only in HDR
I understand that the Shield reads only DV marked as profile 5. However Blu-ray profile 7 dual tracks changed to single tracks should be profile 8 and not profile 5, as the BL is BT.2100 and not Dolby IPT colorspace. The Shield SoC seems to be able to read any DV as long as it is marked profile 5, so this is something that should be addressed by NVidia in a firmware rather than allowing to disseminate non-compliant DV files.
-
mulucy
- Posts: 145
- Joined: Tue Jan 07, 2020 7:08 pm
Re: Dolby Vision now possible through MP4 Mux.
Apple TV 4K only supports Profile 5. Apparently, the all-new Shield TV supports Profile 4 and 5. And with Profile 4, you get both: single track dual layer and single track single layer and all with lossless audio and ATMOS/DTS-X.shawnc22 wrote: Sun Mar 29, 2020 10:14 pmI think the Shield is good with reading single track+dual layer dv profile 4, and single track+single layer profile 5 and 8 videos. Dual track+dual layer profile 7 videos have always been the problem, hence yusecope's tool to merge the tracks but keep the layers still separate (or the -mode 2 option to also merge the layers). The issue somebody was having was with an Apple TV 4k not reading a ST+SL file in prof 8, but when the same video track is remuxed in 5, it'd work perfectly. Probably an issue with the Apple TV not supporting prof 8jcdr428 wrote: Sun Mar 29, 2020 9:31 pm I understand that the Shield reads only DV marked as profile 5. However Blu-ray profile 7 dual tracks changed to single tracks should be profile 8 and not profile 5, as the BL is BT.2100 and not Dolby IPT colorspace. The Shield SoC seems to be able to read any DV as long as it is marked profile 5, so this is something that should be addressed by NVidia in a firmware rather than allowing to disseminate non-compliant DV files.
-
Grencola
- Posts: 343
- Joined: Sun Jan 27, 2019 5:19 pm
Re: Dolby Vision now possible through MP4 Mux.
Just gotta lower the Red and Green sliders in your TV's color settings and you're all setmulucy wrote: Mon Mar 30, 2020 1:19 am Apparently, the all-new Shield TV supports Profile 4 and 5. And with Profile 4, you get both: single track dual layer and single track single layer and all with lossless audio and ATMOS/DTS-X.
-
jcdr428
- Posts: 34
- Joined: Fri Mar 20, 2020 6:55 pm
Re: Dolby Vision now possible through MP4 Mux.
To clarify the profiles:mulucy wrote: Mon Mar 30, 2020 1:19 amApple TV 4K only supports Profile 5. Apparently, the all-new Shield TV supports Profile 4 and 5. And with Profile 4, you get both: single track dual layer and single track single layer and all with lossless audio and ATMOS/DTS-X.
Profile 4 is SDR BL with DV IPT EL -therefore backward compatible with SDR, not HDR10.
Profile 5 is DV IPT colorspace BL, not backward compatible with SDR or HDR10, i.e. will not give correct colors on a non-DV TV.
Profile 7 is dual track HDR10 BL with DV IPT colorspace EL, backward compatible with HDR10.
Profile 8 is SDR or HDR BL with DV metadata, backward compatible with SDR or HDR.
Levels are only about bitrate and HEVC profile.
-
MastaG
- Posts: 98
- Joined: Thu Aug 08, 2019 11:40 am
Re: Dolby Vision now possible through MP4 Mux.
Just gave the 1917 movie a shot.jcdr428 wrote: Mon Mar 30, 2020 6:22 amTo clarify the profiles:mulucy wrote: Mon Mar 30, 2020 1:19 amApple TV 4K only supports Profile 5. Apparently, the all-new Shield TV supports Profile 4 and 5. And with Profile 4, you get both: single track dual layer and single track single layer and all with lossless audio and ATMOS/DTS-X.
Profile 4 is SDR BL with DV IPT EL -therefore backward compatible with SDR, not HDR10.
Profile 5 is DV IPT colorspace BL, not backward compatible with SDR or HDR10, i.e. will not give correct colors on a non-DV TV.
Profile 7 is dual track HDR10 BL with DV IPT colorspace EL, backward compatible with HDR10.
Profile 8 is SDR or HDR BL with DV metadata, backward compatible with SDR or HDR.
Levels are only about bitrate and HEVC profile.
First using yusesope's v0.0.3 rev 1 tool:
Code: Select all
python src/bl_el_rpu_builder_v0.0.3_rev_1.py -bl ./BL.hevc -el ./EL.hevc -of 1917.hevc
BL_ANALYSIS: 100.0% EL_ANALYSIS: 100.0% BL_EL_RPU WRITING: 100.0% (BL AUDs: 171176 EL AUDs: 171176)
ELAPSED TIME: 09m 08s
Press a button to exitFor the record, I didn't use mp4muxer in the process...
Here's the output file:
Code: Select all
mediainfo 1917.ts
General
ID : 1 (0x1)
Complete name : 1917.ts
Format : MPEG-TS
File size : 70.3 GiB
Duration : 1 h 58 min
Overall bit rate mode : Variable
Overall bit rate : 84.6 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.04.06, BL+EL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : 36
Duration : 1 h 58 min
Bit rate : 79.9 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.402
Stream size : 66.4 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
Stream size : 381 MiB (1%)
Language : English
Service kind : Complete Main
Number of dynamic objects : 11
Bed channel count : 1 channel
Bed channel configuration : LFEShouldn't it report profile 05 instead?
Because your PR has been merged: https://github.com/justdan96/tsMuxer/pull/264 and I built the latest rev, which should include your fix.
-
badrobot
- Posts: 21
- Joined: Wed Mar 25, 2020 4:14 am
Re: Dolby Vision now possible through MP4 Mux.
When you use yusesope's v0.0.3 rev 1 tool, you MUST add a parameter -mode 2,then you will get a DoVi Profile 5 hevc video, without this parameter, the default mode produces a DoVi Profile 4 hevc video.MastaG wrote: Mon Mar 30, 2020 10:27 amJust gave the 1917 movie a shot.jcdr428 wrote: Mon Mar 30, 2020 6:22 amTo clarify the profiles:mulucy wrote: Mon Mar 30, 2020 1:19 amApple TV 4K only supports Profile 5. Apparently, the all-new Shield TV supports Profile 4 and 5. And with Profile 4, you get both: single track dual layer and single track single layer and all with lossless audio and ATMOS/DTS-X.
Profile 4 is SDR BL with DV IPT EL -therefore backward compatible with SDR, not HDR10.
Profile 5 is DV IPT colorspace BL, not backward compatible with SDR or HDR10, i.e. will not give correct colors on a non-DV TV.
Profile 7 is dual track HDR10 BL with DV IPT colorspace EL, backward compatible with HDR10.
Profile 8 is SDR or HDR BL with DV metadata, backward compatible with SDR or HDR.
Levels are only about bitrate and HEVC profile.
First using yusesope's v0.0.3 rev 1 tool:And afterwards I remuxed the 1917.hevc along with the TrueHD+ac3 core track from the bluray disc into a .ts file with the latest TsMuxer (built from source).Code: Select all
python src/bl_el_rpu_builder_v0.0.3_rev_1.py -bl ./BL.hevc -el ./EL.hevc -of 1917.hevc BL_ANALYSIS: 100.0% EL_ANALYSIS: 100.0% BL_EL_RPU WRITING: 100.0% (BL AUDs: 171176 EL AUDs: 171176) ELAPSED TIME: 09m 08s Press a button to exit
For the record, I didn't use mp4muxer in the process...
Here's the output file:As you can see it reports: 04.06.Code: Select all
mediainfo 1917.ts General ID : 1 (0x1) Complete name : 1917.ts Format : MPEG-TS File size : 70.3 GiB Duration : 1 h 58 min Overall bit rate mode : Variable Overall bit rate : 84.6 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.04.06, BL+EL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible Codec ID : 36 Duration : 1 h 58 min Bit rate : 79.9 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.402 Stream size : 66.4 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 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
Shouldn't it report profile 05 instead?
Because your PR has been merged: https://github.com/justdan96/tsMuxer/pull/264 and I built the latest rev, which should include your fix.
I am not a native English speaker.
Sorry for my bad English.
Sorry for my bad English.
-
MastaG
- Posts: 98
- Joined: Thu Aug 08, 2019 11:40 am
Re: Dolby Vision now possible through MP4 Mux.
Well now both 1917 and Gemini Man will stutter every one or two seconds..MastaG wrote: Mon Mar 30, 2020 10:27 amJust gave the 1917 movie a shot.jcdr428 wrote: Mon Mar 30, 2020 6:22 amTo clarify the profiles:mulucy wrote: Mon Mar 30, 2020 1:19 amApple TV 4K only supports Profile 5. Apparently, the all-new Shield TV supports Profile 4 and 5. And with Profile 4, you get both: single track dual layer and single track single layer and all with lossless audio and ATMOS/DTS-X.
Profile 4 is SDR BL with DV IPT EL -therefore backward compatible with SDR, not HDR10.
Profile 5 is DV IPT colorspace BL, not backward compatible with SDR or HDR10, i.e. will not give correct colors on a non-DV TV.
Profile 7 is dual track HDR10 BL with DV IPT colorspace EL, backward compatible with HDR10.
Profile 8 is SDR or HDR BL with DV metadata, backward compatible with SDR or HDR.
Levels are only about bitrate and HEVC profile.
First using yusesope's v0.0.3 rev 1 tool:And afterwards I remuxed the 1917.hevc along with the TrueHD+ac3 core track from the bluray disc into a .ts file with the latest TsMuxer (built from source).Code: Select all
python src/bl_el_rpu_builder_v0.0.3_rev_1.py -bl ./BL.hevc -el ./EL.hevc -of 1917.hevc BL_ANALYSIS: 100.0% EL_ANALYSIS: 100.0% BL_EL_RPU WRITING: 100.0% (BL AUDs: 171176 EL AUDs: 171176) ELAPSED TIME: 09m 08s Press a button to exit
For the record, I didn't use mp4muxer in the process...
Here's the output file:As you can see it reports: 04.06.Code: Select all
mediainfo 1917.ts General ID : 1 (0x1) Complete name : 1917.ts Format : MPEG-TS File size : 70.3 GiB Duration : 1 h 58 min Overall bit rate mode : Variable Overall bit rate : 84.6 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.04.06, BL+EL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible Codec ID : 36 Duration : 1 h 58 min Bit rate : 79.9 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.402 Stream size : 66.4 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 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
Shouldn't it report profile 05 instead?
Because your PR has been merged: https://github.com/justdan96/tsMuxer/pull/264 and I built the latest rev, which should include your fix.
This is on my LG C8 btw.
So either the change from yusecope's 0.0.3 to 0.0.3 rev1 caused this. (Was using mode 1 for both versions)
Or the updated tsmuxer could be the cause.
Since the previous revision was showing profile 8..
Either one of two is upsetting my TV.
-
1000010
- Posts: 19
- Joined: Sun Nov 03, 2019 12:18 pm
Re: Dolby Vision now possible through MP4 Mux.
could you explain what you did? I'm really interested in figuring out why some movies don't work on the Shield.yusesope wrote: Tue Mar 24, 2020 12:17 pm I am therefore trying to modify at bit level the .ts files produced by FFmpeg.
I did some experiments using THIS file and HERE you can find the results.
If your device plays the original file, test the files I edited.
If there is a positive response (I have my doubts but there is no harm in trying!), I will explain what and how I did it.
-
Mortenjorstad
- Posts: 19
- Joined: Wed Mar 18, 2020 9:43 am
Re: Dolby Vision now possible through MP4 Mux.
You have to edit the the youscope toolMastaG wrote: Mon Mar 30, 2020 10:27 amJust gave the 1917 movie a shot.jcdr428 wrote: Mon Mar 30, 2020 6:22 amTo clarify the profiles:mulucy wrote: Mon Mar 30, 2020 1:19 amApple TV 4K only supports Profile 5. Apparently, the all-new Shield TV supports Profile 4 and 5. And with Profile 4, you get both: single track dual layer and single track single layer and all with lossless audio and ATMOS/DTS-X.
Profile 4 is SDR BL with DV IPT EL -therefore backward compatible with SDR, not HDR10.
Profile 5 is DV IPT colorspace BL, not backward compatible with SDR or HDR10, i.e. will not give correct colors on a non-DV TV.
Profile 7 is dual track HDR10 BL with DV IPT colorspace EL, backward compatible with HDR10.
Profile 8 is SDR or HDR BL with DV metadata, backward compatible with SDR or HDR.
Levels are only about bitrate and HEVC profile.
First using yusesope's v0.0.3 rev 1 tool:And afterwards I remuxed the 1917.hevc along with the TrueHD+ac3 core track from the bluray disc into a .ts file with the latest TsMuxer (built from source).Code: Select all
python src/bl_el_rpu_builder_v0.0.3_rev_1.py -bl ./BL.hevc -el ./EL.hevc -of 1917.hevc BL_ANALYSIS: 100.0% EL_ANALYSIS: 100.0% BL_EL_RPU WRITING: 100.0% (BL AUDs: 171176 EL AUDs: 171176) ELAPSED TIME: 09m 08s Press a button to exit
For the record, I didn't use mp4muxer in the process...
Here's the output file:As you can see it reports: 04.06.Code: Select all
mediainfo 1917.ts General ID : 1 (0x1) Complete name : 1917.ts Format : MPEG-TS File size : 70.3 GiB Duration : 1 h 58 min Overall bit rate mode : Variable Overall bit rate : 84.6 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.04.06, BL+EL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible Codec ID : 36 Duration : 1 h 58 min Bit rate : 79.9 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.402 Stream size : 66.4 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 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
Shouldn't it report profile 05 instead?
Because your PR has been merged: https://github.com/justdan96/tsMuxer/pull/264 and I built the latest rev, which should include your fix.
open up the .bat file in notepad and add -mode 2 to the end of the single line of text in there and save it.
python-3.7.6.amd64\python src\bl_el_rpu_builder_v0.0.3.py -mode 2
If you do that you will have a dolby vision 05.06 file
-
jcdr428
- Posts: 34
- Joined: Fri Mar 20, 2020 6:55 pm
Re: Dolby Vision now possible through MP4 Mux.
So your have hacked the Blu-ray dual tracks to move the second track to an EL layer in the first track. The resulting single track is BL+EL (which should be profile 4) with HDR10 (which should be profile 8 ), but is definitely not profile 5 (which is DV IPT without EL). You should ask Dolby to create a new profileMastaG wrote: Mon Mar 30, 2020 10:27 am As you can see it reports: 04.06.
Shouldn't it report profile 05 instead?
Because your PR has been merged: https://github.com/justdan96/tsMuxer/pull/264 and I built the latest rev, which should include your fix.
Edit: I don't really know how I should classify the profiles for your hacked files, but I've pushed the following to tsMuxer:
Code: Select all
// cf. "DolbyVisionProfilesLevels_v1_3_2_2019_09_16.pdf"
int profile = 0;
if (!isDVBL) // dual HEVC track
profile = 7;
else if (m_hdr->isDVEL)
profile = 4;
else if (m_sps->colour_primaries == 2 && m_sps->transfer_characteristics == 2 &&
m_sps->matrix_coeffs == 2) // DV IPT color space
profile = 5;
else
profile = 8;
Last edited by jcdr428 on Mon Mar 30, 2020 2:47 pm, edited 3 times in total.
-
pargo
- Posts: 3
- Joined: Sun Mar 29, 2020 2:22 pm
Re: Dolby Vision now possible through MP4 Mux.
Bumping this because my edit got buried - any ideas why mp4muxer isn't working for me?pargo wrote: Sun Mar 29, 2020 9:47 pmEdit I found the 64bit version of mp4muxer and my TV still doesn't activate DV when I play the output file, only HDR.planet_hoarder wrote: Wed Mar 18, 2020 8:40 amAlso would be my question, since Dolby's mp4muxer works perfectly (well at least mp4muxer_64bit.exe works) with extracted bl, el tracks from mkv-files. Watched couple of DV movies on LG Oled that way.Arbigator wrote: Wed Mar 18, 2020 6:53 am What is it about a demuxed mkv rip that this tool doesn't like? Do you think it might be possible in the future?
I have Shield 2019, using nightly tsmuxer to demux Annihilation bluray remux MKV, and repackage the BL and EL with the AC3 layer using mp4muxer 64 bit. But the Shield playing via plex always shows HDR. Any ideas what I'm missing? Would really appreciate it.
I've now tried with Annihilation and Aquaman remuxes. Could it be because I'm starting with the remuxed MKV? But I know other people on this forum have said they were able to rip BL/EL from a remux MKV with no problems (as long as they were using mp4muxer and not yuseopoe tool).
Thanks everyone for your work on this project. I've read through pretty much everything and its been extremely helpful.
-
MastaG
- Posts: 98
- Joined: Thu Aug 08, 2019 11:40 am
Re: Dolby Vision now possible through MP4 Mux.
For the record I didn't change/alter anything.jcdr428 wrote: Mon Mar 30, 2020 2:18 pmSo your have hacked the Blu-ray dual tracks to move the second track to an EL layer in the first track. The resulting single track is BL+EL (which should be profile 4) with HDR10 (which should be profile 8 ), but is definitely not profile 5 (which is DV IPT without EL). You should ask Dolby to create a new profileMastaG wrote: Mon Mar 30, 2020 10:27 am As you can see it reports: 04.06.
Shouldn't it report profile 05 instead?
Because your PR has been merged: https://github.com/justdan96/tsMuxer/pull/264 and I built the latest rev, which should include your fix.
Edit: I don't really know how I should classify the profiles for your hacked files, but I've pushed the following to tsMuxer:Code: Select all
// cf. "DolbyVisionProfilesLevels_v1_3_2_2019_09_16.pdf" int profile = 0; if (!isDVBL) // dual HEVC track profile = 7; else if (m_hdr->isDVEL) profile = 4; else if (m_sps->colour_primaries == 2 && m_sps->transfer_characteristics == 2 && m_sps->matrix_coeffs == 2) // DV IPT color space profile = 5; else profile = 8;
I just updated yusecope's tool from 0.0.3 to 0.0.3 rev1 and updated tsmuxer to the latest git revision.
No changes/patches.. I'm remuxing the EL/BL straight from the Blu-ray disc, convert them with yusecope's python tool and then use tsmuxer to create a .ts file from the output of it.
So I'm not using mp4muxer.
Now previously this used to work on my LG C8.
Now it doesn't work any longer and just skips.
So either the upgrade of yusecope's tool or tsmuxer caused it.
So I assumed the profile was wrong in the resulted .ts file, since perhaps it requires 5 instead of 4, but I'm not sure.
It can also be rev1 of yusecope's tool producing different conversion causing the stutters.
-
jcdr428
- Posts: 34
- Joined: Fri Mar 20, 2020 6:55 pm
Re: Dolby Vision now possible through MP4 Mux.
@yusesope and others, any means to check whether your Blu-rays changed to BL+EL+RPU HDR10 single tracks work on TV, STB and/or OTT if we assign correct profile 6 to these ?
Edit: so profile 8 will get deprecated as well, it looks like Dolby are pushing for proprietary DV streams that cannot be read by non-DV TVs or STBs, to force people to buy Dolby equipment.
Edit: so profile 8 will get deprecated as well, it looks like Dolby are pushing for proprietary DV streams that cannot be read by non-DV TVs or STBs, to force people to buy Dolby equipment.
-
shawnc22
- Posts: 637
- Joined: Tue Jan 21, 2020 7:40 am
Re: Dolby Vision now possible through MP4 Mux.
As far as I know, rev1 of yusecope's tool merely added the AUD count debugging messages over the base version and didn't change how the resulting the HEVC file is constructed. If you're not using -mode 2 of the tool, the resulting file should be profile 4 (or 6 i guess according to the blu-ray forums), but definitely not 5 or 8 since the EL layer is not supported in these profiles.MastaG wrote: Mon Mar 30, 2020 2:35 pm For the record I didn't change/alter anything.
I just updated yusecope's tool from 0.0.3 to 0.0.3 rev1 and updated tsmuxer to the latest git revision.
No changes/patches.. I'm remuxing the EL/BL straight from the Blu-ray disc, convert them with yusecope's python tool and then use tsmuxer to create a .ts file from the output of it.
So I'm not using mp4muxer.
Now previously this used to work on my LG C8.
Now it doesn't work any longer and just skips.
So either the upgrade of yusecope's tool or tsmuxer caused it.
So I assumed the profile was wrong in the resulted .ts file, since perhaps it requires 5 instead of 4, but I'm not sure.
It can also be rev1 of yusecope's tool producing different conversion causing the stutters.
Are you saying you had gotten TS remuxes to work on your C8's internal player with atmos audio? I was under the impression that LG's do not support lossless audio at all. At least on my B9, whenever I try to play any of my TS remuxes, I would always get the "This video does not support audio" message on the top right corner while the video is playing. As for the videos skipping, I've had some mixed results. Some of the files I've created with the older version of tsmuxer that produced prof 8 played back perfectly and some had the same skipping issues like you mentioned. Not a big issue for me anyways since they all playback perfectly on the Shield with the included Atmos track, but have you tried redoing a movie that you have known to work on your C8 with the new versions of yusecope's tool and updated tsmuxer to determine if it might be a title-related or tool-related issue?
@jcdr, I can recompile tsmuxer and give prof 6 a try. will report back with results