Dolby Vision for Minix U22X-J (Max) and Ugoos AM6+

Yes the RPU is the dynamic meta data - this allows better (dynamic) tone mapping to the capabilities of the display device (TV) on a frame by frame or scene by scene basis rather than fixed for the complete film to one (static) tone mapping.

Note: This is similar though not the same as the capabilities of the rival standard: HDR10+ Metadata.

The RPU in your P8 encodes - presuming the P8 is sourced from a P7 - will be identical to the P7.

As you have seen well produced HDR10 will look good already, to a point it may not be obvious the difference - if you want to see the difference more clearly I would say get the Spears & Munsil Benchmark Discs to compare, if there is no difference that you like then it is all really moot - just go with what you have.

If though you then want to have P7 FEL where the RPU is passed to and processed at the TV, then only the devices here do that (outside of BluRay Players) and are -ng devices.

Bottom line it needs a combination of:

  • Software
    OpenSource drivers available for the hardware (amlogic linux)
    DoVi linux module available
    CoreELEC to bring it all together with a Kodi front end and fix issues on the OpenSource side.

  • Hardware
    Two HEVC hardware decoders
    DoVi Licence enabled

For all this to work.

Even given all the right ingredients it does not just then happen by magic it needs lots of effort to then make it all work together; maybe tomorrow a -ne device will be ready that does that and the software all ironed out - maybe that happens in another 6 months, I am not part of the CoreELEC team but the way I see it is this is a open source project - there is no planned product road map to be releasing such a device, it arrives when it does when all the pre-requisites are ready and the software has been built to make it all work together.


My advice is - if sticking with P8 then you have a lot of choice for the player, it really depends if you place any value on P7 FEL.

FYI - there are P7 FEL out there with very high bitrates in the FEL layer talking up a large proportion of the UHD 100 GB available, not all the benefit of that can be unlocked with current displays but there certainly are current benefits and as displays evolve more to come.

1 Like

Thank you for the compehensive answer, highly appreciated!

One more question regarding performance, I asked earlier about 4K AV1 software decoding, which was not feasible with these boxes. Has there been any tests with 1440p (2560x1440)? In AV1, I guess tiling will also help with multithreaded decoding.

@ragico

Created another test build - based on latest CE21

new parameter to clear out the colorimetry flag for DoVi tv-led.

Edit:
echo Y > /sys/module/hdmitx20/parameters/dovi_tv_led_no_colorimetry

Edit:
echo N > /sys/module/hdmitx20/parameters/dovi_tv_led_no_colorimetry

This overrides the existing bt2020 paramerter, can use combinations of both to check all three flag settings:

BT.2020nc
BT.709
(No Flag) - will say Default in Kodi overlay.

1 Like

would it be possible (and hopefully not too much of work) to integrate a menu setting to set this flag fixed (maybe at the same place where the option for player led/tv led is)?

Thank you for this.
I have installed your tar file upon my CE21 latest nightly.
Then I have used both your ssh commands (one at time) and no difference with the CE21 nightly.is observed. BT709 flag is always there in any combinations of your commands. Both Panasonic info and CE21 info show BT709 flag.

Did late last night (my time) and put a typo in the command - try the below (should be parameters with an s)

echo Y > /sys/module/hdmitx20/parameters/dovi_tv_led_no_colorimetry

As well as the screen can also use the following command line to see the current AVI Info Frame settings in detail, along side other Info Frames / Packets:

cat /sys/kernel/debug/amhdmitx/hdmi_pkt

There it will say:
colorimetry: disable

I think it is doable, but not too sure on the benefit, probably not something I will look at unless find myself with lots of free time, and done the other things I want to get done :slight_smile:
Others please feel free to add.

FYI, I will likely submit a PR for the command line parameter to get this into the mainline later on.

it works perfectly. Applying the first command Panasonic info no longer displays BT709, no flag as the ATV 4k and the sony x800m2… The second command gives a lot of info including colorimetry disable. Thank you.
After rebooting the box returns in the previous state and displays again BT709 flag.
May be it is autosuggestion but to my eyes the video looks a little better with no flag status. I believe to my eyes and to my ears too, so I ask you if this change (no flag) can be made permanent and there is no necessity to apply the command every time the box is rebooted.
Many thanks @cpm

1 Like

Would you be able to add equivalent parameters for clearing color depth and chroma subsampling flags?
Ugoos in contrast to x800m2 certainly sends color depth (Sony OSD: Ugoos = 8bit, x800m2 = empty).

Who on ce21 has a bt709 or bt2020 flag on DV, try doing, complete shutdown of tv, receiver or any other device between tv and player. My hdfury unequivocally now shows blank, as does the oppo clone. Some devices remember the last picture mode for DV. For example on the hdfury I found such a defect. If you switch between different edid with DV, it does not switch to the new edid DV data, switching to the edid where DV is removed helps. Then it adequately applies the new edid parameters to the DV. So try complete shutdown of the whole chain from player to TV.

Mine definitely fluctuates. Mine was showing BT. 2020 regardless of whether player led was enabled but then I switched skin and after that it always said 709 until I enabled player led even after restarting the box (but not the TV or AVR)

Tried many times to shutdown everything even unplugging them from the mains. Nothing changes, always info displays BT709. Only wirh the @cpm “tricks” I have no flag.

If you are not aware, you can use autostart.sh to set every time automatically.

Once this is into the nightlies and tested more, then can look to see if there is broad consensus to have a different default for the flag - as above autostart.sh can be used for any other setup.

Maybe some kind dev will also expose on the UI later.

Please can you explain how to use autostart sh? I am a not familiar with these commands. Thank you

Do you have any theory or material indicating the need to change or just like the idea of matching the Sony?

not near the box currently to confirm but iirc this is the same for CoreELEC

Try the below in the autostart.sh file when you create it:

(
 echo Y > /sys/module/hdmitx20/parameters/dovi_tv_led_no_colorimetry
)&

2nd option: only the idea of matching the Sony.

Thank you very much. Followed yr instructions and it works as intented. No flag of any type now, even after box reboot. Great for me.

TIL: About the DDVT Tool. It bundles quietvoid’s dovitool and hdr10plus_tool while making it simpler to use. I’ve been mainly running it to convert movies I have with at most HDR10+ to inject a profile 8 DV layer. This pretty slick and I like how I can effectively get the benefits out of HDR10+ only Movies with my TVs that are limited to DV as the only dynamic HDR supported format.

Pretty slick now that in conjunction with FEL playback that I have capabilities that even my Panasonic UB820 player cannot natively do (at least while playing back the disc itself).

There is also this: GitHub - R3S3t9999/DoVi_Scripts: User-friendly / drag & drop scripts to process any HDR / Dolby Vision files and more...

Courtesy of @R3S3T_9999

Edit: This one has two methods of conversion,

Second one is quick and probably the same as ddvt tool, first option seems to be more involved but it reencodes for some reason and it takes a lot of time. (reencoded file isn’t used in the final file) No idea about the differences between two options.

2 Likes