Dolby Vision now possible through MP4 Mux.

[Deihnyx]

I used the method described in the past threads.

• ffmpeg to decode the BL + EL layer

  Code: Select all

  ffmpeg -i bluray:H:\ -map 0:0 -c copy D:\output\BL.hevc -map 0:1 -c copy D:\output\EL.hevc
  

• yusesope's script to merge the layers (all counters to 100%)

  Code: Select all

  python src\bl_el_rpu_builder.py -bl D:\output\BL.hevc -el D:\output\EL.hevc -of D:\output\Full.hevc
  

• tsmuxer to remux the new hevc + truehd atmos to TS

Everything seems OK to me.

To try to understand where the problem lies, I recommend you:
Download version_0.0.3_revision_1 of my tool and start it with the command:

Code: Select all

python bl_el_rpu_builder_v0.0.3_rev_1.py -bl D:\output\BL.hevc -el D:\output\EL.hevc -of D:\output\New_Full.hevc

It is important that all the counters reach 100%, that the total number of BL AUDs is equal to those of EL Layer and that the program ends with the invitation to "press a button to exit".

If everything was ok, I recommend, before using tsMuxeR, to test only the video with mp4muxer (HERE) by trying both profile 4 and profile 7 (it takes some time).

Code: Select all

mp4muxer -i D:\output\New_Full.hevc --dv-profile 4 -o D:\output\New_Full_dvhe04.mp4

Code: Select all

mp4muxer -i D:\output\New_Full.hevc --dv-profile 7 -o D:\output\New_Full_dvhe07.mp4

If the video is displayed correctly on your devices then add the audio with tsMuxeR (as you did previously).
If that doesn't work, try creating a BL + RPU file by adding the "-mode 2" switch to my script.

Code: Select all

python bl_el_rpu_builder_v0.0.3_rev_1.py -mode 2 -bl D:\output\BL.hevc -el D:\output\EL.hevc -of D:\output\BL_RPU.hevc

Thank you,
Trying your new revision and the patched tsMuxer for profile 4 DV is recognized on my C7 and C9 while using a TS file.
However, it stutters terribly. Maybe these tvs can't handle dual layers natively?

While using the shield, it works (DV detected on the team, Atmos detected on my Denon) but only with Plex, and it crashes at start sometimes. I was never able to get DV to work with Emby on Shield.
The EL file generated by "Us" was almost 10GB, I suppose that's FEL?

Thanks

[Mortenjorstad]

You need
Eac3to 3.34
Tsmuxer
Yusesope tool v.0.0.3

First you have to make bl.hevc and el.hevc

Eac3to path to folder with DV movie 2:bl.hevc 3:el.hevc

Know you have made 2 files bl.hevc and el.hevc

Start yusesope tool and drop first bl.hevc and then el.hevc
This will make a new hevc fIle

Start tsmuxerGui
Add the file you made With yusesope tool
Add Blu-ray movie and just select the soundtrack
Mux the files together in Ts.

You will know have a movie that is DV with Atmos that will play on shield 2019

I followed the exact same steps but the final file only has 1 video stream (hdr10).

You must use this tsmuxer, if you use wrong only hdr10 is copyed

https://mega.nz/#!9m4FDJjT!1276qfyWM_tU ... 5SqsVORvSg

[shawnc22]

Thank you,
Trying your new revision and the patched tsMuxer for profile 4 DV is recognized on my C7 and C9 while using a TS file.
However, it stutters terribly. Maybe these tvs can't handle dual layers natively?

While using the shield, it works (DV detected on the team, Atmos detected on my Denon) but only with Plex, and it crashes at start sometimes. I was never able to get DV to work with Emby on Shield.
The EL file generated by "Us" was almost 10GB, I suppose that's FEL?

Thanks

The TV player cannot play Atmos audio. I'm assuming you're using Plex because the internal player would not play the audio to begin with. The stuttering is probably caused by tv plex player trying to transcode that atmos track into something playable.

