Posts by HiassofT

  • Anything better than a Pi4 currently?

    Quote from tomstephens89

    Am I really missing anything with DV compared to HDR10?

    Dolby Labs will of course tell you so, but the reality is that you won't notice much difference unless you have display equipment costing in the 5-7 digits USD/EUR range (eg professional cinema projectors).

    See also the conclusion in the rtings article https://www.rtings.com/tv/learn/hdr10-vs-dolby-vision

    Quote

    Ultimately, the difference between the three formats isn't that important. The quality of the TV itself has a much bigger impact on HDR. Both formats can produce much more dynamic images than what we used to see, and HDR delivers a more impactful movie experience as long as the TV displays it properly. There are limitations with HDR, though, because TVs can't reach the 10,000 nit peak brightness and all the colors HDR is capable of, but most TVs still deliver a satisfying HDR experience.

    so long,

    Hias

  • LibreELEC support for Raspberry Pi 5

    Quote from trent

    The power button will maybe be good for safely rebooting when LibreElec/Kodi freezes (?). Maybe you can hold the button for 5s and it will trigger a reboot.

    The power button works pretty much as on a PC: if you press it for a shot time it'll do a graceful shutdown and if it hold it for 5s it'll do a hard poweroff (needed when the system/kernel completely locked up).

    so long,

    Hias

  • LibreELEC support for Raspberry Pi 5

    Quote from shedrock

    I just received my RPI4 on Friday, to find out that there's now an RPi5 on the way. ;(

    No worries, the RPi4 is still an excellent device. And as it draws less power than the RPi5 it's also easier to put it in a passively cooled case.

    I can't comment on cooling requirements yet as I neither have the official active cooler nor the official active cooled case here (and OFC third-party cases or heatsinks are yet to come) but I'd guess it'd overheat (and throttle) quickly if you'd just put it into a simple plastic case without a fan.

    Personally I'm a huge fan of passively, fanless, cooled systems as there are no mechanic parts that will make noise or wear out sooner or later. For RPi4 there are various proven cooling cases/heatsinks (I like the "armor case" a lot, some others prefer the Flirc case) and we'll yet have to see what will come (and work) for the RPi5.

    so long,

    Hias

  • LibreELEC support for Raspberry Pi 5

    Quote from hbbs

    Is for test purposes only and I will delete it after is done.

    https://mega.nz/file/EogjmIRD#…6euyM9vpLMM-LZc

    RPi5 was bored with that. Roughly 20% CPU load (15-30%, most of the time around 20%)

    so long,

    Hias

  • LibreELEC support for Raspberry Pi 5

    Quote from hbbs

    I wonder if you can test a SW playback of an AV1 10bit media as well Link

    That file seems to be an 8bit one and it was a bit short.

    Testing showed roughly 40% CPU load and playback seemed smooth.

    so long,

    Hias

  • LibreELEC support for Raspberry Pi 5

    Quote from JohnWayne111

    Will LE 11.0.3 run with a raspberry Pi 5 ?

    LE 11.0.3 pre-dates the RPi5 release, so no :)

    We are still thinking about if or how we include RPi5 support in LE 11 (eg 11.0.4).

    Background info: we've been testing with LE12, which runs entirely 64bit code and can take advantage of several nice optimizations (eg accelerated deinterlace) which are only available on 64bit.

    LE11 on RPi is entirely 32bit userspace code though. Adding 64bit support to it would open a can of worms (lots of the addons would need updates etc) so likely I'll have a look at doing a 32bit LE11 RPi5 build as this should be easier to achieve (fingers crossed).

    so long,

    Hias

  • Same sound output via two sound cards

    Which LE version are you using?

    I did a quick test on LE12 nightly and oddly kodi showed it under the name of my soundcard but with empty parenthesis after them (usually they have he name of the soundcard, again). Certainly some kodi oddity but I saw it in the log, too:

    Code
    2023-09-25 18:58:05.085 T:1120     info <general>:     Device 3
