Dolby Vision now possible through MP4 Mux.

[atomdelpro]

The X700, X800M2, and Oppo Dolby Vision playback is less dynamic than CMv4.0 players, but the Jurassic Park clip has a 4000-nit MDL, so it should still have an effect. Try remuxing the file to TS, maybe.

https://github.com/justdan96/tsMuxer/releases

This worked! I was able to remux to a TS file and now I can see the difference. One thing for others who stumble upon this post, I was getting an error when trying to use the tsMuxerGUI from the GitHb page, I needed to also download tsMuxeR (nongui) and have both in the same folder in order for it to work.

[joseluko]

Problem with Dolby Vision when creating Blu-ray structure with tsMuxeR

Hello,

I have run into an issue while using tsMuxeR.

I have MKV files that I would like to convert into a Blu-ray disc structure (or ISO) so I can burn them to a physical disc.

The problem is that when the MKV file contains Dolby Vision, tsMuxeR gives a warning saying that the resulting disc may not play correctly.

I am not sure how to solve this issue. My goal is to keep some content that is only available on streaming platforms in a physical format.

Is there any way to fix this problem? Should I remove Dolby Vision, convert it, or use a different tool?

Any advice or guidance on where to look would be greatly appreciated.

Thank you very much.

[RESET_9999]

Yes, you need to remove DV if it’s a P8 hybrid WEB-DL. Only dual-layer, dual-track P7 is valid for Blu-ray discs with DV. A Blu-ray structure with P8 HEVC might still play on some Blu-ray players, but I’ve never tested it.
If the WEB-DL is cropped, the Blu-ray structure may not be valid either.

[joseluko]

Yes, you need to remove DV if it’s a P8 hybrid WEB-DL. Only dual-layer, dual-track P7 is valid for Blu-ray discs with DV. A Blu-ray structure with P8 HEVC might still play on some Blu-ray players, but I’ve never tested it.
If the WEB-DL is cropped, the Blu-ray structure may not be valid either.

How can I remove DV?

Mediainfo says this:

Video
ID : 1
Format : HEVC
Format profile : Main 10@L5@High
HDR format : Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2094 App 4, Version HDR10+ Profile B, HDR10+ Profile B compatible
Codec ID : V_MPEGH/ISO/HEVC
Bit rate : 24.4 Mb/s
Width : 3 840 pixels
Height : 1 746 pixels
Frame rate : 24.000 FPS
Bit depth : 10 bits

[Gatorman]

Mode 2 of the script can do this. Start here https://forum.doom9.org/showthread.php?t=185317

[LV8HD]

@RESET_9999 what do you think about https://github.com/tinof/hdr-analyze?

[RESET_9999]

@RESET_9999 what do you think about https://github.com/tinof/hdr-analyze?

useless since a free version of the official Dolby algo (cm_analyze) can be used to create proper cmv4.0 metadata.

[LV8HD]

useless since a free version of the official Dolby algo (cm_analyze) can be used to create proper cmv4.0 metadata.

Yeah, but what about HDR analysis with MadVR integration?

[RESET_9999]

useless since a free version of the official Dolby algo (cm_analyze) can be used to create proper cmv4.0 metadata.

Yeah, but what about HDR analysis with MadVR integration?

nothing new here, been available in my scripts for years.
DoVi_Scripts\tools\madMeasurementAnalyzer.exe

[LV8HD]

nothing new here, been available in my scripts for years.
DoVi_Scripts\tools\madMeasurementAnalyzer.exe

Sure. I was just wondering how it differed from the current implementation in your script, since I haven't been able to find officially updated sources for madMeasurementAnalyzer.exe and madMeasureHDR.exe.

By the way, talking about the measurement process in general: the -qscale:v parameter in ProRes encoding specifies to the encoder to use variable bitrate, and the integer value specifies how aggressively to compress the final media.

How big of an impact does the -qscale:v parameter play in the measurement process (whether for HDR, Dolby Vision and HDR10+)? How much does it differ compared to a constrained variable bitrate encoding (as per ProRes specification)?

[RESET_9999]

Sure. I was just wondering how it differed from the current implementation in your script, since I haven't been able to find officially updated sources for madMeasurementAnalyzer.exe and madMeasureHDR.exe.

Well, the madvr data is the same regardless of the tool you use to read it.

By the way, talking about the measurement process in general: the -qscale:v parameter in ProRes encoding specifies to the encoder to use variable bitrate, and the integer value specifies how aggressively to compress the final media.

How big of an impact does the -qscale:v parameter play in the measurement process (whether for HDR, Dolby Vision and HDR10+)? How much does it differ compared to a constrained variable bitrate encoding (as per ProRes specification)?

Negligible difference, but I wouldn't use a value higher than 8...

[Alldu]

Hi guys,

I've used to play my muxed DV movies on Sony X700, and now switching to Ugoos am6b+ with coreELEC. Pretty happy with the new toy, but I have one small thing that bothers me. I'm a sucker for pgs subs which I make myself to represent their theatrical look as close as possible, when they are not burned in the transfer itself. I didn't have this problem with X700, but when playing plain white subs on Ugoos (movies, like Godfather or Salvador), it seems Ugoos adds a tiny grey outline to them - even though there shouldn't be any. Kinda small thing, but it is very visible on my 65'' Sony OLED A95K.

It looks like that with the new mkv files and my old m2ts files. I tried AI, and I understood the reason is that Ugoos reads those PGS somehow differently from X700 - thus, the outline. So is there a workaround for it, perhaps? Or it is what it is? Thanks!

[Gatorman]

Hmm. Maybe ask here. https://www.avsforum.com/threads/ugoos- ... 6/page-608

[Alldu]

Hmm. Maybe ask here. https://www.avsforum.com/threads/ugoos- ... 6/page-608

Thanks for the tip, will do!

[jayper]

https://github.com/avdvplus/Builds/releases

That's the latest but make sure you go back and read the release notes for R1 and R2, as well. avdvplus did a LOT of work on Dolby Vision.

EDIT: Fixed the link...accidentally posted the same R3 link again.

Would love some assistance, I am still running the last CPM build from last year.

Can I upgrade from CPM to the avdvplus builds? Or do I need to start fresh?