Posts by chewitt

Quote from FeFiFoFum

Sorry, just to clarify, when Linux 5.2 is the base for Libreelec, that's likely when the os will fully support 4k and HDR with the Pi4?

I'm curious so that I know for future reference. (I may consider a Pi4 then)

LE master branch is already on 5.3 and will bump to 5.4 soon .. but not for RPi4 which needs to remain on 4.19 until more V4L2 plumbing has been completed. Kodi is slowly inching towards HDR support. It's already possible to hack something up that works for some SoCs (not RPi4 yet) but we'd rather do it properly at a more measured pace. I'm not expecting to see "proper" HDR support for some time yet.

I asked one of my kids to guess at the problem, she said there's probably a software issue. It's a vague answer, but without a Kodi debug logfile to show us what's happening (or not) it's as good as any other guess

You can add the Confluence skin to Kodi v18 (from the Kodi add-on repo) but you cannot run Kodi v17 (or older) on RPi4 - core hardware support for the RPi4 does not exist in older releases.

RPi3 and 3B+ have on-board WiFi and it's not brilliant at reception. There are no specific known bugs or things in the OS to exculde support for WPA2, but you might have a bad connection. Use Ethernet or a WiFI > Ethernet brigde if possible. Use some kind of USB external WiFi device if you're forced to go wireless. Or experiment with positioning.

(
sleep 10
systemctl stop kodi
pactl load-module module-udev-detect
pactl set-default-sink alsa_output.0.iec958-stereo
pactl set-default-source bluez_source.74_9E_AF_73_EC_4F.a2dp_source
systemctl start kodi
)&

autostart.sh runs at the start of userspace boot long before Kodi is running so the script will fail. If you (background)& the process with a sleep timer it will run later (10 seconds later in the above example) and should succeed.

N2 has been supported in official nightly images for some time now, but G12 devices still have some quirks in overall codec coverage (e.g. the HEVC firmware is missing). In the next couple of weeks work will restart on video things now the kernel V4L2 stateful API has been documented. Changes for API compliance are being made to the hardware video decoder (and firmwares are being revised) and these changes will need to be accomodated in ffmpeg and Kodi.

FURIxKURI Official Kodi Wiki

The model number is irrelevant. You need to tell us the chipset inside the device. Then we can onfirm it's yet-another shitty realtek chipset that we're not going to add more broken realtek drivers for (which is usually how things pan out).

project: add wireguard package by chewitt · Pull Request #3498 · LibreELEC/LibreELEC.tv · GitHub

^ still a draft PR as other things have a higher priority for my time. It was working a few months ago but needs some fixup changes now.

Support for HD audio hasn't been implemented yet, and since general multi-channel audio is working (on par with RPi3) it's a much lower priority than the major video plumbing work that's in progress. I wouldn't expect it for some time yet.

Quote from FURIxKURI

Good day! guys tell me please. I am a new user of orange pi3 and kodi in general. Since I'm a complete beginner, I barely managed to install everything. two days installed in the evenings after work))) Question! LibreELEC-H6.arm-9.80-nightly-20191022-9abd690-orangepi-3.img.gz can I make it Russian? in localization, only English is available. Thank!

Домашний экран > Add-ons > Download > Look and feel > Language add-ons > Russian > install

Удачи!

Axymeus It's probably more cost effective to re-encode 4K H264 media to H265 so there's a wide variety of usable hardware than build expensive custom HTPCs using the rare parts that can do that natively. How much 4K H264 media do you have? - the only thing I can find with that combination is "Big Buck Bunny" .. which immediately crashed my RPi4 the first time I tried to test 4K output a few months ago

Help will be provided after you go read forum rules again and remove the "XENON build" piracy shitware from your system. Share a Kodi debug log to prove it's clean. Until then .. your problem is not our problem.

Quote from blueribb

Is this website run by LE ?

FTP archive directory /pub/mediaplayer/libreelec/

NLUUG operate an LE mirror so it looks like an alternative FQDN that resolves to the same host.

See libreelec-rpi4.arm-9.1.001.img.gz?mirrorlist

So files should be legit - check the hashes if you want to make sure.

blueribb libreelec-generic.x86_64-9.1.001.img.gz?mirrorlist

I boot tested 9.1.001 on Slice3 before posting the alpha images. At some point soon I will be in Europe and will post the box to HiassofT who is much better skilled at fixing the irregular device-tree breakage than me

VP9: "Currently software decode only. There is a hardware block that can do vp9 bitstream (cabac style) acceleration but the pixel operations need software decode which is the majority of the work." .. my 2c is that VP9 is never seen beyond YouTube which almost always has other (hardware decode supported) streams so it's probably not high on the list of things to spend time upon.

Quote from cheungie

Incredibly exciting news. I wonder whether the device would support things such as Dolby Atmos and Dolby Vision.

I'm told Atmos should be okay. If you aren't using pass-through you'll only get the DTS core (5.1) anyway and if it is being passed through it's not being decoded and thus a license isn't needed. Or something like that .. IANAL