2023-09-25 18:58:05.085 T:1120     info <general>:         m_deviceName      : both
2023-09-25 18:58:05.085 T:1120     info <general>:         m_displayName     : RPi-Cirrus ()
2023-09-25 18:58:05.085 T:1120     info <general>:         m_displayNameExtra: WM5102 AiFi wm5102-aif1-0
2023-09-25 18:58:05.085 T:1120     info <general>:         m_deviceType      : AE_DEVTYPE_PCM
2023-09-25 18:58:05.085 T:1120     info <general>:         m_channels        : FL, FR, BL, BR, FC, LFE, SL, SR, UNKNOWN1, UNKNOWN2, UNKNOWN3, UNKNOWN4, UNKNOWN5, UNKNOWN6, UNKNOWN7, UNKNOWN8
2023-09-25 18:58:05.085 T:1120     info <general>:         m_sampleRates     : 32000,44100,48000
2023-09-25 18:58:05.085 T:1120     info <general>:         m_dataFormats     : AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE
2023-09-25 18:58:05.085 T:1120     info <general>:         m_streamTypes     : No passthrough capabilities

    If you can't get it working please provide a debug log (enabled debug logging in settings, reboot, ssh in and run "pastekodi").

    If you play multichannel content and have the number of channels set to 2 in kodi audio config then kodi will downmix to 2ch automatically.

    OFC you could also configure more channels, like you did before (also increase the number of channels in the multi pcm accordingly) and eg map 6 channels to HDMI and only FL and FR to the soundcard - but then you'll loose the center channel at the soundcard when playing 5.1 contents.

    You could play around with ttable and down-mix more channels into left and right of the soundcard but that could have negative effects if you only output stereo content.

    It's tricky, you have to play around a bit what you prefer.

    so long,

    Hias

  • Same sound output via two sound cards

    It's best to refer to the various cards by name (eg CARD=vc4hdmi), not by number - the numbers can change. see the output of aplay -L

    For hdmi output you need to use the hdmi PCM (i.e. hdmi:CARD=vc4hdmi,DEV=0) or the default pcm - the vc4 hw pcm supports only iec958 format (not S16LE etc) which pretty much no software supports (the hdmi pcm will do the necessary conversion).

    It seems it's necessary to specify the number of slave channels (eg 4 if you want to output 2+2 channels via the multi pcm) in the route pcm.

    And, if you want aplay -L to show the "both" pcm you need to add a description hint.

    Please test with this asound.conf file:

    so long,

    Hias

  • Error backing up

    It looks like your 500GB drive is dying

    Code
    Sep 24 17:24:51.239391 LibreELEC kernel: sd 3:0:1:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=1s
Sep 24 17:24:51.239860 LibreELEC kernel: sd 3:0:1:0: [sdb] tag#0 Sense Key : 0x3 [current] 
Sep 24 17:24:51.240185 LibreELEC kernel: sd 3:0:1:0: [sdb] tag#0 ASC=0x11 ASCQ=0x4 
Sep 24 17:24:51.240507 LibreELEC kernel: sd 3:0:1:0: [sdb] tag#0 CDB: opcode=0x28 28 00 15 17 16 90 00 00 08 00
Sep 24 17:24:51.240824 LibreELEC kernel: I/O error, dev sdb, sector 353834640 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    so long,

    Hias

  • libreelec cannot powerdown from proxmox control pannel

    Next try, I found a rather easy way to fix this at least on GBM (i.e. all devices except Generic Legacy/X11)

    kodi: change remote power button behaviour to show the shutdown menu by HiassofT · Pull Request #8161 · LibreELEC/LibreELEC.tv
    Kodi's default power button handling is OK for typical HTPCs with window systems but it's the exact opposite of what users (and I) expect from a mediacenter…
    github.com

    Solution: let logind handle the system/case power buttons (performing a shutdown) and let kodi handle all other input devices which might have a power button on them as well (and show the shutdown menu).

    so long,

    Hias

  • libreelec cannot powerdown from proxmox control pannel

    Quote from mglae

    Power off via systemd-logind can be configured in /storage/.config/logind.conf.d

    This will only work on Generic Legacy where kodi doesn't grab the input device. On Gerneric with Kodi GBM logind won't see the power button as kodi has grabbed the input devices.

    Currently the best way to do it (which will work on all variants) is to create a simple /storage/.kodi/userdata/keymaps/keyboard.xml file with the following content:

    Code
    <keymap>
  <global>
    <keyboard>
      <power>ShutDown()</power>
    </keyboard>
  </global>
</keymap>

    BTW: I've changed the PR I've linked and it won't fix that issue because it turned out to be very tricky - the change (and the keymap above) also affects USB / BT / Wireless / ... remotes that kodi sees as "keyboards" and thus kodi would shut down immediately if you (accidentally) hit the power button on such remotes (which can happen quite easily and may be fatal as often it's not possible to power up the PC / RPi / other devices via the remote again).

    so long,

    Hias