Dolby Vision now possible through MP4 Mux.

[speeddemon]

I think I found a huge bug on the x700/ x800m2 / C2, even worse than the red push or the lack of FEL support
The L1 brightness changes are totally different than the C2 internal plex and the Shield(which have newer DV engine) but L2 looks exactly the same on all the devices.
By different I mean they are much much less noticeable on the x700/ x800m2 . like 400% difference, no exaggeration. Even less noticeable than Windows 10 HDR10 P8 playback lol.

If you take the out-of-sync version of the Spears and Munsil clip, because the trim passes are active with L1 at the same time, you can barely see a difference between all the devices.
But if you strip out the trims by generating new metadata with madVR (just L1), then again a big difference in the L1 brightness changes.
Tried MP4 / TS, and it makes no difference.cmv2.9, cmv4.0, old mp4muxer, new mp4muxer.

maybe the newer DV engine of the C2/shield vs the older one from x700/x800m2 cause the issue?
I guess I have to connect my old C8 to find out...

pattern to reproduce:
quietvoid's rpu test: https://drive.google.com/file/d/1hAv4eJ ... sp=sharing
SM clip out of sync original: https://drive.google.com/file/d/1BxsK7- ... sp=sharing
SM clip out of sync no L2 (madvr): https://drive.google.com/file/d/1CuWlHK ... sp=sharing

########################################################################################################################
EDIT: no issue on the C8 + x700/x800m2 vs internal player, L1 changes as pronounced as on the C2/shield.
so it looks like there's something going on when using a CMv2.9 HDMI device to a CMv4.0 TV... Or maybe just something with my C2, I hope people with C1,CX will do the same test
I guess I just lost fel and lossless audio support

bug confirmed on:
LG C2 + x700 + x800m2
LG G2 + oppo: viewtopic.php?p=124746#p124746
LG C1 + x800m2: viewtopic.php?p=124868#p124868
LG C9 + x700: viewtopic.php?p=124959#p124959
Sony X900H + x800m2 https://www.avsforum.com/threads/offici ... t-61832553


videos showing the L1 issue on LG C2:
https://www.youtube.com/watch?v=TJtwu1bwlug

@RESET_9999 apologies for bringing up a post from so long ago.
Is this still a bug?
Does it impact all LG C9 and newer displays when connected to CMv2.9 native players/devices?
Thanks.

[RESET_9999]

I literally gave my latest update on different rpu responses on players like 3 posts ago...

[speeddemon]

I literally gave my latest update on different rpu responses on players like 3 posts ago...

That's why I went searching for that old post... the correlation wasn't clear to me. I'll re-read though and try to understand. Thanks for all your research; I'm just nowhere near your level of understanding.

I guess the part I'm most confused on still is how this relates to the TV. There was some talk earlier in this thread (after your post I quoted) where people were saying these CMv2.9 playback devices wouldn't work with newer TVs. Is that actually the case or is the TV not part of the equation... for example, I use my Oppo UDP-203 right now to compare against with the LG C9... If I were to swap the C9 out for a G3 would the Oppo be effectively useless?

[azreil24]

Thank you for the great tool, sir. Quick question please. I have an MKV which only had HDR10+ for dynamic metadata, for which I used the other tools to turn into DV8. If I use the MODE.H flow, MODE.1 (as I see that MODE.2 which says HDR10plus to DoVi maker, is tagged as Not Recommended), will it use the correct HDR10+ layer to generate a new DoVi or it will also take in consideration the Profile 8 I had in the MKV also?

LE: My first attempt on this and for some reason it couldn't find the files it generated, although they were there while it was processing prior to this step. Not sure what happened.

Removing L2 trims.
Copyright (c) 2013-2023 Dolby Laboratories, Inc. All Rights Reserved
12/31/2023/15:06:55.502000000 metafier: ERROR Unable to open Metadata file 'E:\DoVi.Scripts\temp.folder77\Basterds_DV.xml'
Generate RPU from XML
Parsing XML metadata...
Error: The system cannot find the file specified. (os error 2)
File not found - Basterds_DV.xml
The system cannot find the file specified.
Error: The system cannot find the file specified. (os error 2)
Error: expected value at line 21 column 35
Error: The system cannot find the file specified. (os error 2)
Parsing RPU file...
Error: The system cannot find the file specified. (os error 2)
Press any key to continue . . .
mkvmerge v81.0 ('Milliontown') 64-bit
Error: The type of file 'E:\DoVi.Scripts\Basterds_Generated.hevc' could not be recognized.