[Deihnyx]

Thank you,
Trying your new revision and the patched tsMuxer for profile 4 DV is recognized on my C7 and C9 while using a TS file.
However, it stutters terribly. Maybe these tvs can't handle dual layers natively?

While using the shield, it works (DV detected on the team, Atmos detected on my Denon) but only with Plex, and it crashes at start sometimes. I was never able to get DV to work with Emby on Shield.
The EL file generated by "Us" was almost 10GB, I suppose that's FEL?

Thanks

The TV player cannot play Atmos audio. I'm assuming you're using Plex because the internal player would not play the audio to begin with. The stuttering is probably caused by tv plex player trying to transcode that atmos track into something playable.

I normally use Emby. Both Emby and Plex trigger DV on the TV player. It shows both the ATMOS track and the AC3 "Core" track. Both of them stutter. Transcoding anything in Emby will strip DV anyway, so I'm confident it's not the problem.
My only conclusion is that the C7/C9 needs DV in single layer in order to work. But from what I understand if I do produce single track single layer track I won't be able to play them with devices that can only play regular HDR, correct? Otherwise, what's the drawback in producing single track single layer files?

Emby on shield just doesn't trigger DV for some reason, but I'm guessing that's something I'll need to ask the Emby team.

[shawnc22]

Thank you,
Trying your new revision and the patched tsMuxer for profile 4 DV is recognized on my C7 and C9 while using a TS file.
However, it stutters terribly. Maybe these tvs can't handle dual layers natively?

While using the shield, it works (DV detected on the team, Atmos detected on my Denon) but only with Plex, and it crashes at start sometimes. I was never able to get DV to work with Emby on Shield.
The EL file generated by "Us" was almost 10GB, I suppose that's FEL?

Thanks

The TV player cannot play Atmos audio. I'm assuming you're using Plex because the internal player would not play the audio to begin with. The stuttering is probably caused by tv plex player trying to transcode that atmos track into something playable.

I normally use Emby. Both Emby and Plex trigger DV on the TV player. It shows both the ATMOS track and the AC3 "Core" track. Both of them stutter. Transcoding anything in Emby will strip DV anyway, so I'm confident it's not the problem.
My only conclusion is that the C7/C9 needs DV in single layer in order to work. But from what I understand if I do produce single track single layer track I won't be able to play them with devices that can only play regular HDR, correct? Otherwise, what's the drawback in producing single track single layer files?

Emby on shield just doesn't trigger DV for some reason, but I'm guessing that's something I'll need to ask the Emby team.

No, the problem is that the TV player cannot play Atmos audio, it's been said here many times. The AC3 Core track you're trying to play is not an actual audio track. Here're a couple tests you can do:

1) With the same HEVC video track you've been using from yusecope's tool, use TSMuxer to add in a different audio track from the original m2ts file, or add no audio tracks at all and see if that plays on the TV player without stuttering.
2) Use makemkv to create an mkv with the Atmos track and just the HDR10 layer. Try playing that on the Plex TV player and see if it stutters (it will).
3) Lastly, if you open the TS file that's been stuttering on the barebones internal tv player (by browsing to it through the Photos and Videos app), you'll notice that it plays perfectly in DV while you get a message saying that the Audio track is not supported.

[eblackadder]

Using MXPlayer on the shield i havent got any method to work, ive tried several in this thread (all using yusesope tool), is it supposed to work? If so please teach me, i feel like theres 10 different TSMuxer mentioned and some mentioning mp4muxer instead (which is the correct version btw? i believe there are several different programs when u google mp4muxer)

I don't get it to work as well. When i start a file(made with yusesope's tool 0.3 and the modified TS Muxer) i chose HW decoder. It works and my tv triggers Dolby Vision and my Denon receiver triggers Atmos. Then after awhile i get a message that HW decoder isn't supported. Then it goes to HW+ decoder and it triggers HDR and only Stereo on my receiver.

