Dolby Vision now possible through MP4 Mux.

[FubbAyH]

That's a great sample @quietvoid. It's very interesting to see examples of all the DV adjustments, because until now I've always been a little bit vague about exactly what the DV metadata can do.

[NiCE77]

Would you be able to try one of the titles where the FEL is obvious (e.g. Power Rangers or Total Recall) to see if it is being used?

that's because I did those samples with tsmuxer and it breaks something in the RPU when you split the file. I didn't know about that back then.
As @FubbAyH said, the ending credits of Power Ranger is a better way to verify if FEL is processed.

The credits are grey like HDR10, so nothing new.

And what about the Fire TV Cube (2019)? The Amlogic S922 SoC is able to decoding FEL.

[quietvoid]

And what about the Fire TV Cube (2019)? The Amlogic S922 SoC is able to decoding FEL.

I don't know, I don't own a FireTV Cube.

[ragico]

@quietvoid

Thanks for your Great work on Dovi.
Have you compiled an update Kodi version for the Firestick 4k (original not the Max)?
I am using the version available in Fandango's Matrix 19 Final

[juzer7]

Guys, question.

I'm re-encoding some of my UHD Remuxes. I wanto to inject then RPU into re-encoded BL.
This way I can easily create MKV files with Dolby Vision Profile 8. Playing flawlessly on my Shield 2019 Pro.

But what if I wanted to create a file that I could play directly on different TVs? I just used mp4muxer to create DoVi Profile 8 mp4. However it plays well on my Shield but not on my LG OLED B9. (which I did not expcted as this TV is able to play MP4 Profile 7)

So what container and DoVi Profile should I choose if I want to create a file being able to be playd directly on TVs? At leat on LG OLED we are using in our family?
MP4? TS? M2TS? What profile?
I want this file to be able to be played on TV, Shield and Android mobile devices. If there is no DoVi compatibility then it would be good if the file is played as HDR. That's why I think the only format BL+RPU with HDR compatibility is Profile 8?

Maybe I can mux them into Profile 7 with some "fake" EL layer? Profile 7 MP4s play fine on my LG OLED and Android mobile devices.

Thx for help.

[quietvoid]

Have you compiled an update Kodi version for the Firestick 4k (original not the Max)?
I am using the version available in Fandango's Matrix 19 Final

I build my own but it's running Kodi 20 Nexus, and doesn't include all binary addons.
You can find it here: https://mega.nz/file/4BVTTAoI#KBpPwfQZ1 ... cjlh62Bh-s
The code branch is this https://github.com/quietvoid/xbmc/tree/ ... oska_build

I think Maven's builds might be better for you though, from here: https://www.kodinerds.net/index.php/Thr ... ür-Android
Both are probably a different package name.

[ragico]

Thanks
I downloaded your Nexus version but have problems for sideloading in the Firestick. Have you any suggestion?

[quietvoid]

Thanks
I downloaded your Nexus version but have problems for sideloading in the Firestick. Have you any suggestion?

Not sure I can help you with that.
I always install mine through ADB, like this:

Code: Select all

adb install -r kodi-20-Nexus-dovi-armeabi-v7a-release-2021-10-07.apk

The -r flag is to overwrite an existing install, I think.

[juzer7]

I want this file to be able to be played on TV, Shield and Android mobile devices. If there is no DoVi compatibility then it would be good if the file is played as HDR. That's why I think the only format BL+RPU with HDR compatibility is Profile 8?

Ok. So I tried
mp4muxer --overwrite --dv-profile 5
and the file reporst as
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2086, HDR10 compatible

MP4 works perfectly on LG OLED and Shield 2019 Pro.

If I turn off DoVi in my Shield the file plays as HDR. I though Profile 8 is not HDR compatible? Anyway. This is exactly what I wanted.

Question 1:
What other TVs/sticks will I be albe to play this file on as Dolby Vision? Fire Stick 4K? Sony TV?

Question 2:
Is there any mobile device (Android, iOS) capable of displaying mp4 DoVi Profile 5 as Dolby Vision?

Cheers

[ragico]

Thanks @quietvoid

Please can you give a more detailed step by step guide on how to use it?
Sorry for my ignorance, I never heard of adb and dont know what to do.
Thanks.

[quietvoid]

Thanks @quietvoid

Please can you give a more detailed step by step guide on how to use it?
Sorry for my ignorance, I never heard of adb and dont know what to do.
Thanks.

The basics of it are to get the tools from here: https://developer.android.com/studio/re ... form-tools
You then need to enable the ADB debugging on the device, it's in the developer options.
Then you can connect with adb by command line with adb connect IP:port.
And then you should be able to install the app.

There are many tutorials on the usage of ADB.

[chros]

