Posts by lrusak

The setting isn't available when using GBM windowing in Kodi

Quote from rosede

I'm sorry, but that option just is not there, and yes, I have Export enabled.

Daryl

Post a debug log please

Use a USB stick

Quote from Raven

Thanks, I just tested and ran the live/run version on USB.

However I don't get any HDR output on my tv.
When I run Kodi in Windows my tv does recognized the HDR input so I would assume there is nothing wrong my connection setup (nuc -> onkyo -> tv)

I have a Nuc i5 (NUC7i5BNB)

Onkyo TX-NR676E

Samsung Q90

I don't think that hardware is supported with the current HDR builds

There isn't any vnc server available

HDR isn't supported on x86 devices at this time.

There is a thread on here with some WIP builds to support HDR but your mileage may vary.

It's done via udev, you would have to override the udev rule to stop specific devices from mounting

something like:

cp /usr/lib/udev/rules.d/95-udevil-mount.rules /storage/.config/udev.rules.d/

Then you can edit it with nano in it's new location

nano /storage/.config/udev.rules.d/95-udevil-mount.rules

Post an entire kodi debug log (using pastebin preferably)

Quote from x0x0

Thank you, Zero. I am still playing around with things and trying to familiarize myself with how everything ties together. I had NO idea this would be such a learning experience. All I wanted to do was to play a couple games. It tuned out to be more, much more than I barganed for.

It's pretty easy if you don't have to deal with firmware.

For SNES games:

1) download snes rom from internet

2) install snes emulator (snes9x) from the LibreELEC add-on repo

3) navigate in kodi to the rom that you downloaded in step one and select it

4) play game

I've never personally seen this before and would likely consider it a kernel bug.

You can't use python in a shell script

You need to add that code to the RGB_Cooling_HAT.py

You should also post the exact python error you get when you try to run the script

check the output of

systemctl status service.lcdd.service

Quote from chewitt

For iPlayer TV watching and older lower quality DVD rips that's completely true, but when I listen to SACD or watch well mastered 4K UHD rips the difference is - to my ears - quite clear.

LPCM and the HD audio formats are effectively the same thing (once the later is decoded)

Quote from Deezle

The same goes for me. I have IMO a pretty good AVR. I want that device to decode audio and not Kodi. The difference is well audible.

It's very unlikely you can hear a difference between HD audio formats and LPCM

Quote from spinarak-miguel

Thanks for answering. Is PipeWire something you've considered?

I have pipewire already packaged as a replacement for our bluetooth audio stack but it likely won't hit LibreELEC for a while yet as there is some propblems running pipewire on arm platforms. It will be nice though as pipewire already supports sbc, aptx, and ldac

It will work on a Generic PC. The pipeline used on the RPi4 is still very much WIP.

Also, I'm glad 3D is dying in the world of movies, it's such a gimmick anyways.

Quote from spinarak-miguel

Hey, any progress on this?

Probably not going to happen, you have to switch between audio devices to use bluetooth audio anyways so enabling/disabling passthrough shouldn't be much of an extra step

Quote from ghtester

At first, I would remove brackets and & sign from autostart.sh.

I have no experience with docker but I suppose it's enough to run the docker run command one time to start it so & sign does not make sense, especially when there's the sleep command in brackets as well.

This is typically done so the calling command can be queued into the background and doesn't block the startup of LibreELEC. Likely the OP would want to block though based on network access and docker starting