On Plex it runs pretty well but subs with PGS enabled made the video stop. I can solve that with an external srt file. I also feel that there is sometimes a micro stutter after awhile. Maybe that has something to do with the Shield Tv pro that i'm using? Can someone tell me when i watch a dv movie what the setting of the AI upscaler? Can i turn it off for 4k movies?

[ragico]

I have made several m2ts DV adding also the atmos/dts hd master audio tracks and all play flawlessly in the shield 2019 using Plex app.
Among them Braveheart, Cold Pursuit, The Doors, Earth: One Amazing Day (all FEL). All made using Yusesope tool v.003
There is one remaining problem to be sorted out and this is the pgs subtitles.
Any time in any movie I try to enable the subtitles the movie either stops or does not start.
May be is a Plex problem.

[1000010]

The DTS-MA track could definitely be the issue. One last thing you might want to try is create a TS file with TSMuxer with only the video tracks. If that works, then it's probably the DTS track causing the issue.

edit: oops yusecope beat me to it!

right so I made a couple of additional tests:
* ts with LPCM sound didn't work
* mp4 without sound worked
* ts short clip without sound worked
* ts full movie without sound didn't work

I find the last two points interesting. I think there might be a bug in tsmuxer that messes some things up. I will try tomorrow with m2ts if it perhaps makes a difference (I don't know either format in detail).

Client log with ts full movie without sound:

Code: Select all

03-22 21:59:14.684  e: [ExoPlayer][EventLogger] playerFailed [4.93, 0.00, window=0]
03-22 21:59:14.684  e: An exception occurred: com.google.android.exoplayer2.r: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
03-22 21:59:14.684  i: [FF] Loading canceled (released: true)
03-22 21:59:14.685  e: Stacktrace: com.google.android.exoplayer2.r: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
	at com.google.android.exoplayer2.v.handleMessage(SourceFile:29)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:193)
	at android.os.HandlerThread.run(HandlerThread.java:65)
Caused by: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
	at com.plexapp.plex.ff.FFDemuxer.open(SourceFile:31)
	at com.plexapp.plex.ff.source.FFLoadable.load(SourceFile:3)
	at com.google.android.exoplayer2.y0.a0$d.run(SourceFile:4)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.lang.Thread.run(Thread.java:764)

03-22 21:59:14.685  e: [Player][ExoPlayer] Playback error detected
03-22 21:59:14.685  e: An exception occurred: com.google.android.exoplayer2.r: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
03-22 21:59:14.686  i: [FF] Releasing demuxer.
03-22 21:59:14.686  e: Stacktrace: com.google.android.exoplayer2.r: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
	at com.google.android.exoplayer2.v.handleMessage(SourceFile:29)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:193)
	at android.os.HandlerThread.run(HandlerThread.java:65)
Caused by: [Open]com.plexapp.plex.ff.data.FFException: Demuxer failed to open input.
	at com.plexapp.plex.ff.FFDemuxer.open(SourceFile:31)
	at com.plexapp.plex.ff.source.FFLoadable.load(SourceFile:3)
	at com.google.android.exoplayer2.y0.a0$d.run(SourceFile:4)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.lang.Thread.run(Thread.java:764)

03-22 21:59:14.686  i: [Player][Timeline] Handling player error
03-22 21:59:14.686  i: [Player][Timeline] Playback stopped (error: true)
03-22 21:59:14.686  i: [Player][Timeline] Unable to report progress to server as duration is unavailable.

server log:

Code: Select all

