Found them. My bad.
P.S.: I'm wondering if we will ever see fully functional upstream kernel support (including the video decoding functionality). Would be awesome!
I think it will happen sometime 
Hi johngalt
do you think RGB issue can be fixed in 8.2 ?
Thanks in advance !
Yes, but i'm not sure of the exact issue. It seems to be fixed without the amports reverts that fix some playback bugs.
Are you sure? I couldn't find them on kszaq's Github.
The default branches on kszaq's github for both linux-amlogic-le and libreelec have all these kernel changes merged in.
Sorry I've been off for awhile, had real life and other projects require significant attention. I currently recommend kszaq's 8.2 builds over these, all changes here have been merged in. Regarding the leia builds, I stopped using them because of instability but may maintain the branch and push some builds. I still need to update this OP.
Display MoreFirst off - Great work on this - Many thanks!
I was stuck using MrMC on an apple tv and kodi on a NUC5PPYH till I realized I could actually run 2160p on a box that cost less than the SSD on the NUC
The display in use is a Samsung JS9000 which is a true 10bit panel hooked to a Marantz SR6010 that fully supports 10bit
I installed the current kszaq 8.2 version Amlogic s905x box till I realized I probably need this fork
However, I do have a very fundamental question
I tried playing back a 10 bit video which was reported by the AVR as 8 bit
Subsequently, I enabled 10bit on the box by setting the class attribute as follows (on the original kszaq 8.2 commit)
Codeecho '444,10bit' > /sys/class/amhdmitx/amhdmitx0/attrHowever,now the AVR reports 10bit>10bit at all times, i.e. not only while playing a 10bit video but even regular 8 bit videos
Short of copying said files on a USB drive and running a visual comparison between playback off the USB drive on the TV vs Kodi, is there anyway to conclusively determine what bit depth Kodi is actually sending out the output as?
Yes, that will set 10 bit output at all time, but it's not an issue while playing back 8 bit videos. When 10 bit output is enabled there is also no 10->8bit dithering used. This is all possible in kszaq's 8.2 builds as well.
mmpp, here's a build with the old output_rgb sysfs interface back. Initially I know you had issues with it (when the other method worked), but at this point I think it's worth trying. LibreELEC-S905.arm-8.2-devel-20170729192828-r25998-gf65b5f2.tar
mmpp , here's a rgb test build (to be set in the same way).
Release 8.2-rgbtest · amillogical/LibreELEC.tv · GitHub
It's built off kszaq's current tree with a kernel patch. When you first reported issues with force_rgb and the attr method worked for you, we still had the following commit in kernel: drivers/amlogic/hdmi: set video color parameter as well with forced o… · amillogical/linux-amlogic@4ad76d3 · GitHub
I had reverted it along with the sysfs interface commit immediately after your report, but in hindsight should have only reverted one.
My LG-TV does not show that it recognizes a HDR-file. If I play the files via a USB-disk connected directly to a HDMI-port of my TV, the
TV says 'HDR input recognized'. That is not the case when the files are played with Kodi/C2 to the same HDMI-port..
Thanks for any advice!
Only s905x+ support HDR, and the better HDR->SDR conversion (a nonstandard hack) also depends on s905x+.
RGB still not work.
This may need a mode change to take effect. Could you try playing a movie for a refresh rate change, and then see if it works?
Checked this evening, colors changed after several files were played. Dmesg:
Given how intermittent this bug is, I wonder if setting it this way ever worked. That's the only change that could be responsible for breaking it within the last few LE8 testing releases.
Do you remember approximately what testing release you were running prior?
The only other way this could've been fixed in other releases, is if you were running one of the "nougat-exp" builds (labeled as "exp" on releases).
kszaq tried your proposed solution of reversing that commit in 8.1.1 - I just tested with my affected Philips tv set and the problem persists.
Did you try playing media for refresh change after? It doesn't change or reset mode, that's up to you (when set early enough in autostart.sh, this isn't needed). Could you get a log to see if it's taking effect? dmesg | pastebinit
johngalt: Are you still using my Repo? Due to recent Kodi API changes I bumped the repo for LE9 to 9.0.1:
rb-addons/addons/9.0.1 at master · Raybuntu/rb-addons · GitHub
Might be the issue here.
Thank you, I'll bump version as well. I saw those changes in commit log, so the bump makes a lot of sense.
Is it possible to set the HDMI Out to RGB Color space? /sys/devices/virtual/amhdmitx/amhdmitx0/output_rgb does not exist anymore. However, there is a setting in /sys/devices/virtual/amhdmitx/amhdmitx0/config that refers to Color Space:
Codeabox:/sys/devices/virtual/amhdmitx/amhdmitx0 # cat config cur_VIC: 16 cd = 4 cs = 2 audio config: on 3D config: offThe setting in question is "cs", a value of 0 would be RGB. But writing to it always leads to a "write error: Bad address". Any idea how to accomplish this?
There's a new way of setting it, but it's broken in the current build (and I broke it). Once kszaq reverts aml/video_dev: updates for nougat: · kszaq/linux-amlogic-le@c89478b · GitHub for the next build, you'll be able to run the following for forcing RGB out:
echo 'rgb,8bit' > /sys/class/amhdmitx/amhdmitx0/attr
If you don't have anything in autostart.sh yet, you'll be able to run the following to set it on boot:
echo "echo 'rgb,8bit' > /sys/class/amhdmitx/amhdmitx0/attr" > autostart.sh
Display Morejohngalt I tired again. If that command put it in autostart.sh, then all video (4k, sd, 720p, 1080p too) are BT2020 and 10 bit.
Resolution: 4k:24Hz -> 4k:24Hz (or 60Hz)
Color space: BT2020 4:4:4 -> BT2020 4:4:4
Pixel depth: 10 bits -> 10 bits
Refresh rate is enable.
I think, this is good now. Or it is problem, sd, and 720p, 1080p 8 bits films show 10 bits?
Why dont put in this command in autostart.sh as default? 8 bits devices cant hande, or why?
I'm glad to hear it. It causes problems for some people even on hardware that can support it depending on their setup, so it's not a good default. The 10 bit on 8 bit media isn't a problem, and to be expected
Display Morejohngalt I bought M8S II 905x box. I use test8 build. I tired hdr content. Tv show hdr, it is good. But my Denon can show hdmi signal info.
4k film (10 bit, bt2020):
Resolution: 4k:24Hz -> 4k:24Hz
Color space: YCbCr 4:4:4 -> YCbCr 4:4:4
Pixel depth: 8 bits -> 8 bits
I run this command: echo '444,10bit' > /sys/class/amhdmitx/amhdmitx0/attr
4k film (10 bit, bt2020):
Resolution: 4k:24Hz -> 4k:24Hz
Color space: BT2020 4:4:4 -> BT2020 4:4:4
Pixel depth: 8 bits -> 8 bits
8 bits is ok? Or something is wrong?
Why dont run this command automatic under boot?
Could you try setting it before you play anything, or put it in autostart.sh (located in .config) and reboot? If you never added anything to autostart, you can run the following: echo "echo '444,10bit' > /sys/class/amhdmitx/amhdmitx0/attr" > autostart.sh
If this doesn't work, I'll need to see a log. Do you have refresh rate switching enabled (it should be).
I know there was a handshake issue with your denon receiver, so I wonder if it's unable to read 10bit support (will see in a log).
kszaq, awesome work, thank you! I broke the forced rgb output support with the following commit, and recommend a revert for now: aml/video_dev: updates for nougat: · kszaq/linux-amlogic-le@c89478b · GitHub
With this reverted, you can set echo 'rgb,8bit' > /sys/class/amhdmitx/amhdmitx0/attr in autostart.sh to recreate the force_rgb behavior.
I also recommend merging PR15 of your LibreELEC.tv repo into libreelec-8.2 so colorspace can get passed if mode is the same.
Note: for users who want 10 bit output, you may set the following in your autostart.sh:echo '444,10bit' > /sys/class/amhdmitx/amhdmitx0/attr
Hey,
I am using this version 9.0.0-testing6. I installed Netflix and Amazon. It runs, but sometime I have video and audio stuttering and video and audio are asyncron. After a few seconds (30 seconds) it works again. Any soultion/idea for this?
Not currently. This is something that may improve over time. On these devices, netflix and amazon aren't hardware accelerated.
plikmuny ssh into your box and run those commands (top to verify, bottom to set). That tearing photo is also nothing like what I expected when you mentioned it awhile back; I expected "screen tearing" in the traditional sense.
mmpp I'll fix the rgb issue in the next build (know the issue).
olive069 S912 support is easy on both the LE9 and LE8 branches, there's just one patch I need to update to fix the build.
I know I was talking about doing a new build this weekend, but I shouldn't have given an ETA because I didn't get a chance to test some nougat-exp changes.
Thx johngalt
You're welcome. Testing6 of LE9 just uploaded which includes those kernel patches.
