Posts by HiassofT

Just tested with your images, everything fine here.

Watching your video rang a bell, though, I remembered having a very similar issue back then when I first tested my LED strip but was using a power supply with too low power rating. If I raised the LED brightness beyond a certain point the strip would just shut off completely. This was most easily to reproduce with white light (as this means all three R/G/B LEDs are active at the same time).

Not sure why that also happens with green and why it was OK on the RPi3, but as it's rather easy to test and would provide some interesting datapoint please give it a try:

Start up hypercon, connect to libreelec and then pick white on the color-wheel. Then change the brightness (on the vertical slider to the right) and check if the LEDs turn black at some point. Checking with other colors (yellow, green etc) may also be interesting.

so long,

Hias

Yes, 2GB will work fine for 4k playback.

If you feel the itch to have more memory then spend the additional 10 bucks for the 4GB version, it won't hurt but isn't necessary for 4k.

so long,

Hias

I've just watched Disenchantment S02E01 from netflix at 1080p24 with hyperion active on a RPi4 4GB and didn't notice and screen dropouts or other issues. So not quite sure what might be going wrong on your setup.

A rather common cause for screen blackouts, especially with CPU demanding content like software decoded video or power demanding peripherals like USB HDDs or DVD drives are marginal power supplies - if you're not using the official RPi power supply (I use that here and it's fine) or if you have one or more bus-powered USB HDDs you might look into that.

So far I'm only aware (and can reproduce) 2 major issues with Hyperion (more specifically the dispmanx grabber):

4k playback with the dispmanx grabber / Hyperion active results in no signal on the HDMI output. There's currently no workaround or solution available, reason for that seems to be that the RAM bandwidth is just too high. This is a known issue and it will be fixed eventually (but seems to be a bit low priority - it needs to be fixed in the RPi firmware so not much we can do about it).

The other issue I frequently see here is no HDMI signal at all after a cold boot (on my 4kp60 screen) if Hyperion is active. A simple workaround for that is to start Hyperion after Kodi has started, I'm using a simple systemd drop-in here to do that:

.config/system.d/service.hyperion.service.d/delay.conf

[Unit]
After=kodi.service

[Service]
ExecStartPre=/usr/bin/sleep 10

Not exactly sure what causes the no-signal issue (could be something in the firmware), but with the drop-in workaround everything's been fine here in the last weeks.

so long,

Hias

If you installed the 9.2.0 test build linked above please do a manual upgrade to the now released official 9.2.0 version (from the download page).

We had to do a last-minute change (forgot to bump the VERSION_ID from 9.1 to 9.2) and while everything should be fine ATM it could result in issues with addon updates in the next days/weeks.

so long,

Hias

You'll have to create a button mapping for the video playlist window (should be "VideoPlayList") as well and eg map "blue" to "ContextMenu".

Otherwise the default (global) mapping is used, which is usually the PVR functions for color buttons.

If in doubt enable debug logging in kodi and check kodi log for "Window Init" messages - this will tell you which window is currently being used. The https://kodi.wiki/view/window_ids wiki page lists the window names (which you have to use in keymap xml files) and window xml files - eg if you see "MyPlaylist.xml" in kodi.log you'll have to use "videoplaylist" in keymap.

The kodi log will also show you the button press and the performed action.

so long,

Hias

yes

Ah, just noticed you wrote in your first post that you want the functionality of the "c" key. The default keyboard keymap shows that "c" is mapped to "Playlist" in FullscreenVideo - so use that.

eg

<keymap>
  <FullscreenVideo>
    <remote>
      <blue>Playlist</blue>
    </remote>
  </FullscreenVideo>
</keymap>

so long,

Hias

Instead of global use FullscreenVideo (or FullscreenLiveTV etc) - see the list of window names here Keymap - Official Kodi Wiki

Mappings in "global" are the global defaults and window specific mappings can override the global ones.

eg in kodi defaults both the menu and title button are mapped to ContextMenu, but in FullscreenVideo menu is mapped to OSD and title to PlayerProcessInfo - see hee xbmc/remote.xml at master · xbmc/xbmc · GitHub

so long,

Hias

Forgot to add: if you don't want to wait you can also do a manual update (see samba/cli sections here Update LibreELEC [LibreELEC.wiki]) using the 9.2 Beta 2 image libreelec-rpi4.arm-9.1.502.img.gz

so long,

Hias

Quote from fatshotty