Mar 22, 2020 21:59:23.247 [0x7f5f8911f700] Error — MDE: video has neither a video stream nor an audio stream
Mar 22, 2020 21:59:23.247 [0x7f5f8911f700] Debug — MDE: received PLEX_PROTOCOL_ANY from client, but could not determine best protocol. Defaulting to HTTP
Mar 22, 2020 21:59:23.247 [0x7f5f8911f700] Debug — MDE: analyzing media item 23682
Mar 22, 2020 21:59:23.247 [0x7f5f8911f700] Error — MDE: video has neither a video stream nor an audio stream
Mar 22, 2020 21:59:23.247 [0x7f5f8911f700] Error — Streaming Resource: Cannot make a decision because either the file is unplayable or the client provided bad data
Mar 22, 2020 21:59:23.248 [0x7f5fcb088700] Debug — Completed: [192.168.0.18:34090] 400 GET /video/:/transcode/universal/decision?audioBoost=100&autoAdjustQuality=0&directPlay=0&directStream=1&directStreamAudio=1&fastSeek=1&hasMDE=1&location=lan&maxVideoBitrate=200000&mediaBufferSize=209664&mediaIndex=0&partIndex=0&path=%2Flibrary%2Fmetadata%2F13354&protocol=*&session=2344769d6696a1ac-com-plexapp-android&subtitleSize=100&videoBitrate=200000&videoQuality=100&videoResolution=3840x2160 (14 live) TLS GZIP 590ms 384 bytes (pipelined: 5)

[DaMacFunkin]

You should try and then report your experience here on the forum.

just tried your method with with MEL and FEL on Shield and it works like magic. Hats off to you sir. I can even do it on linux.

It makes me a bit confused though, I thought Shield does not support decoding of FEL, which means it should skip DV pipeline according to the diagram from one of your previous posts. Any idea what might be happening there? Is there any way I can check? going to take a look client logs later, I already deleted all my test files.

I think what I wrote: according to the official documents if the hardware is not able to handle a FEL stream (by instantiating a secondary HEVC decoder), it should fall back on HDR10/SDR.
The hardware of the new Shield is very performing, it is not unlikely that it is also able to manage FEL streams.

The confirmation can only come from you: my tool has been downloaded hundreds of times but few people have posted their feedback.

If it can help you (when you check the client logs), the Shield's hardware decoder is

Code: Select all

OMX.Nvidia.DOVI.decode

If @DaMacFunkin answers my previous question, it would also be interesting if he could compare the output video quality of the OPPO with that of the new Shield

Hi, Following the guide can't get FEL to work on the oppp, the file does work in HDR10 on the 2017 shield, can't check on the 2019 shield as it is at my weekend address (won't be there again till Friday)…

General
ID : 1 (0x1)
Complete name : E:\Video\1917\1917 (2019).m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 71.8 GiB
Duration : 1 h 58 min
Overall bit rate mode : Variable
Overall bit rate : 86.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.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 : 82.5 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.415
Stream size : 68.6 GiB (96%)
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
Delay relative to video : 17 ms
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

[ragico]

Using MXPlayer on the shield i havent got any method to work, ive tried several in this thread (all using yusesope tool), is it supposed to work? If so please teach me, i feel like theres 10 different TSMuxer mentioned and some mentioning mp4muxer instead (which is the correct version btw? i believe there are several different programs when u google mp4muxer)

I don't get it to work as well. When i start a file(made with yusesope's tool 0.3 and the modified TS Muxer) i chose HW decoder. It works and my tv triggers Dolby Vision and my Denon receiver triggers Atmos. Then after awhile i get a message that HW decoder isn't supported. Then it goes to HW+ decoder and it triggers HDR and only Stereo on my receiver.

On Plex it runs pretty well but subs with PGS enabled made the video stop. I can solve that with an external srt file. I also feel that there is sometimes a micro stutter after awhile. Maybe that has something to do with the Shield Tv pro that i'm using? Can someone tell me when i watch a dv movie what the setting of the AI upscaler? Can i turn it off for 4k movies?

I dont think that the A1 upscaler should be used with 4k.
I do not use it even for 2k
As a workaround for subtitles in m2ts I too use srt external for plex.

[eblackadder]

Using MXPlayer on the shield i havent got any method to work, ive tried several in this thread (all using yusesope tool), is it supposed to work? If so please teach me, i feel like theres 10 different TSMuxer mentioned and some mentioning mp4muxer instead (which is the correct version btw? i believe there are several different programs when u google mp4muxer)

