Posts by ghtester

Yes it's possible to have a video on HDMI0 and audio on HDMI1 when running LE (at least it works with test build 9.80 nightly, not sure about official LE 9.2.6) on RPi 4B.

This looks OK, focus on Infra-Red Remotes - LibreELEC.wiki section (file paths) and compare files from working / not working LE installations. Then copy the appropriate configuration / mapping files from working LE to not working LE (to overriding paths in /storage/.config...)

Use putty (putty.exe) or another SSH client to connect to your RPi 4 ( the SSH service needs to be enabled in Settings / LibreELEC / Services ), username = root, password = libreelec , then use nano editor to create or edit existing autostart.sh file:

nano /storage/.config/autostart.sh

There are plenty of dead links to wiki.

For instance:

Dead links from boot/config.txt :

https://wiki.libreelec.tv/index.php?title=LibreELEC_Settings

https://wiki.libreelec.tv/index.php?titl…_USB-SD_Creator

https://wiki.libreelec.tv/index.php?title=Config.txt

Dead links from Where is config.txt :

https://wiki.libreelec.tv/index.php?title=Config.txt

https://wiki.libreelec.tv/index.php?title=Main_Page

https://wiki.libreelec.tv/index.php?title=Main_Page

https://wiki.libreelec.tv/index.php?title=Raspberry_Pi

https://wiki.libreelec.tv/index.php?titl…&action=history

https://wiki.libreelec.tv/custom_edid#tab__intel

Dead link from ssh password :

https://wiki.libreelec.tv/index.php?titl…ssing_LibreELEC

Dead link from problem second monitor

https://wiki.libreelec.tv/autostart.sh

Dead link from problem with "longpress" actions in keymap.xml under LibreELEC (Leia) v8.90.009 ALPHA

https://wiki.libreelec.tv/infrared_remotes

Dead link from Libreelec on Pi 4 Cooling Fan control

https://wiki.libreelec.tv/config.txt

Perhaps some global check could be applied to forum contents?

So if the issue is still the same after reboot, it looks your LE installation is somehow broken (maybe the SD card issue) because this problem does not happen on a clean LE. Check the dmesg output if there're some errors, the few published lines from kodi.log does say nothing.

I am usually using just:

reboot

or (if Kodi is running)

kodi-send --action="restart"

Official:Forum rules/Banned add-ons - Official Kodi Wiki

In LE 9.2.6's Kodi audio settings (Settings - System - Audio) you can even select that both analog jack and HDMI are active for audio output at the same time and it was working fine on my RPi4 (but I did not use that add-on as you mentioned). So you can perhaps try that settings.

Now I am using LE 9.80 nightly where it's a bit different (and there's not possible to activate the analog and HDMI at the same time for audio output) but setting regarding to preffered audio output works fine there as well.

Quote from peram1

for sitiuations like these would be really good having an archive of nightlys ... and not everybody has to keep his "last known good by himself"

... and moreover far more constructive, friendly and helpful than: "get yourself a PI", "install regular linux" ...

what's so difficult in having an archive of nightlys ?

Do you even understand what "nightly builds" are?

From my point of view, we should be grateful to developers for publishing them at all.
What prevents you from setting up this archive if you think it is needed? In my opinion, however, it would be a waste of space that someone has to pay, because hosting is not free.
Everyone can (and should) keep the previous functional "nightly" version + configuration backup and as you can see in the very first post, it happened here as well.

Start reading here:

Infra-Red Remotes - LibreELEC.wiki

And focus on file names / paths.

In LE 9.80 the mapping files have .toml extension and a slightly different structure but the general rules are the same.

OK, so what if you try to unload the module:

modprobe -r snd_bcm2835

or

rmmod snd_bcm2835

Or comment out by # this line in /flash/config.txt:

dtparam=audio=on

Yes I can confirm it works fine if you push 'o' button on keyboard, it can also be displayed / hide with console commands:

