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 pmI 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.
Dolby Vision now possible through MP4 Mux.
Re: Dolby Vision now possible through MP4 Mux.
-
- 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:
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
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 amAs 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.
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.
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.
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 amAs 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.
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.
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 pmFor 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
Re: Dolby Vision now possible through MP4 Mux.
Thanks @shawnc22 . Or you can try this W64 build bb51a5f from my fork. Single tracks created from Blu-rays should be profile 6.
Code: Select all
// cf. "http://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-profiles-levels.pdf"
int profile;
if (m_sps->bit_depth_luma_minus8 == 2)
{
if (!isDVBL) // dual HEVC track
profile = 7;
else if (m_hdr->isDVEL && (V3_flags & HDR10))
profile = 6;
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;
}
else // 8-bit
{
if (m_sps->colour_primaries == 2 && m_sps->transfer_characteristics == 2 &&
m_sps->matrix_coeffs == 2) // DV IPT color space
profile = 3;
else
profile = 2;
}
Last edited by jcdr428 on Mon Mar 30, 2020 4:33 pm, edited 2 times in total.
-
- Posts: 104
- Joined: Wed Nov 06, 2019 11:26 pm
Re: Dolby Vision now possible through MP4 Mux.
Curious if this will play on the shield, I think not because the devs said profile 4 MEL, 5,8 and 9 are only supported.jcdr428 wrote: ↑Mon Mar 30, 2020 4:22 pmThanks @shawnc22 . Or you can try this W64 build bb51a5f from my fork. Single tracks created from Blu-rays should be profile 6.
Code: Select all
// cf. "http://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-profiles-levels.pdf" int profile; if (m_sps->bit_depth_luma_minus8 == 2) { if (!isDVBL) // dual HEVC track profile = 7; else if (m_hdr->isDVEL && (V3_flags & HDR10)) profile = 6; 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; } else // 8-bit { if (m_sps->colour_primaries == 2 && m_sps->transfer_characteristics == 2 && m_sps->matrix_coeffs == 2) // DV IPT color space profile = 3; else profile = 2; }
We support profile 4 MEL (minimum enhancement layer). Also single layer profiles 5,8.9.
-
- Posts: 311
- Joined: Tue Oct 30, 2018 4:17 pm
Re: Dolby Vision now possible through MP4 Mux.
Anybody??
A way to remove HDR10+ without removing Dolby Vision?
Cheers.
A way to remove HDR10+ without removing Dolby Vision?
Cheers.
-
- Posts: 104
- Joined: Wed Nov 06, 2019 11:26 pm
Re: Dolby Vision now possible through MP4 Mux.
No way that I am aware ofDaMacFunkin wrote: ↑Mon Mar 30, 2020 4:40 pmAnybody??
A way to remove HDR10+ without removing Dolby Vision?
Cheers.
Re: Dolby Vision now possible through MP4 Mux.
Does that mean that profile 4 isn't the best choice for Shield because it doesn't have FEL? And we should use profile 5 if possible? Sorry if I'm misunderstanding, still trying to get this all figured outAngryunibrow wrote: ↑Mon Mar 30, 2020 4:26 pmCurious if this will play on the shield, I think not because the devs said profile 4 MEL, 5,8 and 9 are only supported.jcdr428 wrote: ↑Mon Mar 30, 2020 4:22 pmThanks @shawnc22 . Or you can try this W64 build bb51a5f from my fork. Single tracks created from Blu-rays should be profile 6.
Code: Select all
// cf. "http://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-profiles-levels.pdf" int profile; if (m_sps->bit_depth_luma_minus8 == 2) { if (!isDVBL) // dual HEVC track profile = 7; else if (m_hdr->isDVEL && (V3_flags & HDR10)) profile = 6; 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; } else // 8-bit { if (m_sps->colour_primaries == 2 && m_sps->transfer_characteristics == 2 && m_sps->matrix_coeffs == 2) // DV IPT color space profile = 3; else profile = 2; }
We support profile 4 MEL (minimum enhancement layer). Also single layer profiles 5,8.9.
Re: Dolby Vision now possible through MP4 Mux.
Thank you guys for all the answers.. so I need to set mode 2 to get profile 5, got it
@shawnc22 No the internal player of my C8 does not support TrueHD/Atmos.
But I'm storing it for preservation reasons.
For playback I must select the AC3 core track or E-AC3 5.1.
What I meant to say is that.. before I was able to produce .ts files with -mode 1 hevc that would play fluent on my C8.
Even the 60fps Gemini Man was OK.
Just using the 0.0.3 tool to create a mode 1 hevc file from the BL/EL and then use TsMuxer to mux it into a transport stream.
See my success story: https://www.makemkv.com/forum/viewtopic ... 295#p86295
It would say:
Dolby Vision, Version 1.0, dvhe.08.09, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible
The latest TsMuxer will say:
Dolby Vision, Version 1.0, dvhe.04.09, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible
So it seems 04 will cause stutters every 1 or 2 seconds while 08 works fine?
Or it's caused by the difference between yusesope's 0.0.3 and 0.0.3_rev1 tool.
@shawnc22 No the internal player of my C8 does not support TrueHD/Atmos.
But I'm storing it for preservation reasons.
For playback I must select the AC3 core track or E-AC3 5.1.
What I meant to say is that.. before I was able to produce .ts files with -mode 1 hevc that would play fluent on my C8.
Even the 60fps Gemini Man was OK.
Just using the 0.0.3 tool to create a mode 1 hevc file from the BL/EL and then use TsMuxer to mux it into a transport stream.
See my success story: https://www.makemkv.com/forum/viewtopic ... 295#p86295
It would say:
Dolby Vision, Version 1.0, dvhe.08.09, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible
The latest TsMuxer will say:
Dolby Vision, Version 1.0, dvhe.04.09, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible
So it seems 04 will cause stutters every 1 or 2 seconds while 08 works fine?
Or it's caused by the difference between yusesope's 0.0.3 and 0.0.3_rev1 tool.
Re: Dolby Vision now possible through MP4 Mux.
Just tested the following using yusecope's tool v0.0.3 and tsmuxer build edited to force all profiles to 6 (sorry @jcdr, saw your build too late, but resulting file should be same in this scenario):
Joker sample file that's been used extensively here before with no audio track:
- Plays on B9 internal player, triggers DV
- Plays on 2019 Shield, triggers DV
Full Joker movie remuxed with Atmos audio:
- Plays on B9 internal player (no stutter), triggers DV, and no audio support message (as expected)
- Plays on 2019 Shield, triggers DV and Atmos audio
Here is the resulting mediainfo from the full movie remux:
Interesting findings as my previous remux of the full joker movie that was prof 4 did stutter on my B9, so seemingly the stutter issue on the LG internal player is related to DV profiling. Also interesting that the Shield is able to play these since it's been mentioned in that past that profile 6 is not supported. As far as my eyes can tell, there is no discerning difference between the profile 6 vs 4 DV remuxes. Not sure what the best step is moving forward, since profile 6 has pretty much been deprecated? I had to go back to a 2016 version of the dolby profiles pdf to even find a mention of it.
Joker sample file that's been used extensively here before with no audio track:
- Plays on B9 internal player, triggers DV
- Plays on 2019 Shield, triggers DV
Full Joker movie remuxed with Atmos audio:
- Plays on B9 internal player (no stutter), triggers DV, and no audio support message (as expected)
- Plays on 2019 Shield, triggers DV and Atmos audio
Here is the resulting mediainfo from the full movie remux:
Code: Select all
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.06.06, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 2 h 1 min
Bit rate : 53.7 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.270
Stream size : 45.7 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.0050 cd/m2, max: 4000 cd/m2
Maximum Content Light Level : 992 cd/m2
Maximum Frame-Average Light Level : 120 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 1 min
Bit rate mode : Variable
Bit rate : 640 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 : 558 MiB (1%)
Language : English
Service kind : Complete Main
Number of dynamic objects : 15
Bed channel count : 1 channel
Bed channel configuration : LFE
Re: Dolby Vision now possible through MP4 Mux.
yeah, so profile 4 stutters on LGshawnc22 wrote: ↑Mon Mar 30, 2020 5:13 pmJust tested the following using yusecope's tool v0.0.3 and tsmuxer build edited to force all profiles to 6 (sorry @jcdr, saw your build too late, but resulting file should be same in this scenario):
Joker sample file that's been used extensively here before with no audio track:
- Plays on B9 internal player, triggers DV
- Plays on 2019 Shield, triggers DV
Full Joker movie remuxed with Atmos audio:
- Plays on B9 internal player (no stutter), triggers DV, and no audio support message (as expected)
- Plays on 2019 Shield, triggers DV and Atmos audio
Here is the resulting mediainfo from the full movie remux:
Interesting findings as my previous remux of the full joker movie that was prof 4 did stutter on my B9, so seemingly the stutter issue on the LG internal player is related to DV profiling. Also interesting that the Shield is able to play these since it's been mentioned in that past that profile 6 is not supported. As far as my eyes can tell, there is no discerning difference between the profile 6 vs 4 DV remuxes. Not sure what the best step is moving forward, since profile 6 has pretty much been deprecated? I had to go back to a 2016 version of the dolby profiles pdf to even find a mention of it.Code: Select all
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.06.06, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible Codec ID : 36 Duration : 2 h 1 min Bit rate : 53.7 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.270 Stream size : 45.7 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.0050 cd/m2, max: 4000 cd/m2 Maximum Content Light Level : 992 cd/m2 Maximum Frame-Average Light Level : 120 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 1 min Bit rate mode : Variable Bit rate : 640 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 : 558 MiB (1%) Language : English Service kind : Complete Main Number of dynamic objects : 15 Bed channel count : 1 channel Bed channel configuration : LFE
Now if profile 6 works on both the Shield (also playing the Atmos track) and LG.. then -mode 1 with profile 6 in TS should be the golden combination.