I don't get it to work as well. When i start a file(made with yusesope's tool 0.3 and the modified TS Muxer) i chose HW decoder. It works and my tv triggers Dolby Vision and my Denon receiver triggers Atmos. Then after awhile i get a message that HW decoder isn't supported. Then it goes to HW+ decoder and it triggers HDR and only Stereo on my receiver.

On Plex it runs pretty well but subs with PGS enabled made the video stop. I can solve that with an external srt file. I also feel that there is sometimes a micro stutter after awhile. Maybe that has something to do with the Shield Tv pro that i'm using? Can someone tell me when i watch a dv movie what the setting of the AI upscaler? Can i turn it off for 4k movies?

I dont think that the A1 upscaler should be used with 4k.
I do not use it even for 2k
As a workaround for subtitles in m2ts I too use srt external for plex.

How can you turn it off if i may ask? I see 3 options. Basic, Enchanted and AI Enchanted

[ragico]

I don't get it to work as well. When i start a file(made with yusesope's tool 0.3 and the modified TS Muxer) i chose HW decoder. It works and my tv triggers Dolby Vision and my Denon receiver triggers Atmos. Then after awhile i get a message that HW decoder isn't supported. Then it goes to HW+ decoder and it triggers HDR and only Stereo on my receiver.

On Plex it runs pretty well but subs with PGS enabled made the video stop. I can solve that with an external srt file. I also feel that there is sometimes a micro stutter after awhile. Maybe that has something to do with the Shield Tv pro that i'm using? Can someone tell me when i watch a dv movie what the setting of the AI upscaler? Can i turn it off for 4k movies?

I dont think that the A1 upscaler should be used with 4k.
I do not use it even for 2k
As a workaround for subtitles in m2ts I too use srt external for plex.

How can you turn it off if i may ask? I see 3 options. Basic, Enchanted and AI Enchanted

enchanted

[mulucy]

just tried your method with with MEL and FEL on Shield and it works like magic. Hats off to you sir. I can even do it on linux.

It makes me a bit confused though, I thought Shield does not support decoding of FEL, which means it should skip DV pipeline according to the diagram from one of your previous posts. Any idea what might be happening there? Is there any way I can check? going to take a look client logs later, I already deleted all my test files.

I think what I wrote: according to the official documents if the hardware is not able to handle a FEL stream (by instantiating a secondary HEVC decoder), it should fall back on HDR10/SDR.
The hardware of the new Shield is very performing, it is not unlikely that it is also able to manage FEL streams.

The confirmation can only come from you: my tool has been downloaded hundreds of times but few people have posted their feedback.

If it can help you (when you check the client logs), the Shield's hardware decoder is

Code: Select all

OMX.Nvidia.DOVI.decode

If @DaMacFunkin answers my previous question, it would also be interesting if he could compare the output video quality of the OPPO with that of the new Shield

