Posts by HiassofT
-
-
This is a question only the developer of the VPN manager addon can answer - it's not an official LibreELEC addon.
so long,
Hias
-
-
Don't worry about automatic updates, we only enable that for minor version updates (eg 9.2.5->9.2.6). Major version upgrades (eg 9.2.x->10) need to be done manually.
You haven't mentioned which platform you are using, but if you are using an RPi then, yes, hyperion won't work on LE10 as hyperion(ng) doesn't have a working grabber for that yet.
On Generic//x86 the hyperion addon with the X11 grabber should work as before.
so long,
Hias
-
There's a PR to add hyperion ng BROKEN: Hyperion-NG by CvH · Pull Request #4673 · LibreELEC/LibreELEC.tv · GitHub but currently there are major issues in building it and it doesn't work.
As neither hyperion nor hyperion ng support GBM yet Raspberry Pi 4 with Libreelec v19 / Kodi Matrix, no grabber is working · Issue #983 · hyperion-project/hyperion.ng · GitHub it's quite useless for anything other than X11 on Generic/x86 platforms or external video grabbers in LibreELEC 10. As we'll be using GBM on all platforms except Generic/x86 in LE 10 it's quite low on our priority list ATM.
Any help (PRs, fixes, etc) would be highly appreciated though, if the issues are resolved then hyperion ng will be included in LE.
so long,
Hias
-
Question: is a SD moved from RPi3b it supposed to boot on RPi4 ?
No, not without quite a lot of hassle.
In the end, it will be a lot easier and safer if you just start from scratch with a fresh RPi4 installation.
so long,
Hias
-
Interesting, kodi-autostart.service seems to be pulled in by kodi.service, not kodi.target (which is a bit unusual...).
To get it back with kodi.service mask the following command should to the trick:
For filesystem mounts it's better though to use mount units, see eg the nfs/cifs mount samples in .config/system.d and the mount unit documentation systemd.mount
If this filesystem is used for tvheadend recordings I strongly recommend ordering the mount unit before service.tvheadend42.service so the filesystem will be mounted before tvheadend is started.
so long,
Hias
-
Format/Info : Advanced Video Codec
Format profile : High [email protected]
Like most other devices RPi doesn't support hardware acceleration for 10bit H264, so it has to be decoded in software.
so long,
Hias
-
Ah, sorry, I totally missed that you are not using an original Hifiberry card. In that case you'll have to contact the respective manufacturer of course, he's probably the only one who knows the implementation details about the card.
so long,
Hias
-
As I already wrote here RE: Should I change to Rpi 4B? contact the Hifiberry folks. Something is off either with your RPi4 or the soundcard.
I just tested with a plain LibreELEC 9.2.6 installation on a RPi4, plugged in my Hifiberry Digi Pro and it was detected fine.
so long,
Hias
-
[ 5.242057] wm8804 1-003b: Failed to read device ID: -121
[ 5.242252] wm8804: probe of 1-003b failed with error -121
Remove the changes to config.txt and double-check if the card is plugged in correctly. The Hifiberry Digi Pro should be auto-detected and work out-of-the box.
If the error persists contact Hifiberry. The dmesg lines indicate there's a communication error with the wm8804 chip which could indicate a hardware fault.
so long,
Hias
-
-
inputstream.adaptive is in the LibreELEC addon repository (in VideoPlayer InputStream).
so long,
Hias
-
use the "-p rc-6" option. Please read through the IR wiki page, it's all explained there in detail Infrared Remotes [LibreELEC.wiki]
so long,
Hias
-
With ir-keytable you have to specify the rc device, "rc1" in the case above, using the "-s" option. eg ir-keytable -s rc1 ...
Note that the rc device numbers may change across reboots so always check with "ir-keytable" before.
In rc_maps.cfg you can match by driver name, that's the first entry. eg
That being said, using the nuvoton CIR would be a better choice (if it has an IR receiver connected) as it supports more protocols - the imon receiver is quite limited...
so long,
Hias
-
Ahem, why did you mask lircd-uinput? This is definitely not a standard configuration. Run systemctl unmask lircd-uinput and reboot.
so long,
Hias
-
No, that's not normal, lircd-uinput is missing in the process list. It should look like this:
CodeLibreELEC:~ # ps | grep lirc 316 root 0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/run/lirc/lircd 448 root 0:00 /usr/sbin/lircd -O /storage/.config/lirc_options.conf --nodaemon /storage/.config/lircd.conf 450 root 0:00 /usr/sbin/lircd-uinput -O /storage/.config/lirc_options.conf --add-release-events 846 root 0:00 grep lirc
Post the output of systemctl status lircd-uinput and make sure you didn't mess around with lircd after reboot (i.e. no killall lircd or systemctl stop lircd, this will break lirc operations).
so long,
Hias
-
Make sure lircd-uinput is running - if you restarted lircd you'll also need to restart lircd-uinput, or just reboot your system.
Then you should also see button presses on /run/lirc/lircd (via irw) where kodi picks them up from.
so long,
Hias