Posts by HarryH

  • [RPi] Argon ONE Control Add-on (Support Thread)

    Quote from firefox

    Downloaded from github right now , but latest libreelec version gives installing error.

    Until now I only provided ready to install add-on packages here (attachments are at the end of the text):

    Post

    [RPi] Argon ONE Control Add-on (Release Notes)

    Please be aware:

    I'm not a developer of KODI Add-ons. This is only a result of someone who had the wish to get the add-on work again with LibreELEC 10 and later.


    Argon ONE Control

    2025/12/13 Version 1.2.2 (recommended): Please note the updated documentation.

    What it does:

    Provides a GUI and installs a service to manage Argon ONE case features including the power button, fan speed, and the Argon IR remote.

    • supports LibreELEC 10 / 11 / 12 / 13
    • supports Argon ONE V1/2 (RPi4)
    • supports Argon ONE V3 (RPi5)
    …
    HarryH
    August 2, 2023 at 9:57 PM


    So I don't really know what you are talking about and need more details with an exact version and, if necessary, a link to the debug log.
    Perhaps you tried the original version 0.0.1 from Argon, which is known that it not working with versions, which are newer than LibreELEC 9?

  • [RPi] Argon ONE Control Add-on (Release Notes)

    Version 0.0.14 beta 2 released:

    • avoid overwriting the existing rc_maps configuration, just add Argon REMOTE
    • automatically switch between Celsius/Fahrenheit, depending on regional/temperature setting
    • language file refactored
    • regression: fan always-on setting and emergency fan (90°) doesn't worked
    • switched to official add-on versioning

    With this version in the most cases it shouldn't needed anymore to create the lock file to protect the own remote control configuration.
    But for the worst case, for example if someone is using a lircd.conf file, the lock file support remains.

  • RPi5 with three TV tuners

    The positioning of usb_max_current_enable=1 within the config.txt is not really important, but its good placed below the exiting lines in the [all] scope. It should be case sensitive, so you should use lower case for parameters in the config.txt, but UPPER CASE for parameters of the bootloader config.

    You can check the current bootloader config with:
    rpi-eeprom-config
    or
    vcgencmd bootloader_config

    and edit with:
    rpi-eeprom-config -e

  • RPi5 with three TV tuners

    Please keep in mind, that the RPi5 itself needs more power, than previous generations. If the system is very CPU agile and not in the idle state, then attaching of USB devices could be the worst case for the power supply and/or the PMIC.

    If your USB HUB is really a powered one, you should try to only attach 1 tuner to the RPI5 directly and 2 tuners at the powered HUB.

    Only to be sure, you attached the RPi5 power supply directly to the RPi5 pcb, right? You doesn't use a additional case or gadget like RemotePi board ?

  • RPi5 with three TV tuners

    This doesn't looking good regarding the USB power. Was this an attempt with the powered HUB?

    Code
    [  323.045985] usb usb1-port1: over-current change #1