Hi, Following the guide can't get FEL to work on the oppp, the file does work in HDR10 on the 2017 shield, can't check on the 2019 shield as it is at my weekend address (won't be there again till Friday)…

General
ID : 1 (0x1)
Complete name : E:\Video\1917\1917 (2019).m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 71.8 GiB
Duration : 1 h 58 min
Overall bit rate mode : Variable
Overall bit rate : 86.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.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 : 82.5 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.415
Stream size : 68.6 GiB (96%)
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
Delay relative to video : 17 ms
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

According to the Nvidia's tech support ( unable to find the link to that post ), the new Shield TV supports only the latest Dolby Vision Profile 4 with MEL, no support for the FEL. Please, update us as soon as possible. I'd like to hear your feedback, and I am super curious whether the new Shield is going to play it in HDR10 like the 2017 version, or it will be in full Dolby Vision with FEL. With full FEL, with lossless Audio, and with the tools available on this forum (tremendous gratitude for yusecope for his hard work and others on this forum including you ), the new Shield TV can be the ultimate device!

[Angryunibrow]

I think what I wrote: according to the official documents if the hardware is not able to handle a FEL stream (by instantiating a secondary HEVC decoder), it should fall back on HDR10/SDR.
The hardware of the new Shield is very performing, it is not unlikely that it is also able to manage FEL streams.

The confirmation can only come from you: my tool has been downloaded hundreds of times but few people have posted their feedback.

If it can help you (when you check the client logs), the Shield's hardware decoder is

Code: Select all

OMX.Nvidia.DOVI.decode

If @DaMacFunkin answers my previous question, it would also be interesting if he could compare the output video quality of the OPPO with that of the new Shield

Hi, Following the guide can't get FEL to work on the oppp, the file does work in HDR10 on the 2017 shield, can't check on the 2019 shield as it is at my weekend address (won't be there again till Friday)…

General
ID : 1 (0x1)
Complete name : E:\Video\1917\1917 (2019).m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 71.8 GiB
Duration : 1 h 58 min
Overall bit rate mode : Variable
Overall bit rate : 86.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.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 : 82.5 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.415
Stream size : 68.6 GiB (96%)
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
Delay relative to video : 17 ms
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

According to the Nvidia's tech support ( unable to find the link to that post ), the new Shield TV supports only the latest Dolby Vision Profile 4 with MEL, no support for the FEL. Please, update us as soon as possible. I'd like to hear your feedback, and I am super curious whether the new Shield is going to play it in HDR10 like the 2017 version, or it will be in full Dolby Vision with FEL. With full FEL, with lossless Audio, and with the tools available on this forum (tremendous gratitude for yusecope for his hard work and others on this forum including you ), the new Shield TV can be the ultimate device!

I have already made plenty of DV movies using these tool with Atmos audio, few pages back talking about it.

I'm one of the ones who spoke to Nvidia about what the shield can output and they confirmed profile 4 MEL.

The only thing I can't confirm is what the shield is actually outputting when a FEL file is played.

What I do know is Doctor Strange which is a MEL movie definitely has color issues, but again I'm lead to believe this is a shield issue as per previous tests located a bunch of pages back.

[mulucy]

Hi, Following the guide can't get FEL to work on the oppp, the file does work in HDR10 on the 2017 shield, can't check on the 2019 shield as it is at my weekend address (won't be there again till Friday)…

According to the Nvidia's tech support ( unable to find the link to that post ), the new Shield TV supports only the latest Dolby Vision Profile 4 with MEL, no support for the FEL. Please, update us as soon as possible. I'd like to hear your feedback, and I am super curious whether the new Shield is going to play it in HDR10 like the 2017 version, or it will be in full Dolby Vision with FEL. With full FEL, with lossless Audio, and with the tools available on this forum (tremendous gratitude for yusecope for his hard work and others on this forum including you ), the new Shield TV can be the ultimate device!

I have already made plenty of DV movies using these tool with Atmos audio, few pages back talking about it.

I'm one of the ones who spoke to Nvidia about what the shield can output and they confirmed profile 4 MEL.

The only thing I can't confirm is what the shield is actually outputting when a FEL file is played.

What I do know is Doctor Strange which is a MEL movie definitely has color issues, but again I'm lead to believe this is a shield issue as per previous tests located a bunch of pages back.

According to the Profile 4 document above, the new Nvidia Shield TV suppose to exit and fall back to the HDR10/SDR format since, technically, it does not support the original Profile 4 with FEL, only MEL. And if I am understanding the document right, suppose the New Shield does support the Profile 4 FEL, which means there should be two hardware decoders decoding the layers simultaneously. Correct me if I am wrong.

edit:
"The only thing I can't confirm is what the shield is actually outputting when FEL file is played" - are you saying the New Shield is actually displaying the Dolby Vision logo when playing the video with FEL? If that's the case, it has to be the real FEL since the document above states the device has to display the video in standard range if it can not process the FEL layer