Posts by chewitt

Kodi is a player app running on video output hardware connected to your TV. If the video output hardware can connect to the DAC over USB then Kodi should be able to see/select the DAC as the audio output device. Kodi is not an audio server/streaming app so it will not be able to send/stream audio to the DAC over Ethernet.

There appears to be a Tidal add-on for Kodi https://github.com/arnesongit/plugin.audio.tidal2 but have never used it. The support thread in the Kodi forums appears to be active https://forum.kodi.tv/showthread.php?tid=200555

There was a Qobuz add-on but it appears there were changes to the service that broke it and the add-on doesn't appear to have been updated since, see https://forum.kodi.tv/showthread.php?tid=146568 and https://github.com/tidalf/plugin.audio.qobuz

The AMLGX image can support an S905W box but (to state it again clearly) it has no support for 3D media. The legacy kernel S905 image has some level of support for 3D media (but never tested by me .. I never bothered with 3D hardware or media) but here is no longer any support for the legacy S905 image and I doubt it works with a random S905W box.

It might not have been the "Yes, please purchase some cheap rubbish Android box and we'll make it work for you" answer you wanted, but if you want good 3D support on a cheaper device .. I gave you an option.

run "pastekodi" and share the URL please

The default Library is designed to scrape and add files but not auto-delete them. Installing the "Library Watchdog" add-on from the Kodi repo should give you what you want.

English language forum (es tut mir leid).

You moan wish is granted..

Quote from tinca

I am upgrading from 9.2.8 which worked fine. Now, after upgrade LibreELEC keeps crashing/rebooting until finally loads into safe mode.

So apparently your upgrade which worked fine, is not fine. This is self-inflicted punishment for ignoring all the DO NOT DIRECTLY UPDATE FROM LE9.x to LE10.x (or LE11.x) BECAUSE IT WILL CAUSE PROBLEMS type warnings and blog posts we made in the last 18-months since LE10 launched advising everyone to do a clean install. In 99% of cases the problem is older Python2 add-ons which are not compatible with the now Python3 only environment .. causing Kodi to crash when it loads them.

If you can SSH in "systemctl stop kodi && mv /storage/.kodi/addons /storage/.kodi/addons-old && systemctl start kodi" should solve the initial problem by removing all add-ons; allowing Kodi to start without crashing. Then you can (re)install them from compatible sources.

Switch to LE11 update channel and do a manual update. Direct update from 10 > 11 isn't an issue. Only 9 > 10 or 9 > 11 will cause problems.

Quote from f3jeff

Now the only thing missing is 3D support

Don't hold your breath, I have low expectations it will be on the Pi Foudnation to-do list.

The best device for 3D support in LE is a Raspberry Pi 3B+ running the LE 9.2.x image; newer images use a revised video pipeline that doesn't support 3D yet (and maybe never will since it's not a big priority these days) and there is no support for 3D in the current Amlogic releases. It might work in older Amlogic releases but you can expect limited/no support on those now (different codebase, all the developers that hacked it are long gone). If you go RPi, use a simple HDMI > S/PDIF splitter for audio (or a DAC card, but that costs more).

Or you can use the cheap Android box with Kodi on Android .. which prob. works enough for playing occasional 3D movies.

ConnMan does not support being used as a repeater, and it's a very-deliberately simple hotspot function so I doubt it will acquire that ability.

If you want to create overlays you'll need to compile them (to use them); so in the context of the LE build-system you might as well just patch the device-tree that you want to use via a normal kernel patch. IMHO that's easier and doesn't need support for overlays.

Quote from DiMag

Does RPi4B (2GB RAM) play AV1 video reliably? (I take it as granted that it does play reliably HEVC, up to 10bit.)

AV1 is a new codec and there is very little hardware out there with native decoding for it (mostly Android TV boxes). So RPi4 will be forced to software decode AV1 content and I've seen RPi Foundation developers comment that SD/720p content should be in range, but not 1080p. As most of the content providers that started to offer AV1 content also provide it in H264 which an RPi4 plays easily, the lack of AV1 (and VP9) is more of a hypothetical problem than a real-world one. HEVC support on RPi4 is excellent.

Quote from lobbie1978

So yesterday I hardcoded EDID by SSH'ing into the Pi while a HDR movie was playing on my projector (TV was off) and programming EDID with getedid create. When I restarted the projector, the AVR and LE, the HDR availability was gone again.

I would keep things simple and capture the EDID direct from the projector without the AVR inline. Check it works over reboots before you add the AVR back into the mix.

Quote from lobbie1978

What would happen if I play HDR media on the TV? Wouldn't the TV just ignore the HDR signal and play content in UHD without HDR?

The RPi4 thinks an HDR compatible panel is connected so will output with HDR. If the TV has HDR > SDR auto-conversion then it would be able to handle the HDR signal and display in SDR, but generally the only TVs that have conversion capabilities are the ones that support HDR. So I think it is rather unlikely that it will be handled and I would expect green/purple tinged and washed colours due to the wrong colourspace.

There's no need to add extensions for flac files, it's one of the defaults. Have you defined the SMB share as a source and scraped the media into the Library? (Music is a Library view). Flac files are similar to mp3 and contain tags that are scraped.

Quote from Da Flex

I would say yes. Hopefully this bug will be fixed in the next stable release. Developers are informed.

There is no bug .. auto-update has not been enabled yet.

All S905X boards use the same Ethernet configuration so that should simply work in all S905X device-trees. Most devices are derivatives of the P212 reference design with few changes so all the core perhiperals will the same. The only major changes are buttons/LEDs .. and sometimes the SDIO WiFi/BT module.

There is no support in the upstream kernel for the RTL8189ETV chip, and I (and rest of the team) have no interest in adding more downstream Realtek drivers (https://github.com/jwrdegoede/rtl8189ES_linux) to the distro image - they're low quality and a pain to maintain. You could attempt a custom build with that driver included. The WiFi part of the SDIO module should probe; SDIO is a bus so connected devices are auto-discovered and wifi@1 reference in device-tree for broadcom chips will also work for Realtek. The BT part of the module will need things to be described correctly in device-tree.