[RESET_9999]

That's why I went searching for that old post... the correlation wasn't clear to me. I'll re-read though and try to understand. Thanks for all your research; I'm just nowhere near your level of understanding.

I guess the part I'm most confused on still is how this relates to the TV. There was some talk earlier in this thread (after your post I quoted) where people were saying these CMv2.9 playback devices wouldn't work with newer TVs. Is that actually the case or is the TV not part of the equation... for example, I use my Oppo UDP-203 right now to compare against with the LG C9... If I were to swap the C9 out for a G3 would the Oppo be effectively useless?

It could just be how the cmv2.9 devices were made(chromecast seem different but cant do tv-led), I think they always target the TV edid regardless of L1. I believe the oppo is the same and the rpu reaction difference I mentioned on my old C8 is most likely because the C2 original DV configuration was broken and brightened everything. When they fixed the C2, my C8 was already sold so I couldn't test that anymore.

[RESET_9999]

Thank you for the great tool, sir. Quick question please. I have an MKV which only had HDR10+ for dynamic metadata, for which I used the other tools to turn into DV8. If I use the MODE.H flow, MODE.1 (as I see that MODE.2 which says HDR10plus to DoVi maker, is tagged as Not Recommended), will it use the correct HDR10+ layer to generate a new DoVi or it will also take in consideration the Profile 8 I had in the MKV also?

LE: My first attempt on this and for some reason it couldn't find the files it generated, although they were there while it was processing prior to this step. Not sure what happened.

Workflow 3-2 is not recommended because the HDR10plus average pq metadata are calculated differently. Dolby latest cmv4.0 algo is very conservative(targets 92nits) while HDR10plus is more representative of the brightness and can have much higher values which could result in unexpected tone mapping when you straight convert HDR10plus to DV. see: https://slow.pics/c/WlGwchoE
L1 avg_pq has none to very little effect on 1000nits RPU though but for 4000nits RPU, it does react to avg a lot.


As for 3-1, when you input a file that contains HDR10plus or DV, the script will use only their original scene cuts and generate new proper dv metadata based on those cuts with the latest Dolby algo.
For your error, you did not provide enough information for me to help you. Post the complete log with echo set to on and mediainfo of your input.

[azreil24]

Many thanks for your input. I will do some more testing and hopefully I will get the hang of it. I love these things, but never had time to dive into such detail, that is why the Dolby Vision Tool by QfG came in handy.

I also checked your Dolby Vision stuff sheet and I see multiple cases differentiated by playback conditions. For now I am with the Zidoo Z9X Pro + LG C2 camp, but I do not look to convert the movies I have too specifically, like make it work as good as it gets for Zidoo and lose some things down the road, in case I change the player, to have things misaligned and having to rip the files again. So what would it be the best way to have the disk transferred to MKV and keep everything from the disk intact without affecting PQ in any way? Is MakeMKV enough for that? I basically extract only the video, main English audio and Subs, to save space, with MakeMKV and that is it. At least for DV, as it seems that with HDR things are more simple and it's not as convoluted as with DV. I see you mention "quality loss if content is FEL" but I suppose that is only applicable to that specific player, the Neo thingy, right?

[RESET_9999]

Many thanks for your input. I will do some more testing and hopefully I will get the hang of it. I love these things, but never had time to dive into such detail, that is why the Dolby Vision Tool by QfG came in handy.

I also checked your Dolby Vision stuff sheet and I see multiple cases differentiated by playback conditions. For now I am with the Zidoo Z9X Pro + LG C2 camp, but I do not look to convert the movies I have too specifically, like make it work as good as it gets for Zidoo and lose some things down the road, in case I change the player, to have things misaligned and having to rip the files again. So what would it be the best way to have the disk transferred to MKV and keep everything from the disk intact without affecting PQ in any way? Is MakeMKV enough for that? I basically extract only the video, main English audio and Subs, to save space, with MakeMKV and that is it. At least for DV, as it seems that with HDR things are more simple and it's not as convoluted as with DV. I see you mention "quality loss if content is FEL" but I suppose that is only applicable to that specific player, the Neo thingy, right?

