Dolby Vision now possible through MP4 Mux.

[shawnc22]

https://www.nvidia.com/en-us/geforce/fo ... n/2791567/

bit of an update for those following. good news that it's gone up the chain all the way to dolby (although they may not be entirely happy we've been creating these frankenstein files off of uhd discs ), so hopefully a resolution is in sight

[RESET_9999]

https://www.nvidia.com/en-us/geforce/fo ... n/2791567/

bit of an update for those following. good news that it's gone up the chain all the way to dolby (although they may not be entirely happy we've been creating these frankenstein files off of uhd discs ), so hopefully a resolution is in sight

why the hell would they make that test with a uhd-bd rip? They need to test genuine profile 5 full-range content (Netflix, disney+, vudu etc) since no one knows if the Shield can play uhd-bd DV rip properly in the first place.

omg, they took pictures as we do, but not even in a dark room, pictures not even taken at the same distance... Thought they would use a color meter or something more professional.
https://www.nvidia.com/en-us/geforce/fo ... n/2791563/

eventhough the distance difference and the bright room, I still can see the same red push on the red flower in their pictures:
https://screenshotcomparison.com/comparison/5129

On this subject, if I use ffmpeg to copy, will it work in the same way as MKVToolNix? Or does ffmpeg still need new updates for this to work?
I use a recent BETA / Nightly version.
I'm new to this subject, so I don't have a lot of knowledge.
Thanks.

I don't know.

[mike admin]

On this subject, if I use ffmpeg to copy, will it work in the same way as MKVToolNix? Or does ffmpeg still need new updates for this to work?

Latest MKVToolnix only preserves DV descriptors, so you have to have a "good" MKV file to begin with.
Both mkvmerge and ffmpeg (all versions really) preserve bitstream data.
Ffmpeg and all previous versions of mkvmerge destroy DV metadata.
Next version of MakeMKV would be able to open an MKV file with totally bogus or missing DV metadata and fully rebuild a proper DV metadata. I feel sort of proud of it, as no other tool can do that, not even mp4mux
This effectively makes it possible to edit and convert any file to a proper DV MKV - copy/convert mp4 or ts to MKV with ffmpeg or mkvmerge, edit as you wish, then open with MakeMKV and it would rebuild all descriptors and make a nice clean DV MKV. That's how the test samples at https://www.makemkv.com/download/dvtest/ were made. PM if you want it for testing...

[shawnc22]

https://www.nvidia.com/en-us/geforce/fo ... n/2791567/

bit of an update for those following. good news that it's gone up the chain all the way to dolby (although they may not be entirely happy we've been creating these frankenstein files off of uhd discs ), so hopefully a resolution is in sight

why the hell would they make that test with a uhd-bd rip? They need to test genuine profile 5 full-range content (Netflix, disney+, vudu etc) since no one knows if the Shield can play uhd-bd DV rip properly in the first place.

omg, they took pictures as we do, but not even in a dark room, pictures not even taken at the same distance... Thought they would use a color meter or something more professional.
https://www.nvidia.com/en-us/geforce/fo ... n/2791563/

eventhough the distance difference and the bright room, I still can see the same red push on the red flower in their pictures:
https://screenshotcomparison.com/comparison/5129

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.

[SamuriHL]

https://www.nvidia.com/en-us/geforce/fo ... n/2791567/

bit of an update for those following. good news that it's gone up the chain all the way to dolby (although they may not be entirely happy we've been creating these frankenstein files off of uhd discs ), so hopefully a resolution is in sight

Ohhhhhhh FFS. Well, it's been fun while it lasted. Getting Dolby involved was the WORST possible outcome as they will order them to kill any "support" for it or lose their Dolby certification. F*************.

[RESET_9999]

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.

I really hope the did try profile 5 content. A bit disappointed by their response.
Anyway, I really hope they figure it out so I can finally enjoy my 6-month-old Shield with only 24h of use lol.

Ohhhhhhh FFS. Well, it's been fun while it lasted. Getting Dolby involved was the WORST possible outcome as they will order them to kill any "support" for it or lose their Dolby certification. F*************.

haha! that would be awful.

[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.