Dolby Vision now possible through MP4 Mux.

[deadchip12]

#1 Buy a Sony UBP-X800M2
#2 Make a full-disc decrypted backup using MakeMKV
#3 Find the playlist for the version of the movie you want (it's probably 00800.mpls for the English version)
#4 Drop that into tsMuxer
#5 Set it to output M2TS, and select the audio and subtitle tracks you want
#6 Watch the movie
#7 Be free
#8 Live your life
#9 Never think about Dolby Vision ever again

Hmm why #4 and #5? Cna't the X800M2 play the full-disc backup directly?

So my hope of getting a x800m2 is gone. There's really no place in my country that sells it.

Is it particularly difficult to import things in your country? There do seem to be lots of places that sell the X800M2 and will ship internationally (but I know there are sometimes a few countries that they can't ship to).

I just checked and Amazon can ship to my country but the import fee is pretty high, adding 40%-50% markup on top of the original price. Same if I ask some 3rd party local company to ship it for me instead. Manufacturer's warranty is another problem. It won't apply abroad I suppose. I'm not sure if all these are worth the improvement over the x700 which I can purchase locally. I live in Vietnam btw.

[FubbAyH]

Ah dang, yeah those import fees suck

[bhuno33]

Hey everybody first post here ... Wanted to know if the x700 does TV-led DV when playing back .m2ts backups via usb created using latest tsmuxer nightly (using full UHD BD backups), and also why creating a bdmv folder is now recommended for the x700? I never had an issue ff or rw with .m2ts files that i noticed at least, and the green screen bug I just worked around by restarting as I'm not switching between content that often. Sorry if this has been answered already finding a bit hard to read through all the posts.

[FubbAyH]

I've been having more adventures with re-ripping for my X800M2. To cut a very long story short, it turns out that the current nightly builds of tsMuxer are producing corrupted output so I thought I should post a warning about that here. Apparently the last working version is the 23 January nightly, and there's a GitHub issue for the corruption bug.

The good news for me is that that's hopefully the source of all my woes. I've just gotta remux for the four-millionth time now to find out, so please wish me luck.

[RESET_9999]

The good news for me is that that's hopefully the source of all my woes

My Dune 2021 test was with the latest tsmuxer and didn't get the error you're getting but it could explain the issue I'm having when I remux from dual track MKV.
My BTTF files were made a long time ago with an older tsmuxer.

but thanks for the info, I'll downgrade to the older version.


EDIT:, nop, dual track mkv to ts still doesn't work.

[Albano]

@RESET_9999
I used your tool to create measurements of Smurfs.The.Lost.Village.2017 in many times but received result always is a Smurfs.The.Lost.Village.2017.mkv.measurements.incomplete 71.4MB
So should I use it?

[Epedemic]

I've been having more adventures with re-ripping for my X800M2. To cut a very long story short, it turns out that the current nightly builds of tsMuxer are producing corrupted output so I thought I should post a warning about that here. Apparently the last working version is the 23 January nightly, and there's a GitHub issue for the corruption bug.

The good news for me is that that's hopefully the source of all my woes. I've just gotta remux for the four-millionth time now to find out, so please wish me luck.

Great... I just redid a shitload of bdmv folders to .ts with the bugged tsmuxer :/ Any chance of fixing these corrupt .ts files, or do i have to start ALL over? :/

[FubbAyH]

I don't know enough about the bug to know whether the files would be fixable, but it might be worth checking your M2TS files with:

Code: Select all

ffmpeg -i testfile.m2ts -f null -

to see if they're okay. It might be that only DV streams are affected, or something like that.

[Epedemic]

You need to demux the video first, and then run the script on the HEVC file.
example: python hdr10plus_remove.py -i video.hevc -o processed_file.hevc

Thanks for that. Is there an idiots guide on HDR10+ to DV conversion?

I wrote up how this idiot does it here:

https://www.avsforum.com/threads/author ... t-60952335

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Turn HDR10+ metadata into Dolby Vision metadata**
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Command 1: 'hdr10plus_tool extract Video.hevc -o Metadata.json' (Extracts HDR10+ metadata and saves to .json file)

>>Next commands go through Dovi_Tool and v0.5.0 minimum required<<<
Command 2: 'dovi_tool generate -j Extra.json --hdr10plus-json Metadata.json --rpu-out RPUPlus.bin' (combines metadata from edited 'Extra.json' - template is below and you need to do one for every title specifically - and metadata from extracted 'Metadata.json' and combines+converts them into p8 RPU metadata format)

Command 3: 'dovi_tool.exe inject-rpu --input Video.hevc --rpu-in RPUPlus.bin' (Injects HDR10+ generated RPU metadata into HEVC stream turning it into single layer Dolby Vision 8 stream)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Blank Template for 'Extra.json'
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
{
"length": (title specific framelength here without parenthesis),
"level2": [
{
"target_nits": 100
},
{
"target_nits": 600
},
{
"target_nits": 1000
},
{
"target_nits": 2000
}
],
"level6": {
"max_display_mastering_luminance": (title specific metadata info here without parenthesis),
"min_display_mastering_luminance": (title specific metadata info here without parenthesis),
"max_content_light_level": (title specific metadata info here without parenthesis),
"max_frame_average_light_level": (title specific metadata info here without parenthesis)
}
}
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Another question: I have a few HDR10+ files i want to "convert" to DV, but the

Maximum Content Light Level & Maximum Frame-Average Light Level lines are missing in mediainfo. Is there some default value to use and hope for the best, or are there some way to find the correct values?

[RESET_9999]

@RESET_9999
I used your tool to create measurements of Smurfs.The.Lost.Village.2017 in many times but received result always is a Smurfs.The.Lost.Village.2017.mkv.measurements.incomplete 71.4MB
So should I use it?

I don't know , is that a seamless branching disc? I think so...
How did you rip your disc? do not use mkvtoolnix or makemkv when the disc has multiples m2ts. always use tsmuxer.

Great... I just redid a shitload of bdmv folders to .ts with the bugged tsmuxer :/ Any chance of fixing these corrupt .ts files, or do i have to start ALL over? :/

Yea, 2nd time in 2 months they mess up Dolby Vision. I'll just stop updating tsmuxer unless there's a major update...

Another question: I have a few HDR10+ files i want to "convert" to DV, but the

Maximum Content Light Level & Maximum Frame-Average Light Level lines are missing in mediainfo. Is there some default value to use and hope for the best, or are there some way to find the correct values?

It's not missing, it's just set to 0

[Epedemic]

Thank you once again. You are awesome

[sickb]

Does anyone have an idea why I get different results...
in the first case I have a 49.3mb/s 42.7gb video track
in the seco case I have a 48.0mb/s 41.6gb video track

That's weird indeed. Maybe waste of space in MEL that tsMuxer would solve when muxing? I recently had a title with 1.6 GB MEL, of which RPU was 36MB. You can of course investigate by demuxing BL and EL from both mkvs and compare sizes.

Even better of course is what RESET_9999 suggested and convert to Profile 8.1 "BL+RPU". You'll have no EL at all.

I just tried the same with James Bond: No Time To Die. It's a FEL movie, and it has the same quirk;
- Direct to MKV: 56.6MBPS, 64.7GB, 58,1 GB BL, 6,53 GB EL
- TS-BDMV-MKV: 52.6MBPS, 60.1GB, 58,1 GB BL, 1,93 GB EL
So it removes about 4.6GB of EL somehow..

[x08vick80x]

Very very interesting... I would like to test it but I'm not sure what values I have to put in the Extra.json, could someone help please ? If I understand well and from what mediainfo tells me :

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 32 min
Bit rate : 4 511 kb/s
Width : 3 840 pixels
Height : 1 600 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Variable
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.031
Stream size : 4.82 GiB (88%)
Default : Yes
Forced : No
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.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 977 cd/m2
Maximum Frame-Average Light Level : 344 cd/m2

I would fill the json like this :

{
"length": 9120, //which is the video duration converted to seconds
"level2": [
{
"target_nits": 100
},
{
"target_nits": 600
},
{
"target_nits": 1000
},
{
"target_nits": 2000
}
],
"level6": {
"max_display_mastering_luminance": 1000, //don't know if cd/m2 is needed here
"min_display_mastering_luminance": 0.0050,
"max_content_light_level": 977,
"max_frame_average_light_level": 344
}
}

I have an error : Error: invalid type: floating point 0.005, expected u16 at line 19 column 50

PS : wouldn't be possible to reduce max luminence in the extra.json considering that OLED TVs can't reach 1000nits ? (Mine is around 700)

[staknhalo]

I just tried the same with James Bond: No Time To Die. It's a FEL movie, and it has the same quirk;
- Direct to MKV: 56.6MBPS, 64.7GB, 58,1 GB BL, 6,53 GB EL
- TS-BDMV-MKV: 52.6MBPS, 60.1GB, 58,1 GB BL, 1,93 GB EL
So it removes about 4.6GB of EL somehow..

what happens when you mux the smaller fel stream alone (no BL stream) into mkv and try to playback? do you still see obvious motion/video data as with full fel or is it all green/solid blank color always as with mel?

[RESET_9999]

I just tried the same with James Bond: No Time To Die. It's a FEL movie, and it has the same quirk;
- Direct to MKV: 56.6MBPS, 64.7GB, 58,1 GB BL, 6,53 GB EL
- TS-BDMV-MKV: 52.6MBPS, 60.1GB, 58,1 GB BL, 1,93 GB EL
So it removes about 4.6GB of EL somehow..

I don't see why someone would use that workflow, it doesn't make sense. If you want a ST-DL file, do not use makemkv, just use yusesope tool.

here's the problem:



what is strange though is that eac3to detect a video delay in both streams with the DT-DL TS...

top= original