it’s ok, it’s running great with slimBOXtv now, btw what kernel version is running on your Android system? I noticed before I flashed slimBOXtv it said 2024 on kernel version, with slimBOXtv it’s 4.9.113 from 2022.
Yeah same kernel on mine
29 posts were split to a new topic: Help, support CPM build
A post was merged into an existing topic: Help, support CPM build
I think I have found a bug.
The setting is working for Dolby Vision and HDR10 content but not for HDR HLG.
I am not sure if this is CoreELEC or Kodi’s problem and where to ask to fix it.
Under Windows HLG content is converted to HDR10 and the setting then works correctly, but the Ugoos sends actual HDR HLG content to my LG OLED and the setting in that case doesn’t work, while it works just fine for HDR10 and DV.
You are sure because this was fixed long ago.
Did you try past nightly?
I am using the latest official release. I tested it back and forth several times with all kinds of DV, HDR and HLG content.
I will give nightlies a try but I was using nightlies before. When you say “long ago” do you have a time in mind, more or less?
But as you did not post any debug log again we can’t help anyway.
I was waiting for feedback, I’ve been a very active Kodi user for almost twenty years, I am kinda aware of what’s needed to debug (but always willing to learn, don’t want to sound snarky or anything). I will provide debug logs, obviously. I just wanted to check if it was something already known.
In any case, I have investigated further, following a look at the code you have provided. I think I have isolated the problem.
There are some HLG files that (correctly) play back as HLG that are not identified as such by, I guess, the ffprobe component. I have noticed they do not have the HLG label in the skin I use (Estuary Mod) but they do play back correctly as HDR HLG. Problem is, the lack of the identification is probably what makes it impossible for the code you posted, to correctly act (as, if I’m not mistaken, it checks for HDR type.
I have tried with latest ffprobe nightly, I paste here the relevant line that actually shows a difference:
Identified correctly as HLG content:
Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67), 3840x2160 [SAR 1:1 DAR 16:9], 25 fps, 25 tbr, 1k tbn (default) (original)
NOT identified correctly as HLG content:
Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/bt2020-10), 3840x2160 [SAR 1:1 DAR 16:9], 25 fps, 25 tbr, 1k tbn (default)
The (lightly edited for clarity and privacy) debug log seems to confirm this. I first played the file that is not detected as HLG and then played the file that is correctly detected.
While I know that Kodi does not use it, MediaInfo (24.06) shows this for both files:
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : HLG
transfer_characteristics_Original : HLG / BT.2020 (10-bit)
Matrix coefficients : BT.2020 non-constant
Identical, even though there is a difference that ffprobe catches.
What should we do about?
Better you ask here?
https://trac.ffmpeg.org/
FYI, the 2nd file looks like 10bit bt.2020 SDR not HDR HLG.
AMLogic in this case has a defect which thinks 10bit bt.2020 SDR is HLG HDR and sends it incorrectly to the display - AMLogic need to fix that one.
1 Like
I don’t understand your point of view. FFMPEG correctly identifies the files as different. MediaInfo sees both as HLG. If both can be identified as HLG by MediaInfo, I suppose the same could be true for Kodi/CoreELEC.
All HDR10 files I am checking result in:
Stream #0:0): Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084)
So maybe the
Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/bt2020-10)
identifier is a different legitimate HLG colorimetry (or whatever it is, I am not knowledgeable about this)?
I don’t know about this, but it’s labeled as HLG in the file name and it’s played back as HDR HLG by my LG OLED C1 and everything looks ok, no oversaturation or strange colors. Plus MediaInfo detects it as HLG and it surely doesn’t do that by looking at the file name.
Maybe as a workaround, because arib-std-b67 is the correct definition for HLG (Hybrid log–gamma - Wikipedia) but at the same time I see MediaInfo correctly identifying the Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/bt2020-10) as HLG.
You are wrong, kodi can only do what FFMPEG do report. If the info is wrong how Kodi should know what to do?
1 Like
I assure you that I am familiar with how Kodi interacts with ffmpeg for stream identification purposes. I have had to learn that when it still wasn’t identifying stuff due to old ffmpeg implementation.
My point is that the files are identified in a different way from regular HDR10, as such, since that information is available through ffprobe (and it’s shown in the logs) maybe it could be a way to work around this problem.
Apparently it’s something similar to this: #9146 (ATC SEI of HLG (18) should overwrite color_trc from VUI in mp4, just like in ts and mkv) – FFmpeg
If I put the same video stream in a .ts container, ffmpeg identifies it as yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67)
Steps to reproduce:
Download sample file (it’s ten seconds, link valid for 30 days): Upload Files | Free File Upload and Transfer Up To 20 GB
ffmpeg -i Test.mkv
shows yuv420p10le(tv, bt2020nc/bt2020/bt2020-10)
ffmpeg -i Test.mkv -c copy Test.ts
ffmpeg -i Test.ts
shows yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67)
I am not knowledgeable enough to understand whether this can be worked around, considering those characteristics are not used in regular HDR10 content or not.
Edit: the resulting Test.ts file is identified correctly as HLG by Kodi and GUI elements are rendered at the correct, reduced, brightness.
Wasn’t sure which thread would be better to post in. I have a AM6b+ on the nightly, and I’m encountering some brief audio cut outs using Stereo FLAC. Curious if anyone else has seen this, or has suggestions for me to try to get better info to diagnose this.
I have more details on my other post in the ng discussion thread, so I’ll just link to that instead so I don’t duplicate everything: CoreELEC 21.1-Omega Amlogic-ng Discussion - #119 by HappyFootie
My setup is as follows: am6+ to AVR (rxa660) to TV.
I want to get it working this way, as I’d like to look into bias lighting akin to ambilight at some point.
I installed CoreELEC using the guide and the recommended settings.
But I have an issue with playback. The device outputs video fine. I can see the settings menu. But once I start plex playback (pm4k) the screen turns blank. I can see on my AVR that it recieves input and I can hear the audio stream. But video doesn’t work.