Has anyone used the Tone Map SDR to HDR option?
Option one is better because it uses official Dolby tools and converting HDR10plus to DV is not very accurate because the average_pq metadata is generated quite differently.
1 Like
Yes , but had to disable for now. Wrong colors after dv playback
Looking back at the AVI info captures from @R3S3T_9999 for various devices.
Data manually copied from the images - so hopefully no typo!
You can paste the comma separated list items from below into:
From that these are the differences (ignoring the diff for the checksum):
| x800m2 | ATV | Ugoos | GTV |
|---|---|---|---|
| Scan Information: No Data | Scan Information: Underscanned | Scan Information: No Data | Scan Information: Underscanned |
| Active Format Present: FALSE | Active Format Present: TRUE | Active Format Present: TRUE | Active Format Present: TRUE |
| Colorimetry: No Data | Colorimetry: No Data | Colorimetry: ITU-R 709 | Colorimetry: ITU-R 709 |
| VIC: 0 | VIC: 93 | VIC: 93 | VIC: 93 |
| YCC Quantization Range: Limited Range | YCC Quantization Range: Full Range | YCC Quantization Range: Limited Range | YCC Quantization Range: Limited Range |
The CS was the same: RGB for all devices.
Presuming you are looking at your TV’s information - maybe it is the lack of the VIC or Active Format Present that is meaning it does not show up for the Sony.
Unless someone comes up with a good reason I think should continue to send the VIC, and set the Active Format Present.
Bonus: Also included below are the VSI info captures, all are the same except for the ATV which I presume is because it is sending p5 or p8 (maybe) would need to dig deeper to understand those parameters.
AVI Info Frame:
x800m2: 82:02:0D:3F:00:28:08:00:00:00:00:00:00:00:00:00:00
Ugoos: 82:02:0D:52:10:A8:08:5D:00:00:00:00:00:00:00:00:00
GTV: 82:02:0D:50:12:A8:08:5D:00:00:00:00:00:00:00:00:00
ATV: 82:02:0D:90:12:28:08:5D:40:00:00:00:00:00:00:00:00
x800m2: 82, 02, 0D, 3F, 00, 28, 08, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00
Ugoos: 82, 02, 0D, 52, 10, A8, 08, 5D, 00, 00, 00, 00 ,00 ,00 ,00 ,00, 00
GTV: 82, 02, 0D, 50, 12, A8, 08, 5D, 00, 00, 00, 00, 00, 00, 00, 00, 00
ATV: 82, 02, 0D, 90, 12, 28, 08, 5D, 40, 00, 00, 00 ,00 ,00 ,00 ,00, 00
VSI Info Frame:
x800m2: 81:01:1B:4B:46:D0:00:02:00:00:00:00:00:00:00:00:00:00:00:00:00
Ugoos: 81:01:1B:4B:46:D0:00:02:00:00:00:00:00:00:00:00:00:00:00:00:00
GTV: 81:01:1B:4B:46:D0:00:02:00:00:00:00:00:00:00:00:00:00:00:00:00
ATV: 81:01:18:34:0C:00:20:03:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
EDID wiki with VIC (Video format Identification Code) reference list:
1 Like
Maybe for longer term, but these devices and AMLogic code are also capable of using the DoVi Engine to Tone Map other content - I imagine it would need a fair amount of coding to integrate with the Kodi side.
1 Like
Yes an option like “Always Hdr”(Dolby Vision)? I use this on minix u22-xj max android OS and is basically play everything in dolby vision.
Make no to yes is very bad! It like you up convert a music with low bit rate to high bitrate, make non sense!
Always better to have high quality source material, and just like sound the mastering effort is a very important element.
Would someday like to see the true Digital Master 16 bit RGB TIFF (lossless compression) i.e. the layer above the Mezzanine Master which is used for UHD and Streaming.
And see how that compares - guess would still be waiting for the Displays to catchup :).
Currently thinking about / looking into mxf (cinema content - to see if better for home projection), but maybe UHD grading for high nit TV will be better for home experience.
But for the content we cannot source at high quality - more sophisticated upscaling and AI techniques does some interesting things now (not that the DoVi Engine is that level), some recent work has been really good.
Ultimately I would also view it as choice some will like it better, some less so.
Probably moot anyway for now as effort I think is high to get going.
For DV tonemapping other content, the current best bet is the Zidoo Z9X Pro with VS10. But then you deal with fake TV-led and the VS10 implementation is okay at best.
Does good on mapping colors, but the gamma mapping I think is subpar. Whites and lights are far too bright, almost glowing.
I’m confused, is always hdr(dv) on be put in coreelec menu as an option or not?
I could be mistaking, but I see very little reason to map HDR10+ to DV, since the TV performs tone mapping on HDR10 content anyway. I would hazard a guess that it’ll probably work better and more correctly than doing it that way.
Not so simple as just add an option in a menu!
Yep they market that to the max, but I think the s922x-j also does something similar:
Here it also mentions VS10 in relation to the s912:
The code certainly points that way as well but would need quite a bit of integration to allow tunning of settings and choosing between if going through the DV Engine or not on a content format level.
I just ordered a Ugoos AM6B+, coming from Intel NUC with NVME SSD.
Can anyone advise whether the Ugoos/CoreElec is faster for UI/Kodi library navigation using an SD card or a USB thumb drive (my media files are all on a NAS so it’s really just accessing local cache files)?
Is there any performance benefit in using larger SD card or USB thumb over smaller (e.g. 256GB vs 32GB)? On Intel larger SSDs outperform smaller by a large factor.
Any recommended specific brands/model numbers?
Thanks.
Could you tell me how you check that flag in your Panasonic? I have the HZ1000 and cannot find this option for the life of me.
With series LZ and MZ, Panasonic introduced the feature that long press the info button on the remote diplays on the TV screen the extra infos we are talking about.
1 Like
I just flashed my newly arrived AM6B+ using the above linked cemmc command found in coreelec wiki. Works like a charm and is a lot faster and more reliable than running a whole OS from a USB stick or sd-card.
2 Likes
In my experience, none of the microsd cards I own regardless of performance class (and I do have some rather high speed cards, too that I’ve tried) have been anywhere near comparable performance to installing on eMMC. Also remember: eMMC has wear levelling (not to mention fstrim.timer appears to actually be functional against eMMC). The vast majority of SD cards still lack wear leveling of any kind. It’s nice to have the option to try out a test build without modifying your currently deemed stable build. But I wouldn’t suggest external media booting for a long term installation, personally.
Also run the ceemmc tool to convert to dual boot. DO NOT use the dual boot image that ugoos provides. It only gives about 3GB coreelec storage partition size (vs about 25GB).
@xmlcom you won’t get any benefit whatsoever of an always on DV setting. If anything it’s implemented in certain low end boxes as a workaround to some sort of limitation, and frankly seems usually more of a quick and dirty workaround to otherwise implementing proper adaptive HDR capability. You’re not actually doing true conversion to DV from a lesser HDR format, like you’re probably thinking. If anything it’s basically merely passing the BL in DV, instead of just passing a HDR10 signal as is. I’m sure there’s also a placebo effect as it seems DV has received quite the marketing buzz lately (e.g. streaming services having the audacity to only enabling it on their most expensive service tiers).
2 Likes
That’s not entirely true. If we look at Zidoo or Dune’s VS10 and it’s always on DV setting, playing all content SDR/HDR in DV, in many scenes it looks very nice. Better than source material imo, but obviously not as good as native Dolby Vision when comparing,
My understanding is it’s doing an on-the-fly colorspace conversion and gamma conversion from the SDR Rec709(?) into BT.2020 (?). Whatever it is, I think it looks quite nice on the Zidoo. Especially colors on older SD content like Cheers or DS9 that didn’t have the best source quality to begin with.
Dolby Vision VS12 is already out on the newer S928X-J SOC (Tencent Aurora 5X), and I’m hoping will improve the existing shortcomings on brightness.