EDID Override - Injecting a Dolby VSVDB Block

@Portisch why is this not in the upstream coreelec build yet? I’d like to get rid of my Dr. HDMI 4K.

Maybe because they already have enough of development tasks across multiple branches.
Also they wouldn’t just blindly merge cpm’s code, they would have to review and rework it, if needed. Also asking it in this manner (don’t know if it’s intentional or not) won’t help the matter…

5 Likes

This. I also think that the proper way would be that cpm creates pull requests as he sees fit, of course guidance coming from the CE team if any splitting is needed.

Hi, if I have LG OLED C3, do I need any additional settings and is native DV playback still possible? I’m currently only interested in SDR/HDR to DV playback, and DV content as native

Assuming you are using cpm’s latest versions T4 or T4A:

  • Mode: On Demand
  • Type: TV-Led
  • Based on your post that you wanted native DV and SDR/HDR to DV playback : Set everything to “Dolby Vision” except setting “off” for HLG HDR (given an AMLogic bug) and of course Dolby Vision.

This will given you native DV (with FEL if available) for DV content and convert to DV (through VS10 engine) everything else except HLG HDR given AMLogic bug.

Thanks a lot, forgot to mention my player is Ugoos AM6B Plus and yes, I installed T4A version

I’m always amazed at this. Each to their own. But why artificially convert SDR to DV, you’re supposed to watch source material as per production. Just seems silly, and a waste of a good TV. DV/HDR isn’t always better

Who cares… “source material as per production” such a loaded term especially in modern era when TVs themselves have a ton of post-processing: upscaling, various pulldown techniques, DNR, sharpening, super resolution, etc. And hell, most times those enhancements look better than the source material. Not like most blurry 480p sources are the best quality anyway.

Watch what you think looks good, SDR → DV can look pretty fun in some cases. Plus when you’ve rewatched stuff multiple times, changing it up once isn’t going to kill the enjoyment. Not sure how much I care about purity on my Nth rewatch of a show.

4 Likes

Yes, to each their own. That is the beauty of choice. This is all about personal preference. If you do not like using the VS10 engine to convert SDR/HDR10 to DV then don’t but for the folks that do want to convert SDR/HDR10 to DV then that is great also. I have two Ugoos setup in different displays, one without DV conversion and another with DV conversion. In some movies I prefer the setup with conversion and with some movies I prefer the setup without conversion.

There is no right or wrong answer here.

3 Likes

'cause I can do it, just for that fact

I’m the opposite I want 4k hdr to play properly on a 1080p tv until I get a 4k tv.

Will this Version do that

Just to remind you, TVs are UHD, (2 x 1920 x 1080 → 3840 x 2160) and 4k movies have slightly wider, 4096 x 2160, resolution to cover 2 major movie aspect ratios “Flat” and “Scope”

Since I never did this, I am not sure if Ugoos with CE (including cpm’s version) can do this downscaling/transcoding of a video file from 4K DV/HDR to 1080p SDR well (meaning without performance problems). cpm’s version can do the DV/HDR to SDR conversion through the VS10 engine and kodi or plex can transcode/downscale 4K to 1080p. So it is possible but not sure if the Ugoos or your server has the horsepower to do both conversions without performance issues.

I know that a HDFury Diva device can do both conversions very well but it is an expensive device - around five hundred dollars - which at this point you can use that money towards a 4K DV TV.

@cpm
Is this on the fly conversion the same thing as you were trying to achieve to convert hdr10+ to DV

1 Like

Though movies on Blu-ray are encoded at 3840x2160 on to the disc, and most OTT streaming platforms are also 3840x2160 when they stream movies.

If you are working in DI, shooting your own content, or have access to other movie post production areas you’ll find 4096x2160 elements around - but they aren’t widespread in the consumer space. (You’ll find high-quality picture monitors with 4096x2160 panels instead of 3840x2160 too)

Whilst in movie production terms 4K = 4096x2160, and UHD is reserved for 3840x2160 content, in the consumer space the two terms are used interchangeably (i.e. a 4K TV will have a 3840x2160 panel, and a 4K UHD Blu-ray is encoded at 3840x2160)

1 Like

Have not tried this build, but from the description, yes - I think it is the same goal.

What I want to do is convert the HDR10+ metadata in the Prefix SEI NAL to a Dolby Vision Unspecified NAL 62 (RPU) metadata (i.e. replacing the metadata in the HEVC stream) - that would be in the Kodi side, so downstream from that point would see it as DV: for DV-Std, DV-LL, DV-HDR etc.

@doppingkoala I would presume the conversion you are doing is on the linux amlogic side, convert from the pre-existing decoded hdr10+ structure to rpu and from there into your existing pixel encoding via the OSD layer (ultimately having pixels encoded as per DV-Std). Do you have the code up on GitHub? would be very useful to see and validate a few things for me.

From the description there, it seems that it uses the inbuilt dovi tools converter which produces sub-optimal results.

we’re looking forward to seeing ur new update. :+1:

btw, what OS are you using for building (Ununtu 20.04 or 22.04+ or smth else) ?.
It tried on my 22.04 dev vm, but for some reason I get the stupid ‘Incorrect checksum calculated on downloaded file’ for the wireguard package (I’ve seen similar error for a different package on the forum, but the cause was not found and it was not resolved, Build Errors - #14). Thx.

Yes, I’ve done it on the amlogic side - seemed far simpler for me.


Very close, the existing decoded hdr10+ structure wasn’t available where I need it to be. I just copied the structure / decoding code and used it on the sei data that was available.

From there, I just filled in the source pq’s and the L1 data into some DV metadata that had the rest of the data pre-set as it doesn’t change.


Not yet. I’ll copy that could over to my -no build and update my existing (and now quite outdated) repo for that. I’ll let you know when it’s up.

1 Like