You are saying you’re seeing scan lines and/or the DV layer “having an offset from the base layer” if I read it correctly? That must be something in your setup then, because for most of us, the Ugoos plays P7 FEL MKVs just fine without these issues.
What’s your setup exactly? Do you have an A/V receiver in your chain? Did you try a different HDMI cable? I cannot imagine this being a bug in CE, or it would have been reported much earlier already.
Something to that effect yes, I think the photo in CE-NG Dolby Vision for G12 SOCs (u22xj, am6+, firetv cube) - #154 by egeedot does a better job in explaining what the issue could be
There isn’t anything unique to my setup that I can think of, my UGOOS is plugged in directly into TV via HDMI port 1, my TV is an LG OLED65C97LA, I have true HD color enabled and there isn’t any A/V receiver in the chain (I have an audio setup using eARC but that shouldn’t be effecting anything).
I am playing movies using PlexMod4Kodi, I also tried using SMB directly in Kodi but that didn’t make any difference. Is there anything else I should be looking out for?
EDIT: I also tried swapping out HDMI cables (no difference, also not expecting any here). Ontop of this I played the BL_EL.mp4 file and its also having the same scan line issues (further confirming its not how I am ripping the Blu Rays).
Try different HDMI port on the TV with a different cable…
Also no difference, I switched HDMI ports 1 and 3 (2 I need to use for my audio setup because its the only port with eARC enabled)
Just to clarify, there is only one version of dovi.ko and it is still neccessary for latest nightly Kodi?
It seems like I am getting the exact same issue that is being described here (Dolby Vision now possible through MP4 Mux. - Page 340 - www.makemkv.com) with the vertical lines. From reading that thread it seems like this issue is not uncommon.
I just ordered a Belkin High Quality HDMI cable certified to work with Dolby Vision just incase its an issue with all of my current cables.
Yes, dovi.ko is still needed.
The cropping issue could also be in the skin you’re using. Did you try switching to the default Estuary skin?
Also, did you try switching DV output to player-led instead of TV-led, just to test?
I am using the default kodi skin
Is this a kodi or a TV setting?
So I found the setting (its in Kodi → Settings → CoreELEC) and indeed setting it to player-led solved the issue, which I guess means that my TV cannot handle the FEL profile 7 Dolby Vision layer.
For the dev’s out there, maybe it makes sense to make the Player vs TV led setting specific based on what Dolby Vision profile is being played? I would gather that a lot of TV’s cannot handle the FEL profile 7 where as other profiles (like the ones from Disney+ or Netflix) can be handled without issues.
interesting, to my understanding there shouldn’t be that much difference between P7 FEL and MEL in the TV-led mode as FEL layer should be applied by the player in both modes (and TV just handles the RPU processing). Have you seen similar reports around here?
Strange… But I don’t think the issue is with the DV profile. The make and type of TV determines if TV-led is supported or not. With TV-led, the media player device sends an 8-bit RGB tunneled signal to the TV and the TV handles the DV processing. With player-led, the media player handles the DV processing and sends a 12-bit YCbCr 422 signal to the TV. But in both cases the FEL layer has already been processed by the media player.
I’m not sure if TV-led uses more HDMI bandwidth than player-led? In that case, your cable might still be the culprit.
New cable is arriving tomorrow so I will test it then!
Wouldn’t it be the other way around, i.e. player led sends more data than TV led since player led is 12-bit YCbCr 422?
So the issue is not the cable, I got a proper expensive cable that has been tested/certified to work with Dolby Vision by HDMI forum and there isn’t any difference.
Hmm ok. Can you find somewhere in your TV’s specs if it supports TV-led DV or if support is limited to player-led DV (LLDV) only?
It doesn’t really make sense though, because you said other DV profiles besides P7 FEL do work with TV-led enabled right?
If you have a Sony TV, try HDMI 1 and 2 instead:
Check that HDMI Enhanced (Sony) or HDMI Deep Color (LG) is enabled on that HDMI port.
So the context of me saying this is that I am able to watch Dolby Vision via Netflix without any issues and I assume that Netflix is not using P7 FEL, and that its also TV led.
Or in other words, I am only having issues with ripped Blu Ray Dolby vision DVD’s (and yes that includes the good remux’es).
Got DV FEL working on DV licensed s905x4 boxes. Updated the OP with a dovi.ko for that SOC. This requires using CE-NG on the s905x4.
I only tested this on one of the SEI s905x4 clones, so report your success or failure, and which device you tried.
I don’t think there’s a link in post one. Can you recheck. I can’t wait to test!
Sorry, fixed
Which dtb did you use? I couldn’t find the SEI one in the -ng nightly.
CE-NG was never fully developed for the s905x4, although everything seemed to work fine when I tested any videos I threw at it.
Use one of the generic s905x4 dtb’s that corresponds to your box’s amount of RAM and ethernet. If the device has 4GB RAM + 1Gbit ethernet, use sc2_s905x4_4g_1gbit.dtb.
Extremely exciting. Now there is triple the number of FEL capable devices just like that.
This will breathe new life into many devices and make many more competitive and appealing.
Does S905X4 support CM4.0 or is it limited to 2.7 similar to S905X2?
About | FAQ | Terms of Service | Privacy Policy | Legal Notice
