Yes and no. The reason for 2 adapter was that the RPi4/RPi5 have 2 HDMI ports. And I think the original intention was to support HDMI0/HDMI1 (multiple) ports. One adapter entry for HDMI0, and second for HDMI1. The port number property inside of every adapter is a different thing and explained in my provided links.
But: KODI (maybe libCEC too) currently doesn't support a splitted configuration, so it currently make no sense/different. After think about all stumbling stones also it's possible that there is no working edge case there it make sense to have that feature. AFAIK there is intended only one sink in the HDMI device tree and every other HDMI device should have a unique address. A splitted configuration would conflicts with that, if enabled simultaneously. Perhaps a toggle to use HDMI0 or HDMI1 for CEC could made work without going in conflict with the addressing. Currently you can in 99.x% of the cases reach the same with only one configuration. And this can make trouble enough ... 
Posts by HarryH
-
-
Hi Marcin ,
KODI is using libCEC, so some parts are already documented here (maybe outdated): https://libcec.pulse-eight.com/FAQ
Some other things I have already tried to explain here:
As long you use a LibreELEC version where you got advertised 2 CEC adapters in the settings menu, please change only one of them. Sometimes one of them exposes more menu entries than the other. Ignore this or use everytime the one with most items listed. Both CEC adapters write to the same settings/properties. Because this is weird and in collision with HDMI device tree, this was fixed/removed within the nightly builds. -
Good eyeballs chewitt
, this was already my first suspection in post#4. wizardly_jennings there seems something was going wrong with your first attempt with the nightly build. Please try again, like chewitt recommend and ensure the you grab the most recent version from below.
Alternatively you can do that at the ssh console of LE12:Codecd /storage/.update wget https://test.libreelec.tv/12.0/RPi/RPi5/LibreELEC-RPi5.aarch64-12.0-nightly-20241008-0803b93.img.gz reboot -
You must add both boot parameters to cmdline.txt not config.txt !
-
Just for reference, as it is not an RPi5:
In the meantime, I have tested my RPi4 with LE 12 nightly-20240914-7b7b3db directly on the X90L at "HDMI 3 (eARC/ARC)" without the issue like you have.
Works immediately without any special settings. HDMI signal format: Standard format -
You should be able to find the equivalent to ‘Deep Colour’ on your SONY here:
Menu -> Settings (gear wheel) -> Channel & Inputs -> External Inputs -> HDMI signal format -> HDMI 1/2/3/4:
- Standard format
- Enhanced format <- could be equal to Deep Colour
- Enhanced format (Dolby Vision)
- Enhanced format (VRR)
The last 2 options are only available at HDMI 3 / 4. So maybe you should also try another HDMI port: 1 vs. 3 or 4 for a crosscheck.
PS: Do you know if you have the latest firmware version installed on your TV? For the European model of this TV, this is: 6.7612 from 18 September 2024. -
Yes, you should give it at try. The chip hardware was reworked to reduce the production costs for the RPi5 2GiB model. Maybe that change is responsible for the special handling and for new production lots of other models it's needed too now. Only a assumption...
EDIT:
The related change should this one https://github.com/LibreELEC/LibreELEC.tv/pull/9253
It depends more on the chip revision 2712C1 vs. 2712D0 than the memory size. But the RPi5 2GiB seems to be one of the first models with that revision and you could be affected by this. -
Do you use a RPi5 2GiB model? I can remember that you should use a current LE nightly to support that. I think the scrambled picture looks so...
-
I did that, but nothing changed.
Possible. So you say the only way to try is by buying a newer cable? Then I hope the 12€ are not for nothing
I can't make the decision in behalf of you or give a guarantee. For example I know that also cheap HDMI 1.4 cables was in the wild, which doesn't have the CEC pin connected.
Like Da Flex already mentioned right. You doesn't informed us which device you are using for LE. Because you should ensure that your LE12 device has a working CEC adapter implemented. If all things are ready, its also possible that you just chose a wrong HDMI input at your TV. Some old TVs supports CEC only at one of them. -
I thought, that you want some help to get a solution for your CEC issue.
No, 12.0.1 is not the last build, so i linked already a newer version which doesn't have the issue with 2 CEC Adapter entries. It's up to you to try it or not.The DENON supports also CEC by itself and reports as active device, so the TV can switch to HDMI 1. After that every single device connected to the DENON can signal as "active source". The last one started, wins.
Example:
TV (HDMI 1) <- DENON (HDMI 1) <- FireTV
.... DENON (HDMI 2) <- LibreELEC (KODI)
.... DENON (HDMI 3) <- Bluray
The TV exposes: "HDMI 1", "HDMI 1 Amazon FireTV", "HDMI 1 KODI...", "HDMI 1 Bluray"
The last 3 entries equals to HDMI 1, HDMI 2 and HDMI 3 of the DENON. So it's usual that you can steering only 1 of that devices with your TV remote control at the same time. It could be that the first entry ‘HDMI 1’ of the TV only passes the remote control buttons via CEC if the device connected there has reported itself as an ‘active’ source.To realise this, you only need a properly configured CEC adapter in LibreELEC 12.0.1+ and no other components that cause additional trouble. (such as cheaply made HDMI cables, firmware, etc.), no more and no less.
-
To fulfill the official HDMI-CEC specification you need cables which follows HDMI 1.2a (and upwards). Maybe your cables does already, because CEC was available for some device since 1.1, but not official. If you already tried, it could be that you have a cable, where the CEC pin is not connected and therefore doesn't work.
-
The behavior with multiple HDMI 1 entries is known to me with SONY Android TVs. There can some more sub devices displayed if you have additional CEC compatible devices connected to your DENON AVR. On that way you are able to switch between the different CEC sources on your AVR via TV remote. Also I can confirm that not all (but the most) CEC keys are working if the TV is only switched to "HDMI 1" and not to the sub entry "HDMI 1 KODI ...". Maybe you have installed a firmware update for the TV, so that something has been changed?
The TalkBack feature (if available) is disabled? https://www.sony.com/electronics/support/articles/00269974
Regarding the irritating double entries for the CEC adapter in the input settings menu, you should switch to a newer version than the official version 12.0.1, as this contains the fix: https://test.libreelec.tv/12.0/RPi/RPi5/…-0803b93.img.gz -
Both are non-native Linux file systems. Can you prepare a thumb drive with ext4 and test again? If you have no Linux to fill the stick with content directly, maybe you can copy from your laptop via network to it.
Note: All file systems on external drives (such as SD cards, USB sticks, etc.) are vulnerable during cached writes, so you should make sure that you do not remove the drive from the running system without taking special measures. For the test with ext4, I would recommend not unplugging the drive until the system has shut down properly. -
Which file system do you use for your thumb drives? Maybe this makes a different.
-
this will not fix the cause, but you can prevent the problem by bypassing gpiozero and using lgpio directly.
lg libraryPS: Your add-on project is currently not set to public.
-
Just a shot in the dark: Because you reported that your AVR switches automatically back to TV/SAT. Do you have tried with CEC disabled? Default is to report KODI as active source. Maybe something is going wrong with it in your current configuration.
-
I already posted the commands to collect some information. The last 3 lines of my previous post contains the commands to use via SSH console.
- lsblb -> list block devices
- lsusb -> list USB devices
- dmesg ... -> search for specific entries in the kernel message log
If it sounds like rocket science for you, then we will go beyond the scope of this thread.
Sorry, if I distracted you. I wanted to make sure that both physical drives are recognized correctly. Because this is important regardless of whether you use 2 individual drives or the spanned volume. But if you have created a spanned volume using the Windows functions, as chewitt has assumed, then you need all the things he has already described to get access to the whole volume. -
chewitt,
it looks to me, that the D4-320 works like a USB->SATA adapter with SATA port multiplier or something like that. Not as the "usual" JBOD volumes of simple software raid adapters. Maybe Gar90 should look for kernel messages regarding the USB devices first?lsusb
lsblk
dmesg | egrep -i "usb|ata|seagate"
