I had to copy paste the url into a new tab to be able to download, and the browser still complains due to http. Or you can use wget or similar. Clicking the link did not work, maybe it is some kind of user protection so they don’t download malware by accident.
Other way around. Select everything.
You are right. After selecting everything, the file plays normally.
Thank you!!!
1 Like
Ok just finished scrolling through thread…it appears August 2024 was the last -no version and I should probably just stick with -ng for all the fixes since then?
I did try the most recent ng from December, I had thought no steps were needed at this point beyond just doing the update from a clean Omega ng? Dolbyvision works but it freezes every few seconds.
Yes
Weren’t meant to be… - as discovered in the last few posts above the problem you are describing can happen when CE plays a video at a non-native framerate. For some reason (presuming that there is one…) that is the default behaviour of CE.
As in the last few posts, workaround is to enable the CE whitelist option for all framerate and resolution options to get the video played back at the native framerate.
2 Likes
Yeah, I did that. Still freezes every few seconds in all DV regardless of framerate. Also audio is out of sync for all videos, DV or not. I can upload a log if you want but otherwise I’ll just wait for your next update. Thanks for working on this.
I had this problem too previously, after investigating it was actually lack of HDMI cable bandwidth, it can be identified by trying to switch resolution to 4k, refresh rate 60, in kodi setings / system / display, and it was several time blackout even on menu (not playing anything).
Some dolby vision media format can push up to 4k 10bit RGB
Changing the cable to higher spec solves this.
For audio out of sync problem, I just set audio offset to be ahead 0.200ms for every video playback.
Now I can use my old N2 to playback tv-led Dolby Vision media format 
Thanks for doppingkoala to make this happen!
This build has the fixed 4-frame audio delay present in the official builds removed - no other differences in audio. As said be others, just adjust a global offset as needed to suit your setup.
For the DV issues, have suspicions of what the problem may be, do
echo 2 > /sys/module/amvideo/parameters/dv_injection_log_level
and then give a dmesg log with DV running. Is it a problem for all files or just some? Also trying a 1080p 23.9…fps DV file would be a good test.
@doppingkoala , I am trying to change the DV RPU before it is processed by the SoC, since you did work on this topic what would be the best place to make those changes? Also, is there a Dolby document that outlines the physical structure of the RPU so one knows what bytes to change for what portions of the RPU? Thank you.
Thank you, I will try to check this just as soon as I figure out how to send that command, do I do that over SSH? Sorry!
Yes it’s on every DV file I’ve tried, I assume some must be 23.97 but I haven’t verified.
I haven’t had any audio sync issues with any Coreelec since Matrix at least except that I think Nexus would be out of sync after pausing and resuming. On Matrix and Omega no issues, so it’s odd I have issues with your build.
Re: The cable, it’s a 48gbps cable and has no problem with HDR10 or HDR10+ in regular CE.
Simplest place may where the existing rpu conversion by libdovi happens, xbmc/xbmc/utils/BitstreamConverter.cpp at f1c2c0f8638cf4931b581fd75bbb73df87585af1 · CoreELEC/xbmc · GitHub, and trying to get libdovi to handle all the encoding etc. The best documentation for the format at that stage is probably the dovi_tool source code…
Be aware though that the official CE code / dovi.ko seems to make modifications to the RPU after that though (i.e. removed the L5 (probably for laziness) and clipping other values for who knows why).
The format of the RPU (the part that actually gets transmitted over the hdmi) is slightly different. See Add feature to write display management metadata suited for tv-led DV. · Issue #303 · quietvoid/dovi_tool · GitHub for a discussion - very similar format, m ain difference is standard types.
Going back to the linux side of the code, it appears this format is what comes out of dovi.ko and get programmed into registers. You might be able to find somewhere in amdolby_vision.c (in the linux code) to intercept and modify the metadata to prevent any unwanted changes being made.
1 Like
yes coreelec:ssh [CoreELEC Wiki]
As long as when set to 12-bit 422 output (any format HDR10, etc), there are no problems it should be good.
Don’t have overscan or something similiar set on either CE or the TV? What device are you using?
No overscan but I am using Kodi’s zoom and vertical shift in the Video OSD - I have to, because I am using a scope screen with a projector. Could that be the issue?
Sorry I have not had a chance yet to try your suggestions, I will this weekend.
Edit - Ok I would have sworn on my life the freezing happened with every video but either I was crazy or some setting I changed has changed that. In some quick tests just now only one movie had the freezes. I didn’t have playlists set up on this install to show my the movies I have with DV so I will check every DV movie after doing that and let you know findings.
Zoom and Vertical Shift worked normally and had no effect on the freezing but in the DV video, the area I had shifted had a grey overlay. In other words I am using Vertical Shift in the OSD for shifting scope movies to the top of the frame, because of the way my screen and projector are positioned; the exact area I have shifted the image up is overlaid with a transparent grey overlay (or maybe the video image is transparently overlaid over black).
I did not have my laptop so have not done the SSH yet. I should be able to report back tonight.
Edit 2 - tested all DV videos I have, now almost none INCLUDING the original did not freeze. But one or two that did, it was 30 seconds or more between freezes so I may not have watched everything uninterrupted long enough to know for sure.
I did the SSH but didn’t understand the second part "and then give a dmesg log ", I have no idea what that is.
Regarding the transparent overlay where I have shifted the image, even more oddly, if I skip ahead or back, or pause and then resume, the overlay is gone for the first couple seconds, with everything rendering correctly, and then it pops back in.
Also iirc the “disable gui scaling” is not necessary anymore, but either way, I don’t see that option anywhere. I have settings on Expert, I don’t see that setting under Interface, System, System>Coreelec, or Coreelec.
Edit 3 - after comparing to native Kodi and Plex apps on the projector, Coreelec on Odroid’s DV displays differently, elevated brightness/blacks in comparison. And in Black Doves e1 at 11 minutes on Coreelec, everything is crazy blown out with bad colors, also Blade 2 opening has weird extreme brightness and color shifts happening.
dmesg | paste
and provide the link. How to post debug logs
That would be when the L5 trims is enabled a few seconds after using the gui. The shifting has probably messed where the L5 trims should be, can disable all L5 trims with
echo 0 > /sys/module/amvideo/parameters/L5_adjust_mode
but the metadata that is embedded may be visible, can also try
echo 2 > /sys/module/amvideo/parameters/L5_adjust_mode
which sets the L5 trim to only hide the metadata
It’s not necessary to set - because I hardcoded it to the required value and hide the option.
First I’ve heard of anything looking different than it is meant to, samples of the files please at those spots. Assuming that they are not P5 files, which isn’t supported. Yet…
1 Like
Ah, thank you! That probably describes and diagnoses all my issues. Will input.showplayerprocessinfo in Kodi or mediainfo in MPC-HC tell me if these are P5? I’m not exactly sure what I’m looking for. I’ll try to cut samples later.
I tried the echo commands you mentioned for L5 trims (I have no idea what that is) and both said “no such file or directory”. I copied so it was not a typo.
Was a typo on my end, I’ve updated the commands.
In MPC-HC, properties, then the mediainfo tab it says the profile, i.e., Dolby Vision, Version 1.0, Profile 5
Ok, thanks. All the videos I came across with elevated black level and/or sometimes way blown out highlights were Profile 5. It’s odd though because sometimes – and in some cases for seemingly most of the runtime – those videos look correct, which seems weird if P5 is unsupported entirely. Is P5 something that will ever be supported?
This command:
echo 0 > /sys/module/amvideo/parameters/L5_adjust_mode
…fixed the overlay issue. But am I losing anything as a result? And can I set this to be permanent so I don’t need to SSH on every reboot?
Thank you for all your work.
P5 is currently unsupported because there is a step required reshaping which isn’t implemented. Without it, p5 video will look anywhere from slightly wrong to not even close depending on how much reshaping should be happening.
Might implemented at some point, seems only the luma channel has a nonlinear reshaping, while the two chroma channels are also a linear reshaping. So should be able to copy from osmc how to use a lut to implemented the reshaping.
Will get raised black levels in the letterboxed area of videos if the L2/L8 offset metadata have values above 2048 edit: been corrected to 2100. Shouldn’t cause any issues for the rest of the image.
Create a autostart.sh (should be able to find an example somewhere else on the forum) that contains that command. Will then run it on startup.
1 Like
Over 2100(0.0025) and only the offset metadata can raise the letterbox. Value between 2048-2100 is fine.
1 Like