Dolby Vision now possible through MP4 Mux.

[SamuriHL]

I'm sure they've tested profile 5 videos as well, but the doctor sleep sample was just the most prominent one that showed off the issue. It's also the one that was more readily available since I chopped up a sample of it. By using it and actually trying to correct behavior off of it, it's a good sign that it's meant to be supported, no? Otherwise, they could've simply just said it's not a supported file and no further action is needed. They may ultimately come back and say that these files are beyond the capabilities of the Shield, but at least they're trying to get to the bottom of it. As for the colorimeter and such, they're still out of the office at the moment so testing equipment and environment is understandably limited.

Yes, nVidia is and I commend them for it. But bringing this directly to Dolby was NOT wise. They are going to get slapped hard.

[shawnc22]

caveat is Dolby did put out the instructions themselves to convert dual PID to single PID so somebody was bound to try it , but excuse me while I go disable auto-update on my Shield...

[SamuriHL]

caveat is Dolby did put out the instructions themselves to convert dual PID to single PID so somebody was bound to try it , but excuse me while I go disable auto-update on my Shield...

You're not wrong but I think they figured "screw everyone, there's no devices that'll play them anyway so let's tease them." Now it's going to be "oh shit! STOP THAT!" I really hope I'm wrong. Dolby honestly needs a bit more support anyway because HDR10+ is a fairly strong standard. And nVidia is obviously paying them their mafia payout, er, I mean licensing fees. So we'll see. But yes, disabling auto-update may be a joke, but, maybe we let other people experiment with that going forward. COUGH COUGH

[shawnc22]

caveat is Dolby did put out the instructions themselves to convert dual PID to single PID so somebody was bound to try it , but excuse me while I go disable auto-update on my Shield...

You're not wrong but I think they figured "screw everyone, there's no devices that'll play them anyway so let's tease them." Now it's going to be "oh shit! STOP THAT!" I really hope I'm wrong. Dolby honestly needs a bit more support anyway because HDR10+ is a fairly strong standard. And nVidia is obviously paying them their mafia payout, er, I mean licensing fees. So we'll see. But yes, disabling auto-update may be a joke, but, maybe we let other people experiment with that going forward. COUGH COUGH

There's also Dolby's own mp4muxer that does something similar and creates files that, for some reason, are playable on LG TVs. So I'm optimistic here that nvidia will, at worst, keep things as is and not roll back any features.

[SamuriHL]

That would be good. Better still if they could fix it.

Sent from my SM-G975U using Tapatalk

[DaMacFunkin]

All I know is that Dolby hates MKV, if you have an Oppo, Dolby’s HDR10 tone mapping will not work on MKV files, the Oppo documentation actually states ‘Dolby sees MKV as piracy’.

[MastaG]

New firmware for 2018 LG OLED models released today.
Version 05.20.0x and it seems to update the Dolby Vision version.
Didn't do any testing yet. But I'm curious whether it could fix some of the performance problems with FEL remuxes.

[SamuriHL]

I wonder if they finally fixed the near black issues when calibrating Dolby vision. Interesting.

Sent from my SM-G975U using Tapatalk

[McZuzlak]

some of the performance problems with FEL remuxes.

What kind of performance problems ? Ob my LG C7 ( not 2018 but close ) I didn't saw any.

[MastaG]

some of the performance problems with FEL remuxes.

What kind of performance problems ? Ob my LG C7 ( not 2018 but close ) I didn't saw any.

Movies such as 1917 or Gemini Man (which is a high frame rate movie) will only play if you remux them with metadata only (mode 2 using yusesope's tool).
If you remux it as dual pid (using mp4muxer) or mode 1 with yusesope's tool (e.g. keeping the full enhancement layer). It will stutter.

[RESET_9999]

Here's proof that the red artifacts on the Doctor Sleep UHD-BD rip is a different issue and have nothing to do with the BT2020 flag. But that doesn't mean the bt2020 flag does nothing to the image.

Shield Default bt2020 RGB Movies Anywhere (fullrange profile 5) VS Shield Default bt2020 UHD-BD RIP
https://screenshotcomparison.com/comparison/5222

So there are actually 2 issues:

1- one that causes a red push on all the UHD-BD rip. The problem is not the file because the SL-DL is identical to the profile 7 DL on my x700 as shown here: https://screenshotcomparison.com/comparison/4913

2- a 2nd red push caused by the bt2020 flag that affects all the streaming app and plex
Shield Default bt2020 UHD-BD RIP VS Shield RGB vertex UHD-BD RIP
https://screenshotcomparison.com/comparison/5224

Shield Default bt2020 RGB Movies Anywhere VS Shield RGB vertex Movies Anywhere
https://screenshotcomparison.com/comparison/5225

Shield Default bt2020 RGB NETFLIX VS Shield RGB vertex NETFLIX:
https://screenshotcomparison.com/comparison/5188


you can clearly see that removing the bt2020 flag fix the red push on profile 5 full range files. In fact, it's slightly affecting all the colors. blue green red yellow

[shawnc22]

Here's proof that the red artifacts on the Doctor Sleep UHD-BD rip is a different issue and have nothing to do with the BT2020 flag. But that doesn't mean the bt2020 flag does nothing to the image.

Shield Default bt2020 RGB Movies Anywhere (fullrange profile 5) VS Shield Default bt2020 UHD-BD RIP
https://screenshotcomparison.com/comparison/5222

So there are actually 2 issues:

1- one that causes a red push on all the UHD-BD rip. The problem is not the file because the SL-DL is identical to the profile 7 DL on my x700 as shown here: https://screenshotcomparison.com/comparison/4913

2- a 2nd red push caused by the bt2020 flag that affects all the streaming app and plex
Shield Default bt2020 UHD-BD RIP VS Shield RGB vertex UHD-BD RIP
https://screenshotcomparison.com/comparison/5224

Shield Default bt2020 RGB Movies Anywhere VS Shield RGB vertex Movies Anywhere
https://screenshotcomparison.com/comparison/5225

Shield Default bt2020 RGB NETFLIX VS Shield RGB vertex NETFLIX:
https://screenshotcomparison.com/comparison/5188


you can clearly see that removing the bt2020 flag fix the red push on profile 5 full range files. In fact, it's slightly affecting all the colors. blue green red yellow

The tag is going away in the next firmware release so I'm glad we're at least solving one issue. Have you had a chance to look at that LG profile 4 BL+EL+RPU video to see if you notice any oddities when compared to another soc?

[RESET_9999]

The tag is going away in the next firmware release so I'm glad we're at least solving one issue.

Really can't wait for that !!!

Have you had a chance to look at that LG profile 4 BL+EL+RPU video to see if you notice any oddities when compared to another soc?

Damn, this is on my todo list but I completely forgot. I'll try that tomorrow night. thank's for reminding me.

[SamuriHL]

Well....it's an improvement. We'll see what they turn up. Especially with their discussion with Dolby. But at least the BT.2020 flag being removed should help. I still don't understand how that works with my UB820 because it's sending the BT.2020 flag and it's definitely doing the correct colors.

[McZuzlak]

Out of curiousity did anyone try reencoding the BL ( same res just lower bitrate x265 ) and then mux it with the original EL into mp4? I wonder if that would be still playble on my LG C7 internal player.