Dolby Vision now possible through MP4 Mux.

[DolbyVisionFTW]

Thanks for the replies above guys.

[DaMacFunkin]

Or is the conclusion that Chinoppo is still the only player that properly support FEL playback?

Ugoos AM6+ has a 2nd decoder so is able to playback FEl (from dual track mp4) but it's a very buggy player.

You may want to ask yourself how many tv's support full 12 bit processing. And then yet, those 12bit colors will be downscaled within max luminance capacity of the screen. TBH, I think that nowadays tv's will not hit enough nits to even support 10 bit to its full brightness.

Even though Ugoos / Am6+ can display FEL titles they don’t have a Dolby Vision SDK so it isn’t actually accurate so a waste of time.

Don’t forget a lo to of recent Fel titles have contained significant picture detail in the enhancement layer, it isn’t always just 2 bits of extra colour in the Fel layer.

[DolbyVisionFTW]

Can either the Oppo 203 or 205 do anything the Sony X700 can't as far as DV BL+FEL+RPU? From what I've read, the Oppo supports ISO whereas the X700 only supports BDMV folders. I also read the X700 supports BDMV folders via USB only and not LAN. Not sure about the Oppo?

Thanks.

[nasuel]

Hi folks,

i have a problem with the process to get an DV MP4 file running on the Apple TV 4k with iOS 15 and the latest Infuse release from the App-Store.

What i've done:
- Ripped the entire UHD Blu Ray with MakeMKV
- Extracted the M2TS File with TsMuxR
- Extracted the base Layer and the enhanced Layer from the M2TS file with `ffmpeg -i 00801.m2ts -c copy -map 0:0 bl.hevc -c copy -map 0:1 el.hevc`
- Extracted the RPU from the el.hevc with `./dovi_tool extract-rpu -i el.hevc -o rpu.bin`
- Re-Injected the RPU to the bl.hevc with `./dovi_tool inject-rpu -i bl.hevc --rpu-in rpu.bin -o bl.rpu.full.hevc`
- Created a MP4 File with `./mp4muxer_mac -o full.rpu.mp4 -i bl.rpu.full.hevc -i aud1.ac3 --media-lang deu -i aud2.ac3 --media-lang eng --dv-profile 5`

Infuse recognizes the File as DV File but when a start playback the TV shows only HDR. Here are the metadata informations of the final output file:

General
Complete name : full.rpu.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (mp42/dby1/isom)
File size : 44.9 GiB
Duration : 2 h 29 min
Overall bit rate : 42.9 Mb/s
Encoded date : UTC 2021-12-24 12:02:44
Tagged date : UTC 2021-12-24 12:02:44

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision
Duration : 2 h 29 min
Bit rate : 42.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
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.211
Stream size : 44.0 GiB (98%)
Default : Yes
Alternate group : 1
Encoded date : UTC 2021-12-24 12:02:44
Tagged date : UTC 2021-12-24 12:02:44
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.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 696 cd/m2
Codec configuration box : hvcC+dvcC

Audio #1
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : ac-3
Duration : 2 h 29 min
Bit rate mode : Constant
Bit rate : 448 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 480 MiB (1%)
Language : German
Service kind : Complete Main
Default : Yes
Alternate group : 2
Encoded date : UTC 2021-12-24 12:02:44
Tagged date : UTC 2021-12-24 12:02:44

Audio #2
ID : 3
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : ac-3
Duration : 2 h 29 min
Bit rate mode : Constant
Bit rate : 448 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 480 MiB (1%)
Language : English
Service kind : Complete Main
Default : No
Alternate group : 2
Encoded date : UTC 2021-12-24 12:02:44
Tagged date : UTC 2021-12-24 12:02:44

What i'm doing wrong in my process?

Thanks a lot
Regards and Merry Christmas

[quietvoid]

Hi folks,

i have a problem with the process to get an DV MP4 file running on the Apple TV 4k with iOS 15 and the latest Infuse release from the App-Store.
...

Infuse recognizes the File as DV File but when a start playback the TV shows only HDR. Here are the metadata informations of the final output file:

What i'm doing wrong in my process?

Thanks a lot
Regards and Merry Christmas

You're trying to trick Infuse to think the file is profile 5 when it's not.
The Apple TV only supports profile 5 and profile 8.4, which are not HDR10.

[staknhalo]

profile 8.4

I wonder if they'll try to do OTA Dolby Vision in USA/Canada with HLG being part of ATSC 3.0?

[nasuel]

Hi folks,

i have a problem with the process to get an DV MP4 file running on the Apple TV 4k with iOS 15 and the latest Infuse release from the App-Store.
...

Infuse recognizes the File as DV File but when a start playback the TV shows only HDR. Here are the metadata informations of the final output file:

What i'm doing wrong in my process?

Thanks a lot
Regards and Merry Christmas

You're trying to trick Infuse to think the file is profile 5 when it's not.
The Apple TV only supports profile 5 and profile 8.4, which are not HDR10.

What steps have i to do to make the file to a Profile 5 file? I thought that was these two steps

- Re-Injected the RPU to the bl.hevc with `./dovi_tool inject-rpu -i bl.hevc --rpu-in rpu.bin -o bl.rpu.full.hevc`
- Created a MP4 File with `./mp4muxer_mac -o full.rpu.mp4 -i bl.rpu.full.hevc -i aud1.ac3 --media-lang deu -i aud2.ac3 --media-lang eng --dv-profile 5`

