Posts by Da Flex

PS: Be sure to push the plug to the max into the RPi.

OK, on my headphones LE is loud enough. I have set the audio channels to 2.0. Maybe it affects analogue audio, too.

Some brainstorming:
- change the wiring to NUC -> TV -> AVR

- select "HDMI" as audio output device on LE

- only use 2.0 channels on LE (this LE option is a bit misleading)

Maybe one of those works. Try combinations, too.

Go to "Settings -> System -> Audio -> Audio output device" and select "PI: HDMI and Analogue".

Proved by myself.

Another theory: maybe the "Intel burst technology" for temporary high frequencies on Celeron is not supported.

Quote from blueribb

CPU Speed: 798 MHz (most of the time) - over a 10 minute period I watched it go from 798 MHz up to 2186 MHz for only a few seconds.

It looks like your system runs fine at ~800MHz, so I think that's the preferred state for LE. It supports my other advice to have a look at the UEFI display settings (HDMI / VGA). If LE has to feed two displays, then ~800MHz could be short.

Quote from SirMacke

Will do.

But if I remember correctly this issue has been present for years.

Thanks. I have seen a lot of people here in the forum, who run Intel NUC's without issues. That's why I'm curious about your one. The 9.1.x development is mainly targeted on RPi4B, which currently has heat issues. Maybe devs play around with CPU frequencies at the moment, so I suggest 9.0.2.

As I already mentioned: Do the tests with a stable release - 9.0.2 is the latest. Expect driver issues at 9.1.x development builds.

I had a look at the CPU data sheet, max. frequency (burst) is 2.30GHz, so 800MHz is not close to the max, as I stated before.

The data sheet of the NUC says, it supports two displays (HDMI, VGA). Maybe one of them has to be switched off to relieve the CPU.

* see my next post *

You are not using a stable build of LE. Try a major release, like 9.0.2.

Quote from SirMacke

It does not explain 800Mhz Max on the CPU.

I don't think so. A memory leak can explain high CPU usage. Follow my advice and post the result.

It looks like a memory leak error, triggered by the Netflix add-on:

...
2019-07-26 10:10:42.314 T:139900012103424   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <class 'urllib2.URLError'>
                                            Error Contents: <urlopen error [Errno 111] Connection refused>
                                            Traceback (most recent call last):
                                              File "/storage/.kodi/addons/plugin.video.netflix/addon.py", line 33, in <module>
                                                NAVIGATION.router(paramstring=REQUEST_PARAMS)
...

Uninstall the add-on and see whether it solves the issue. Maybe a simple re-install makes Netflix work as expected.

Hard to say with the provided data. Please give us a link to the log file. Always use the default skin for all tests.

Welcome!

I'm from Germany. Where are you from?

Quote from Kantilo

For example on a cable here : Câble HDMI 1M - KUBII

Wrong product. If you want 4K, then go for a store that clearly says "4K". It's easy to find.

Official HDMI standard names are "HDMI High Speed" and "HDMI High Speed Premium". They both support 4K.

You need a fresh installation. Avoid to install data into bad blocks of the SD card (I bet you have some). To do so, GParted can identify those bad blocks, and leaves them out on the format process. e2fsck can't do this, and it can't bring the data back that you have already been lost.

It doesn't makes sense to talk about follow-up errors now. Replace or repair the SD card first. Repair is possible, but I only suggest it for advanced users, who can deal with special software tools like GParted.