I build my own but it's running Kodi 20 Nexus, and doesn't include all binary addons.
You can find it here: https://mega.nz/file/4BVTTAoI#KBpPwfQZ1 ... cjlh62Bh-s
The code branch is this https://github.com/quietvoid/xbmc/tree/ ... oska_build

Thanks for the new build!
(Although Kodi is unusable for me on Firestick4k (ethernet cable, not wifi) for whatever reason: low read rate ... message, and it just stalls for a long time...)

Please can you give a more detailed step by step guide on how to use it?
Sorry for my ignorance, I never heard of adb and dont know what to do.

I just upgraded his build with adbLink easily, just installing the new apk again.

[ragico]

@chros
Many thanks it was easy as you said.

[chros]

Anyways, it made me create a cropped test sample for the important metadata: https://mega.nz/file/8YsRRKJa#_g_vX2voc ... raveYPpiIA

That's a great sample @quietvoid. It's very interesting to see examples of all the DV adjustments, because until now I've always been a little bit vague about exactly what the DV metadata can do.

Indeed, really nice, thanks! Now we could see L2 metadata in action!

interesting thanks... will try on my x700.
that sample has very small black bars though

Yeah, I'm not sure if I'll bother switching to the 2018 model though. I only noticed the grey bars with fades to black.

haha, trust me you will.
Having this exact problem with my x700, I just can't stand the grey black bars(especially the 1600px content). I even prefer my Shield with the red push for p8 cropped content(no red push with p5).

Tried it on Oppo, and yes, grey bars are there.
The interesting part is that how grey it is depends on the metadata! E.g. from the previously linked Dolby manual (thanks for thjis for you RESET and Mannix):
"... Blu-ray players ... Due to this implementation on these devices, any positive lift applied to Dolby Vision content during the “trim pass,” will raise the black levels in the letterbox/blanking areas of the image and can become distracting to the end user. Dolby recommends a maximum positive lift value of 0.025 while doing the trims on letterboxed content during the Dolby Vision content creation process."

Edit: what happens with the "min_pq" L1 metadata during madmeasure2RPU generation? Will it be always 0? (I don't think that madvr's bin file has any info about it.)

min_pq is always set to 0. This is the same behavior as the HDR10+ derived generation.

Thanks, now that's interesting. Maybe we can ask mashdi to provide this value as well in the measurement file.
What do you think what would happen if it's not 0 during tonemapping? I mean what's the effect of this value?

Does anyone compared the result this type of metadata RPU (from madvr) vs static metadata RPU (1 for all frames), if so is there any difference?
Reset, Mannix?

[Manixx2020beyound]

Anyways, it made me create a cropped test sample for the important metadata: https://mega.nz/file/8YsRRKJa#_g_vX2voc ... raveYPpiIA

That's a great sample @quietvoid. It's very interesting to see examples of all the DV adjustments, because until now I've always been a little bit vague about exactly what the DV metadata can do.

Indeed, really nice, thanks! Now we could see L2 metadata in action!

interesting thanks... will try on my x700.
that sample has very small black bars though

Yeah, I'm not sure if I'll bother switching to the 2018 model though. I only noticed the grey bars with fades to black.

haha, trust me you will.
Having this exact problem with my x700, I just can't stand the grey black bars(especially the 1600px content). I even prefer my Shield with the red push for p8 cropped content(no red push with p5).

Tried it on Oppo, and yes, grey bars are there.
The interesting part is that how grey it is depends on the metadata! E.g. from the previously linked Dolby manual (thanks for thjis for you RESET and Mannix):
"... Blu-ray players ... Due to this implementation on these devices, any positive lift applied to Dolby Vision content during the “trim pass,” will raise the black levels in the letterbox/blanking areas of the image and can become distracting to the end user. Dolby recommends a maximum positive lift value of 0.025 while doing the trims on letterboxed content during the Dolby Vision content creation process."

Edit: what happens with the "min_pq" L1 metadata during madmeasure2RPU generation? Will it be always 0? (I don't think that madvr's bin file has any info about it.)

min_pq is always set to 0. This is the same behavior as the HDR10+ derived generation.

Thanks, now that's interesting. Maybe we can ask mashdi to provide this value as well in the measurement file.
What do you think what would happen if it's not 0 during tonemapping? I mean what's the effect of this value?

Does anyone compared the result this type of metadata RPU (from madvr) vs static metadata RPU (1 for all frames), if so is there any difference?
Reset, Mannix?

Min pq is mostly set to 0 on hdr10plus, & produces the same result on hdr10 plus to dv rpu.
There should definitely be a difference per frame vs 1 for all frames.
But on true min pq value dv dynamic meta it varies more often
If mad vr handles scenes changes the same way as dv, the dynamic meta produced should be very close I would assume.