[  323.046043] usb usb3-port1: over-current change #1
[  323.075888] usb usb4-port1: over-current change #1
[  323.075928] usb usb2-port1: over-current change #1

  • Remote Install OS

    And now the important question: What do you have detached? Only the Rii X8, ore more devices?

    Quote from ian_j

    I don't have a keyboard connected.

    but

    Quote from ian_j

    And my wife uses an Rii X8 for iPlayer searches

    It sounds weird to me, because the Rii X8 is a keyboard. Or do you use the RPi in time-sharing with your wife? ;)

    Perhaps you has only Caps-Lock enabled or a battery issue with that device. If somebody else have the same issue in the future, it would be nice to know.

  • LibreELEC 12.0 on Raspberry Pi5

    Only to be sure, do you use a case for your RPi5 like the Argon ONE V3? I'm asking because this case doesn't pass-through the PD information to the RPi5. The case pcb is self a power sink and negotiates the power consumption with the power supply. But the connection RPi5 <-> case pcb doesn't negotiate via PD (power delivery).
    The RPi5 relies on that power delivery information, to enable the whole 5A current and additional the USB boot support/max. USB current.

    In such case, you need to add this lines to bootloader config /EEPROM:
    PSU_MAX_CURRENT=5000

    and to your config.txt:
    usb_max_current_enable=1

  • Only 6.1 LPCM for 7.1 sources with Raspberry Pi

    Thank you for providing the additional image.

    Only for sureness, I have tested with different KODI LPCM audio and video sample files: https://kodi.wiki/view/Samples

    With the official 12.0.0 image the mapping was wrong (6.1 -> RC)

    and after update to the image with the patch provided by you it's now correct 7.1 (RLC/RRC):

  • Only 6.1 LPCM for 7.1 sources with Raspberry Pi

    Hi HiassofT , chewitt ,

    thank for your both comments/doings. Yesterday night I tested just for a short time window with the sample multichannel FLAC files. But there was some strange behavior, which has looked like the issues that _marklam_ reported.
    Yes, I prefer the passthrough way too. My RPi4 and my AVR are able to support that. But the current use case of multichannel FLAC (7.1 LPCM) files differs a little bit. I’m interpreting this as the only available way to get („passthrough“) the multichannel audio lossless to the speakers.

    chewitt
    I will try the image you provided and give you a feedback. It would be nice, if _marklam_ will test it with real music files and hopefully can confirm that it‘s working now. :)

    EDIT:
    The image chewitt has provided is for RPi2/3 only, so I can't test it with my RPi4. _marklam_ it's now your turn. ;)

  • Only 6.1 LPCM for 7.1 sources with Raspberry Pi

    Hi chewitt ,

    thank you for the clarifying. But currenly I'm little bit confused and get a node in my head. Do you have a perhaps a link to a sketch about the different positioning of SL/SR vs. BL/BR vs. BLOC/BROC speakers please?

    I'm asking because my DENON 3808 AVR reports this setup via HDMI (EDID decode) and thinking the SONY AVR of _marklam_ behaves the same :

    Code
     Speaker Allocation Data Block:
   FL/FR - Front Left/Right
   LFE1 - Low Frequency Effects 1
   FC - Front Center
   BL/BR - Back Left/Right
   BC - Back Center
   RLC/RRC - Rear Left/Right of Center (Deprecated)

    This 7.1 AVR has 6 terminals for 2x Surround A + 2x optional Surround B and additional 2x Surround Back Left/Right speakers. The Surround A terminals should be used for a 5.1 setup and the speakers placed sideways or little bit behind of the main seating.

    Currently I think BL/BR is mapped to Surround A + B and RLC/RRC is virtual in 5.1 mode. Because I currently haven't a 7.1 speaker setup I can only relies on the reported input signal.

    In that sketch for the 7.1 speaker setup example, it looks to me
    https://www.intel.com/content/dam/support/us/en/images/mini-pcs/7.1.jpg

    • that BL/BR is moved to my assumed RLC/RRC position
    • and SL/SR replaces my assumed BL/BR position

    During my research I found this kind of adapters too: https://www.allaboutadapters.com/au-hcp2.html I'cant see a different positioning for SL/SR vs. BL/BR

    I'm wonder if AESinkALSA should doing the same with LPCM 7.1 media files?

    • map media SL/SR -> HDMI BL/BR channel
    • map media BL/BR -> HDMI RLC /RRC channel

    Being I'm totally wrong with that idea? Or does all others 7.1 receivers advertise SL/SR via HDMI additional?

    EDIT:

      HiassofT Could it be that there is already an option for that, but a condition is wrong (channel replacement looks not executed) :?:

    xbmc/xbmc/cores/AudioEngine/Sinks/AESinkALSA.cpp at 7c7f08a545d6011aa05c0ece2b960452b65e3457 · xbmc/xbmc
    Kodi is an award-winning free and open source home theater/media center software and entertainment hub for digital media. With its beautiful interface and…
    github.com

  • Only 6.1 LPCM for 7.1 sources with Raspberry Pi

    It looks to me that the speakers that are requested not matching the speaker setup reported by your amp. The channels SL and SR are not listed by your amplifier.

    Code
    2024-04-30 11:57:42.244 T:901      info <general>:     Device 4
2024-04-30 11:57:42.244 T:901      info <general>:         m_deviceName      : hdmi:CARD=vc4hdmi,DEV=0
2024-04-30 11:57:42.244 T:901      info <general>:         m_displayName     : vc4-hdmi (vc4hdmi)
2024-04-30 11:57:42.244 T:901      info <general>:         m_displayNameExtra: SNY SONY AVAMP on HDMI
2024-04-30 11:57:42.244 T:901      info <general>:         m_deviceType      : AE_DEVTYPE_HDMI
2024-04-30 11:57:42.244 T:901      info <general>:         m_channels        : FL, FR, LFE, FC, BL, BR, BC, BLOC, BROC
2024-04-30 11:57:42.244 T:901      info <general>:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
2024-04-30 11:57:42.244 T:901      info <general>:         m_dataFormats     : AE_FMT_RAW,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_S16BE,AE_FMT_U8,AE_FMT_RAW
2024-04-30 11:57:42.244 T:901      info <general>:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD,STREAM_TYPE_DTSHD_MA,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512,STREAM_TYPE_EAC3,STREAM_TYPE_TRUEHDz

    Requested by the play process:

    Code
    2024-04-30 11:58:26.562 T:902     debug <general>: CAESinkALSA::GetChannelLayout - Requested Layout: FL, FR, FC, LFE, BL, BR, SL, SR
2024-04-30 11:58:26.562 T:902     debug <general>: CAESinkALSA::GetChannelLayout - Got Layout: FL, FR, LFE, FC, BL, BR, BC, UNKNOWN1 (ALSA: FL FR LFE FC RL RR RC NA)


    I have seen in the manual of the amplifier, that it supports different speaker schemes. How many and which type of speakers do you have? Maybe you should ensure to set it to 3/4.1 and try it again.

    Edit: Some minutes ago I have looked into my kodi.log. With my receiver I get also BLOC and BROC instead of SL/SR reported. I will test it tomorrow with that files if I come to the same result like you:

    GitHub - sfiera/flac-test-files: FLAC test files for multi-channel sound systems
    FLAC test files for multi-channel sound systems. Contribute to sfiera/flac-test-files development by creating an account on GitHub.
    github.com