thanks for the explanation.
I wonder: in kodi log file I saw "9.1.901" , so I think it is newer than 9.1.502, isn't it?
moreover, No update found so far and yes, "wait for network" is active

9.1.901 is an internal version number for addons only, which doesn't always strictly correlate to the LibreELEC version number you see eg in system info or on the boot splash screen. In LE 9.2 alpha/beta (9.1.xx versions) we had to set the point version to a very high number to avoid a clash with previously relased addons for master.

Can you check the LE version number in system info? I'd guess it shows 9.1.501 there. Still puzzling why you got that instead of 9.1.502 and why you don't see any updates....

BTW: final 9.2.0 version should be released very soon (unless last-minute issues show up) which should resolve the version issues, too.

so long,

Hias

Hmm, looks like you got some older LE version via noobs install - not quite sure why that happened.

In LE settings you should see there's an update to 9.1.502 available (if not, set automatic updates to "manual", select "LibreELEC-9.2" in the update channel and then go to available versions - there 9.1.502 should show up).

BTW: automatic LE updates and addon update/installation can fail if the network connection takes too long to come up - it's best to enable "Wait for network before starting Kodi" (in LE Settings->Network), this avoids running into these issues.

so long,

Hias

yes - with the exception of the Arduino Uno, which will be slower due to the limited baudrate.

so long,

Hias

If RPi4 plus level shifter works fine then go for it - both Arduino and GPIO connection plus level shifter should work pretty much the same.

The main reason I'm using an Arduino here is because I have an audio card plugged in which needs SPI - so I can't use the GPIO connection method.

so long,

Hias

Quote from CvH

BEWARE, we made an adjustment specific to Slice that was done blindly without any actual testing. So pls do a backup before, this should work but we can't test it before.

More specifically the changes affects the built-in RTC [le92] Slice/Slice3: use upstream method to set xtal load capacitance by HiassofT · Pull Request #4015 · LibreELEC/LibreELEC.tv · GitHub

Even if I didn't get the change right it shouldn't result in major issues but better keep an eye on the RTC and report back if something's off there (will probably only be noticable if the Slice isn't connected to a network, otherwise time is synced with NTP).

so long,

Hias

Sorry, I somehow missed that you already got an Arduino Uno at home.

In that case just give it a try, just remember that you have to set the baudrate to 115200 which will limit the number of LEDs and the update rate - about 100 LEDs at 25Hz update rate should work though (haven't tested that myself though).

The ATmega 32u4 based Arduinos don't have that limitation, this is why I generally recommend using them (esp when buying new it doesn't make much sense to spend money on the older Arduinos, like the uno).

Concerning the level shifter: without knowing specific details about the used level shifter it's hard to tell if it'll work or not. Most of the level shifters in the form-factor are passive ones with pull-up resistors and while they may work they are neither recommended nor guaranteed to work for this specific application (unidirectional up-shifting of >= 1MHz signals from 3.3V to 5V).

As the issues can be very subtle and hard to track down ("mostly" or "sometimes" working etc) I generally advise against using such improper approaches.

so long,

Hias

The log shows that after startup the RPi is outputting audio to HDMI. But you seem to have a plugin "service.bluetooth-audio" installed which is then switching audio output to pulse. Uninstall that addon and everything should be fine again.

so long,

Hias

Quote from harun-cuk17

US $0.27 9％ Off | IIC I2C Logic Level Converter Bi-Directional Module 5V to 3.3V For Arduino

AliExpress - Online Shopping for Popular Electronics, Fashion, Home & Garden, Toys & Sports, Automobiles and More.

I got now this one at home. Is this one also fine?

Probably not, but you can give it a try if you already got one.

These converters are mainly useful for slower stuff (ike I2C), to get clean signals for higher speed (SPI) stuff use a 74HCTxx chip.

so long,

Hias

hagaygo thanks for reporting back!

I've had a chat with the RPi devs and the CMA issue is quite an odd thing - in theory the CMA size shouldn't matter at all, but your and our tests showed otherwise. Could be a linux kernel issue or we are missing some subtle thing.

Anyways, using cma=64M (or even cma=48M) should be safe with Kodi 18 (with Kodi 19 probably not). Even 32M could work on a HD (1920x1080) screen, though that's very marginal (checked here with a 1920x1200 screen and it was a tad too low and kodi didn't start).

Other than that: reducing gpu_mem (to 256 or 192 - though that'll probably cause issues when trying to play 4k videos) or adding a bit of swap (256MB or so) should also help on 1GB RPi4 models.

so long,

Hias