Thanks a lot
Regards

[quietvoid]

What steps have i to do to make the file to a Profile 5 file? I thought that was these two steps

You can't, the video is still HDR10.

[nasuel]

What steps have i to do to make the file to a Profile 5 file? I thought that was these two steps

You can't, the video is still HDR10.

Okay, so that means at the moment it is not possible to create a backup of a Dolby Vision UHD BD to play on AppleTV with Dolby Vision, correct.

Thanks and regards

[ad329]

What steps have i to do to make the file to a Profile 5 file? I thought that was these two steps

You can't, the video is still HDR10.

Okay, so that means at the moment it is not possible to create a backup of a Dolby Vision UHD BD to play on AppleTV with Dolby Vision, correct.

Thanks and regards

Following up on this, I think this is correct but trying to figure out why this is the case? It's not the color space conversion, but for some reason the RPU can't be created? Why can't the RPU from a profile 8/7 be put on a profile 5 stream? Does it changed based on the color space or something? @yusescope said something about it here but I don't fully understand why - viewtopic.php?style=6&f=12&t=18602&start=2445#p90215

[niteflyr]

You're trying to trick Infuse to think the file is profile 5 when it's not.
The Apple TV only supports profile 5 and profile 8.4, which are not HDR10.

Therefore you are saying, that this has somehow tricked Media Info into reporting this as a DV profile 5 video, but not really. Infuse knows better? Is there anyway possible to get an MKV DV rip, to profile 5 to play on ATV4K via Infuse?

[quietvoid]

Following up on this, I think this is correct but trying to figure out why this is the case? It's not the color space conversion, but for some reason the RPU can't be created? Why can't the RPU from a profile 8/7 be put on a profile 5 stream? Does it changed based on the color space or something? @yusescope said something about it here but I don't fully understand why - viewtopic.php?style=6&f=12&t=18602&start=2445#p90215

When encoding profile 5, the video is encoded with a different colorspace, and is also reshaped from PQ to another custom transfer function.
This reshaping step generates metadata that is specific to that scene/frame.

Without both the original IPT colorspace video AND proper reshaping metadata, there is no way to have a correct profile 5 file.
If you use a different RPU from the one made specifically for the profile 5 video, it would not look correct.

Therefore you are saying, that this has somehow tricked Media Info into reporting this as a DV profile 5 video, but not really. Infuse knows better? Is there anyway possible to get an MKV DV rip, to profile 5 to play on ATV4K via Infuse?

What you did is to remux the video into MP4, and the container tells Infuse "this here file should be profile 5".
However the actual video remains unchanged, and is still HDR10.

I don't know how Infuse sees it, but the actual device is the one ignoring the metadata.
There's no way as of today to convert it to profile 5.

Just play it as HDR10 or use another playback device which supports PQ based Dolby Vision such as profile 7 or 8.1.

[Ride_UL]

process:

Code: Select all

# run madvr madmeasure on the mkv file
# generate RPU from madmeasure bin file
dovi_tool.exe generate -j generator_madvr.json --madvr-file l_0201.bin -o RPU_from_madVR.bin
# extract hevc video and audio with mkvextract
# inject the generated RPU into stream
dovi_tool.exe inject-rpu -i video.hevc --rpu-in RPU_from_madVR.bin -o injected_output.hevc
# mux together with tsmuxer

I'm was just trying to convert a HDR10 movie to DV P6 but got stuck with Step 2
Downloaded madVR, installed it & LAVfilters, copied madMeasureHDR to the madVR installation folder and got the .measurements file by running the mkv file through madMeasureHDR
Can you help me with the madmeasure bin file, how we can generate it?
Sorry, if i sound too noob
@@quietvoid

[chros]

process:

Code: Select all

# run madvr madmeasure on the mkv file
# generate RPU from madmeasure bin file
dovi_tool.exe generate -j generator_madvr.json --madvr-file l_0201.bin -o RPU_from_madVR.bin
# extract hevc video and audio with mkvextract
# inject the generated RPU into stream
dovi_tool.exe inject-rpu -i video.hevc --rpu-in RPU_from_madVR.bin -o injected_output.hevc
# mux together with tsmuxer

I'm was just trying to convert a HDR10 movie to DV P6 but got stuck with Step 2
Downloaded madVR, installed it & LAVfilters, copied madMeasureHDR to the madVR installation folder and got the .measurements file by running the mkv file through madMeasureHDR
Can you help me with the madmeasure bin file, how we can generate it?
Sorry, if i sound too noob
@@quietvoid

That *. measure* file is the bin (binary) file, I just renamed it to *. bin

[chros]

Following up on this, I think this is correct but trying to figure out why this is the case? It's not the color space conversion, but for some reason the RPU can't be created? Why can't the RPU from a profile 8/7 be put on a profile 5 stream? Does it changed based on the color space or something? @yusescope said something about it here but I don't fully understand why - viewtopic.php?style=6&f=12&t=18602&start=2445#p90215

When encoding profile 5, the video is encoded with a different colorspace, and is also reshaped from PQ to another custom transfer function.
This reshaping step generates metadata that is specific to that scene/frame.

Without both the original IPT colorspace video AND proper reshaping metadata, there is no way to have a correct profile 5 file.
If you use a different RPU from the one made specifically for the profile 5 video, it would not look correct.

That's interesting, I didn't know about reshaping, thanks.
So, does dovi_tool take care of reshaping when a P5 RPU is converted into P8?