Posts by Da Flex

No. Some people use extra hardware to switch on by RC.

Same error when using the default skin?

Quote from carlalex

I pretty much do exactly that every day at work.

That's cool, then you're an expert in multimedia routing. Unfortunately your NUC is probably far away from the hardware capabilities you're using at work. To be precise, I don't think the NUC's data bus is able to stream A/V data to TB and HDMI in-sync.

I know that other LE users failed to use an USB DAC when it's about high speed (HD) audio. LE's Linux is no real-time kernel. On most hardware HD audio can't be delivered in time to USB, so audio data will just be dropped by the system. You will run into problems like this if you try to use TB and HDMI at the same time for A/V output.

I bet it's impossible to get A/V on TB and HDMI at the same time. So you can't grab audio from the NUC's HDMI output, and the HDMI audio splitter solution still seems to be the best. Wow, there are some crazy dependencies among BIOS, kernel and Kodi. I don't want to deal with it. That's why you live in Silicon Valley, and I'm in Germany.

Thanks for testing the autostart.sh line.

Quote from yossigo

The config.txt is the default with only two added lines:

Code

hdmi_ignore_edid=0xa5000080
hdmi_force_hotplug=1

Just to be sure you tried the right config.txt options, add this lines to the above:

framebuffer_width=1280
framebuffer_height=720
hdmi_group=1
hdmi_mode=4

It will start your RPi at 720p / 60Hz, fitting for your monitor specs and RPi speed.

He will not benefit from selecting a separate audio device, because HDMI is his only digital audio output on the NUC.

The NUC does not allow to use Thunderbolt as an audio-only device, so it's not available as Kodi audio device.

I'm reading here for a while, but I never heard about such a routing option. Buy an HDMI audio splitter and go optical to your receiver.

I suggest to start the RPi with your preferred HDMI mode, defined at config.txt.

Quote from chewitt

I suggest upstream translators don't do a half-arsed job with their translations. It's the correct and darn sight easier approach

I always try to think from users perspective while programming: When LE just cashes, users think you're the bad boy. When LE doesn't crashes and pops up a toast "Incomplete translation / skin", then users know the real bad boys, and can address them. Isn't that great?

It's worth to program all the if's and then's, because bad translations and skins will never die. Doing some tests before allowing an add-on to be uploaded might help, too. You already do add-on quality control to avoid illegal stuff.

Quote from yossigo

So basically the issue is HDMI needs to be connected only *after* Kodi is up.

Put tvservice -p into autostart.sh.

If this is not successful, post your current config.txt.

Try this settings at config.txt:

hdmi_ignore_edid=0xa5000080
hdmi_force_hotplug=1

Quote from mglae

A bug in resource.language.el_gr causes Kodi to crush in certain skins.

Yes, a combination of custom skins and translation files is a possible cause.

@ LE developers:

I suggest to rework the LE code to make it more error-tolerant against incomplete skin / translation files. LE shouldn't crash in such cases.

It's not the Greek language, your custom skin just needs an update to work on LE 9.x.x (missing texture files):

2020-03-21 15:00:48.704 T:140011197126848  NOTICE:   load skin from: /storage/.kodi/addons/skin.aeonmq8 (version: 2.9.0)
2020-03-21 15:00:49.116 T:140011197126848 WARNING: Trying to add unsupported control type 1
2020-03-21 15:00:49.161 T:140011197126848 WARNING: Previous line repeats 3 times.
2020-03-21 15:00:49.161 T:140011197126848   ERROR: Control 9000 in window 10000 has been asked to focus, but it can't
2020-03-21 15:00:49.379 T:140010747717376   ERROR: DoWork - Direct texture file loading failed for resource://resource.images.recordlabels.white/
2020-03-21 15:00:49.383 T:140010756110080   ERROR: DoWork - Direct texture file loading failed for resource://resource.images.studios.white/

If you want maximum stability, use the default skin.

This hardware situation has some unknown factors. I suggest to try a full desktop Linux first (like Ubuntu on DVD or USB stick). If such Linux is HDMI-visible (maybe only in Live mode for testing), then you have a chance to install LE.

There are some RPi 4B reports about 5GHz problems when using internal WiFi.

If you're an 5GHz-only user, then activate another frequency band on your router.

My theory about this issue is higher energy consumption at 5GHz, and the need of developing a proper energy management. I still have no confirmation for this theory, but it looks like they are working on it.

I had a look at the Argon ONE install script. The location of argononed.conf is wrong. Move it to /storage:

mv /storage/.config/argononed.conf /storage

Quote from fyrstyk

Log attached.

You're still using a custom skin, but it's important to use the default skin to avoid any EGL scaling errors.

I'm no Hyperion user. By just reading here, it looks like the add-on needs a fix to work with RPi 4B. Maybe some higher resolutions lead to approximation errors, resulting in wrongly triggered lights. Just my 5 cents.