Is this dovi.ko file still needed if we are installing the new “CoreELEC-Amlogic-ng.arm-21.0-Omega-Generic.img” on to an Ugoos AM6B+? The changelog is unclear.
Changelog says “Other devices on Amlogic-ng like Ugoos AM6+ or Minix NEO U22-XJ (Max) equiped with S922X-J will support Dolby Vision with profile 7 FEL as well.” but it doesn’t say anything about this dovi.ko file whether it needs it or not. Thanks 
yes, you still need it.
What type of “features” should I be seeing here? Reason being is that I can’t get DV to work with my Ugoos AM6b+ even after two install attempts. And the only thing I see there is one slide bar asking me if I want to disable DV or not. Is this the “features” I should be seeing? Please explain what features I should be seeing… thanks
If I can ascertain if the driver has even “loaded” then perhaps I can troubleshoot further on why I get no DV…
You will not see the option to disable DV if your box couldn’t properly load the DV kernel module.
Use Player led only shows up if your TV reports that it can support it in the EDID it passes along. if you can see the option to disable DV, but not player led, it means your TV claimed it can’t handle it.
If you can’t run DV still. Check to see if your TV is set to standard HDMI, vs. “enhanced” HDMI signal for the specific HDMI input. IIRC at least one of my TVs doesn’t behave properly with DV support when that setting is set to standard instead of enhanced. It will likely vary depending on brand of TV.
Hmmm, oh wow. Thanks for getting me closer to finding the solution to this DV-non playing puzzle.
Okay, so it’s a Sony X85J (in case somebody comes searching) and I got the ugoos plugged into HDMI 4 (HDMI 3 is taken by e-arc to Sony HT-A7000 soundbar). Yes HDMI 4 was on enhanced only so I switched it Enhanced w/ DV and then restarted Kodi and now I got the “Player LED” toggle too. But when I play a DV vid all I get is red & purple splotches even though I do get the DV flag. When I tried toggling the use Player LED to on just to see what would happen, the video is all weird looking plus now again no DV tag on the TV. Swapped out 2.1 HDMI cable with known good 2.1 fiber optic HDMI cable and same thing.
So tried plugging in the ugoos into my Sony HT-A7000 soundbar which has two HDMI inputs. Now I can’t even get any HDR to play nevertheless DV content to play, all I get is no signal from the soundbar even though I tried its various HDMI settings also (enhanced, super enhanced etc). I had used these same 2.1 HDMI cables with my RTX3070 to play HDR content on the TV before so I know they are good. I have no idea why this is happening with this top of the line expensive soundbar.
Regarding the purple/red splotches into HDMI 4 of the X85J TV, is there any other setting in Kodi I can try to make DV finally work? Or is this a brand new $200 paperweight which is incompatible with Sony products? Darn, I am really trying to make this work
I suspect I know what is going on. There appears to be 3 ways of doing tv-led DV. Taking a guess at the setups people are likely to have, only one of these may have been tested so far.
With the HDMI port 4 set to enhanced w/ DV post the outputs of cat /sys/class/amhdmitx/amhdmitx0/dv_cap and cat /sys/devices/virtual/amhdmitx/amhdmitx0/config when you are playing a DV video in tv-led mode and getting the weird colors. Then change the setting of the port back to only enhanced, and post the output of cat /sys/class/amhdmitx/amhdmitx0/dv_cap again.
Now move the ugoos to HDMI port 1 or 2 - I suspect this will make tv-led DV work for you. In any case, again post the output of cat /sys/class/amhdmitx/amhdmitx0/dv_cap, and if tv-led DV works, the output of cat /sys/devices/virtual/amhdmitx/amhdmitx0/config when playing a video in tv-led mode.
For what it’s worth. I plugged my Ugoos into HDMI 2 set that to enhanced and it’s just working. I also have an X85J TV and tbf the HDMI 3 and 4 ports are really weird. Probably because they are the 120hz ports and for some reason Sony had to treat them differently… Maybe try 2 or 1if you can?
As for my nakamichi sound bar for the Sony A8H TV, if I plug into HDMI 4 it goes crazy in 4K 60hz (ie 600mhz HDMI signal). But flawless on HDMI 3.
AV equipment be weird sometimes…
I think it is more that ports 3 and 4 are hdmi 2.1 ports on the X85J - the others are not.
From what I’ve gathered, in hdmi 2.1 tv-led dolby vision doesn’t actually do the whole stuff around with 8 bit RGB tunnelling and embedding metadata into LSB’s of the chroma channels. Instead the 12 bit 4:2:2 is sent normally, and the metadata is sent separately as extended metadata packets (EMP). Seems to be the seem concept as how hdr10+ is transmitted - just Dolby specific packets with a different id and data.
Is it specific to Sony’s implementation of HDMI 2.1?
My LG G2 also has HDMI 2.1 ports where the Ugoos is being used on, but this issue isn’t present.
Doesn’t appear to specific to Sony. See section 6.10 and Annex R of this standard.
Looking at the open source amlogic code, use of this mode still seems to depends upon the TV claiming support in the EDID it sends to the device. Maybe your TV/port mode aren’t claiming support for this type of DV.
Mind running the ssh commands I posted earlier? Might be able to see if this mode works or if you are using the rgb tunnelled mode
cat /sys/class/amhdmitx/amhdmitx0/dv_cap
DolbyVision RX support list:
VSVDB Version: V2
2160p60hz: 1
Support mode:
DV_RGB_444_8BIT
LL_YCbCr_422_12BIT
IEEEOUI: 0x00d046
EMP: 0
VSVDB: eb0146d000480a7e86607694
and
cat /sys/devices/virtual/amhdmitx/amhdmitx0/config
cur_VIC: 352
cur_video_param->VIC=352
VIC: 352 3840x2160p50hz
Colour depth: 12-bit
Colourspace: RGB
Colour range: full
EOTF: DV-Std
YCC colour range: limited
Colourimetry: BT.2020nc
PLL clock: 0xdb1004b9, Vid clock div 0x000a66cc
audio config: on
audio on/off: on
audio source: SPDIF
audio type: Dobly Digital+
audio channel num: 2 channels
audio sample rate: 192kHz
audio sample size: 16bit
3D config: off
Doesn’t look like your tv is claiming to support the yuv422 12-bit mode - would also list DV_YCbCr_422_12BIT and EMP: 1 in that case. Looks like you are using a tunnelled mode with the metadata embedded. Does your TV have different modes for the HDMI port you can try?
edit: @liquidion what do you have HDMI Deep Colour set to on the TV? Looks like that needs to be set to 4K for YCbCr 4:2:2
I would have thought this would be 8-bit. I’m lost again …
I just got my ugoos am6b plus . And got CE 21.0 running.
I confirmed I see the disable Dolby vision option and player led option in the coreelec settings.
I am playing back local UHD ISO files, but all DV titles are in HDR10.
LG C1, Dolby vision works from other devices, nvidia shield, Oppo 203.
I tried player led, no change
Any ideas?
HDMI Deep Color is already set to 4K. I’ve confirmed before the test.
Hmm, maybe DV in this mode another one of the “optional” parts of hdmi 2.1 that leave everyone with no idea what devices actually support
So I can playback mkv files with DV. Is there any support for ISO or MSTS and DV?
The 12 bit I think is occurring because of timing when changing modes at the start of playing content:
this is sometimes called before the hdmi is setup correctly for the content - in the case of DoVi a call to:
So the wrong bit depth is set as it does not yet know it is going to be tv-led DoVi.
There are various approaches around to trying to solve this out there, but for me fundamentally it is a timing issue / race condition, and likely the reason we see content streaming from different sources usb/smb/http that can behave differently as the arrival of content and discovery of what that content is can vary a little timing wise, a faster source looks to be better, in this case - resulting in the hdmitx_set_vsif_pkt call done in time.
The underlying reason we see this issue in Kodi (and probably not in mbox) is maybe: Kodi wants to control the setup and “change” into the correct mode when firing up content to play (a reasonable thing to do) whilst I think mbox (Andorid) would have just set the mode once in the OS / Boot (e.g. everything in DoVi - and this issue would not occur - less switching)
Why not? Don’t we already know what that a file is DV from it’s file info and if coreelec is set to use tv-led DV?
As I am sure you picked up - the call to hdmitx_set_vsif_pkt is what sets the “hdmi config” up correctly for set_display_mode_auto to then recognise it is DV tv-led and then switch into 8bit RGB.
Yes the type is known up front in kodi, but hdmitx_set_vsif_pkt is being done from the amlogic side not from kodi as I recall, so likley the race condition is an outcome from the mix of kodi and amlogic.
Can see from the logs when they happen in the wrong order that leads to the 12 bit issue - it cleared up for me a few builds back (been 8 bit solid on dv content - served from local 1GB SMB) so not looked into it deeper.
I have full bluray menu support with the ISO files. But DV isn’t being triggered.
Help?
About | FAQ | Terms of Service | Privacy Policy | Legal Notice