Posts by HiassofT

MatteN for the last time: please provide logs. No one knows if your issues are related to that, USB, your devices or whatever.

so long,

Hias

Deri can you please test with the latest nightly build (2022-10-30)? It includes an RPi kernel update with the change mentioned by popcornmix

so long,

Hias

You could have a look at the HDFury Acrana https://hdfury.com/product/4k-arcana-18gbps/ (or Vertex2 https://hdfury.com/product/4k-vertex2-18gbps/ if you need eARC from two instead of 1 HDMI inputs)

I don't own one of these myself but the HDFury products have excellent reputation. The price point isn't exactly low so depending on which TV you have swapping that out could be an alternative, too

so long,

Hias

It's definitely needed as otherwise the maximum will be 4kp30 at RGB 4:4:4 8bit - usually the TV also advertise the HDMI 1.4-compatible "fake" 4kp60 YCC 4:2:0 mode but the RPi doesn't support it (only 4:4:4 and 4:2:2).

No idea about that Asus thing though.

so long,

Hias

How did you set up your whitelist, did you follow the recommendations in the wiki or did you also include SD modes? If you did the latter: don't do it.

Anamorphic videos (like on DVDs) are a bit problematic and ISTR LE 9.x had some issues with those. Please test with LE 10.0.3 (which, BTW still has Estuary as default skin so that should not hold you up).

Playing DVD or BluRay images over the network, whether extracted or not, is often problematic. As you can see in your log kodi has to open dozens of files per second during playback as the video is split into thousands of tiny pieces. The better solution is to rip the main movie to mkv, those are far less problematic than dvd/bluray images.

The stutter-every-second issue sounds like the screen is running at 25 or 50Hz but you play a 23.97 or 24fps movie - the log you provided though shows the mode had been switched to 23.97. You could try changing the adjust refresh rate setting to "always", maybe that helps.

so long,

Hias

We really should change that text about RPi (esp RPi4), lots of things have been fixed and improved in the last year

In several aspects, esp HDR video and HBR audio it's now ahead of other devices.

so long,

Hias

There's nothing obvious in the logs except you are running a rather old LE version, 9.2.8, which is EOL now (latest release is 10.0.3) and you are playing a bluray image over nfs (which may or may not be problematic - never tried that myself).

Another thing worth looking into is your TV settings. Best to turn off all picture/video "enhancement" stuff, they usually just make things worse (especially Samsung TVs still seem to come with terrible defaults). Search eg on rtings.com for your TV model to find some info about recommended TV settings.

so long,

Hias

If you haven't setup whitelist and enabled refresh rate switching then the GUI mode will be used for playback - and if you try playing eg an SD or HD 50fps file at 4kp30 things will go south.

If it still doesn't work then post a debug log.

so long,

Hias

Most likely you are running at 4kp30.

Configure kodi as described in the wiki https://wiki.libreelec.tv/configuration/4k-hdr and optionally add hdmi_enable_4kp60=1 to config.txt to get 4kp50/60 modes as well.

so long,

Hias

Quote from Jocke.Sve

Yes, the "Power" seems to ignore the disable setting!

See here: https://github.com/raspberrypi/fi…ment-1225910618

Quote

The safest way to turn off the PWR LED on all Pis with either old or new firmware is to use the default-on method but declare the output as being active-high:

Code

dtparam=pwr_led_trigger=default-on # The default
dtparam=pwr_led_activelow=off

so long,

Hias

RPi0-3 don't have H265 hardware decoders but older LE (more specifically: ffmpeg) versions contained some clever code to offload some of the heavy lifting to the GPU. So H265 up to HD, with not too high bitrate, was playable on RPi 3.

Unfortunately this code could only work with the legacy proprietary graphics drivers so it's no longer available since LE10 (and has now been removed in latest ffmpeg versions).

so long,

Hias

Just use the RPi imager on a PC to create an eeprom/bootloader recovery SD card and then put it into your RPi

Raspberry Pi OS – Raspberry Pi

From industries large and small, to the kitchen table tinkerer, to the classroom coder, we make computing accessible and affordable for everybody.

www.raspberrypi.com

so long,

Hias

I think you may be out of luck, the soundbar only seems to have an HDMI eARC input and no standard HDMI inputs where you could connect the RPi to.

You have to connect the soundbar's eARC input to an (e)ARC output of your TV.

so long,

Hias

It might be worth to contact suntdek support and ask for open source drivers with source code - with their closed source binary drivers it's impossible to debug any issue.

In the (likely) case they won't do that it's up to sundtek to debug the issue - so again, ask sundtek support about that.

so long,

Hias

You have to name the keymap custom_remote.toml if you use the new toml format - keymaps without the .toml extensions are considered to be in the legacy format.

so long,

Hias

Quote from noggin

Is this the case with all versions of the Argon One cases do you know? They switched from Micro-HDMI to Fullsize-HDMI on their Pi 4B cases - do both have issues with lack of Hotplug, SDA and SCL pass-through on their extenders?

Ah, didn't know they now have fullsize HDMI, so there's some hope the situation improved.

So far I only know about issues with their old micro HDMI versions. They had quite some QA / production issues with the board (can't say how high the actual failure rate was, though):

- pin 19 (HPD) shorted to the GND/shield pad next to it, so hotplug detect didn't work

- cold joints / no connection on some HDMI pins/pads

So basically issues in their (reflow?) soldering process which OFC is more critical with the small pitch of micro HDMI connectors, compared to full size ones.

Issues with soldering are quite common, it's very rare to hit 100% yield rate, but usually QA (automatic optical and electrical inspection systems) should have caught those.

so long,

Hias

Quote from MatteN

Last tested was LibreELEC-RPi4.arm-11.0-nightly-20221006-f15e1de, same behaviour.

No log means no problem

Please test with the latest nightly build.

We've now updated to linux kernel 6.0 and won't be looking into issues anymore that once happened with kernel 5.15.

And please post full debug logs created with the "pastekodi" command or the log uploader function in LibreELEC settings.

Cut down logs or "me too" posts with no info don't help us.

https://wiki.libreelec.tv/support/log-files

so long,

Hias