The zidoo cannot do true TV-LED so you're stuck with all its bugs/limitations and it will never be as good as a player that can do true TV-LED (sony, oppo, atv, shield).
Also, the C2 is probably the last generation that can play DV ''properly'' on this device, and any TV with an edid higher than 1000nits will be wrong on this player when the DV RPU mastering display is under the target.

Makemkv or mkvtoolnix are fine to create P7 ST rip from BD but it is useless to your device because it cannot process the EL. So you can save some HDD space and convert them to profile 8 (workflow 4-1-1 or 4-2).
There's a list in my signature of which movies cannot be played without FEL and its applicable to any player that cant decode the EL.

[azreil24]

The zidoo cannot do true TV-LED so you're stuck with all its bugs/limitations and it will never be as good as a player that can do true TV-LED (sony, oppo, atv, shield).
Also, the C2 is probably the last generation that can play DV ''properly'' on this device, and any TV with an edid higher than 1000nits will be wrong on this player when the DV RPU mastering display is under the target.

Makemkv or mkvtoolnix are fine to create P7 ST rip from BD but it is useless to your device because it cannot process the EL. So you can save some HDD space and convert them to profile 8 (workflow 4-1-1 or 4-2).
There's a list in my signature of which movies cannot be played without FEL and its applicable to any player that cant decode the EL.

Yeah, I know. I can some differences when playing the same content on my Panasonic UB820 compared to Zidoo, but can't put my finger on what, as differences seems small when I can't compare them side by side, but the UB820 seems better to my eyes still (could be due to the EL also?). From what I know there isn't any complete package out there with having the control over your library like you can with a Zidoo type of machine and have correct DV output like you have with a dedicated Blu-ray player. In case I missed that and there is, as I can still return the Zidoo )

I don't want to remove the EL just for the sake of space and maybe regret it later, just because the Zidoo can't use it. I barely have time to set things up now, as I just got the Zidoo, so I don't want to waste more time later on re-ripping stuff and re-converting. Sadly the Plex can't play DV and it has to do video transcoding on the C2 native app if I have DTS sound and subs, which messes up the HDR.

[RESET_9999]

Sadly the Plex can't play DV and it has to do video transcoding on the C2 native app if I have DTS sound and subs, which messes up the HDR.

yep. The best solution for the plex internal app is to convert audio to EC3 and use external SRT with the TS container.
or use the mp4 container with internal timed text but I noticed that mp4box sometimes causes audio drop out/stuttering with EC3 atmos tracks.

[azreil24]

These are the plots for Inglorious Basters which came with HDR10+ on disk and which I converted to DV profile 8. Will be curious to see what the DV plot will look like once create using your tool.

[speeddemon]

because the C2 original DV configuration was broken and brightened everything. When they fixed the C2, my C8 was already sold so I couldn't test that anymore.

That part answers my question. I was wondering if the C2 was ever fixed and it sounds like you're saying that it was. I have a C8, C9, and C2 on hand if you want anything tested with them. I also have access to a CX, C1, and C3.

[RESET_9999]

I also have access to a CX, C1, and C3.

I'd be curious to know if L2 trim Chroma Weight work on the C3. It doesn't on the C2 internal player or TV-LED hdmi.
https://drive.google.com/file/d/1qdHux6 ... drive_link

PS, using the C2 edid on my cheap Vizio TV + x700/x800, Chroma Weight is working so no reason to not work on the C2.

[susanstone2022]

x700 doesnt support cmv4.0 so it doesnt matter

Regarding CMv4.0 and CMv2.9 discussion, there are player devices and display devices in TV-led DV mode.
Does a CMv2.9 player care if the metadata is CMv4.0 or CMv2.9?
If player is CMv4.0 but TV is CMv2.9, does the player send over full CMv4.0 data (both L2 and L8) or the player does some processing only send L8 data? If full CMv4.0 data is sent, TV should use L2 data?

Thank you in advance!

[RESET_9999]

In order to display CMV4.0 videos, both the TV and the player must support it.

If the player is cmv2.9, it doesn't matter if the content is 4.0 and the player only uses the cmv2.9 block
if the player is cmv4.0 but the TV is not , only the 2.9 block is used unless the player is in LLDV mode.