kodi-send -a 'Playerprocessinfo'

or

kodi-send --button=o

The debug info can be activated / deactivated through CTRL+SHIFT+O

or by:

kodi-send -a 'PlayerDebug'

Quote from Muffy

The PI 2 had some problems with 1080p streams. After a overclock and turning off de-interlacing, it runs finally smoothly.

The Pi 3 had never such issues. It runs perfectly.

The Pi 4 has still some jittering/running on slow motion and the GUI has some flicker problems.

...

Overall, nothing really works. The GUI flickering is still a problem and UHD streams are still running not smoothly.

Could it just be a big malfuction at all PI4s beause even after a years, there is still no real funcional graphics driver?

Display More

You don't say which LE you are running and which stream is it and it is very important to know what's a current capability of your HW and SW to achieve expected results.

I wouldn't say all RPi 4 devices are malfunctioning, it's a great piece of HW for such a low price. Most likely, as it is still a bit new device, the SW still needs to be finalized to fully utilize the HW. RPi 3 is already finished in this matter, RPi 4 not yet but the developpers are doing a great job and there are many updates in nightly LE builds so it will be better and better
Read this post, it's from January so may not reflect the progress, but you may learn something: RE: Raspi 4B 4G stuttering + tearing

Quote from harry_fine

How do you disable one tuner, other than through the tvh software which likely doesn't turn it off, it just doesn't use it?

Yes, if the utility software (through which you are changing the transfer modes etc.) does not allow to do it at hardware level, at least in Tvheadend server uncheck Enabled: checkbox for one of demodulators in Configuration - DVB Inputs - TV adapters - ....ATSC#2 - Basic settings

It should be possible to do it somehow at driver level but can't say how-to details remotely.

Quote from harry_fine

JO above talked about the the Si2151 as being a very compatible tuner, but I can't find it anywhere to buy.

Si2151 is a radio chip inside your (and many others) TV stick, it's not a complete TV tuner.

OK, thanks a lot for your reaction.

The seeking issues I have encountered were like sometimes the 'cursor' jumped outside the Timeshift window borders when I tried to move back or forward and then it was jumping back only (to nonsense minus values) even if I wanted move forward. So the only solution was to stop playing the channel and start again (so whole Timeshift data were lost).

I would say that main reason why it happens is a temporary bad signal (this happens as I have indoor antenna only) so the data stream suffer some corruption. Then also the Timeshift may have unpredictable behavior (but should not perhaps jump outside borders anyway). I'll see if there's any change in latest builds or not (I understand it should be still the same for H265 but who knows ).

I still had an occasional seeking issues with H265 (using Live TV and Timeshift in RAM only) on recent LE 9.80 nightly builds, I supposed to be the Tvheadend 4.2's issue but perhaps I don't understand how it works together...

It's a bit older thread and I have not tested if it's still valid but you may try:

RE: Can I add WiFi config to SD card pre-install? (headless setup)

If you can't change the wi-fi password at all (at least temporarily), you may also finish the setup with some another / temporary wi-fi AP, perhaps using mobile hotspot at your phone. Then maybe connect through SSH and try steps outlined here (but it's even older thread):

enter wifi password by SSH

I can confirm an issue with special characters that can't be used also for 'tethered' Wireless Access Point names.

Quote from JonasStax

...the tuner functionality in LibreELEC is passing a signal.

Well, in general it's true but I don't think the tuner itself is an issue here.

More likely the demodulator LG LGDT3306a or the Empia EM28274 USB controller which may need a specific settings. I would say it should be possible to make this stick working properly but it's necessary to try everything we recommended here... Connecting through an USB hub with external power supply. Try connecting to both USB 3.0 / USB 2.0 ports. Try both bulk / isochronous transfer modes. Try disabling one tuner. Try another LE build (newest 9.80 nightly or an older 9.2.5 with CrazyCat drivers). And try all possible combinations... Yes it's a lot of testing to do but there should be a solution.