Hi,
I had something similar, I'm using MCE remotes (HP) and tried to assign a button to open the context menu. When I tried to use the "#" button, in file manager, always opened the "rename" menu instead of the context. Then I tried to use the "yellow" and works perfectly. I think some ("special") remote buttons can't be reassigned in the .xml file. As I resolved what I want with "yellow" button, I didn't continued to search a solution for the "#" button remap...
I am noticing a number of files that work well when they are tested with VLC won't work in KODI. When played in KODI it quickly brings up a black screen that disappears just as quickly. Whole seasons of TV shows don't work in Kodi.
Is the file(s) broken and VLC does something to make them playable, but when used in KODI, KODI can't deal with the "error", so they seem unplayable?
The method how the files contains the video information... Exists a lot of codecs, different resolution, etc. Probably that file use an unusual (old?) video codec what don't supported by video player in Kodi. I had some old video files (old TV show season), what when I played in Kodi (last year, LE10), after few minutes, the video became desynchronized to audio (delayed sound). A quick solution for me was to recode that files using the PC to a recent video codec. The result was some far smaller files, without any quality change. Exists free tools for this. Probably always will be old/exotic video files, that will create player problems in Kodi.
I would also suggest a boot parameter for enabling http? Like ssh?
Use any cheep standard PC usb keyboard. It's need only for first boot, to finish the setup, the SSH setup is part of that. The HTTP remote you can enable as I mentioned before using the keyboard. No need any "boot parameter". And for remote, I like to use the classic IR remote and for RPi is really easy to make it working.
If you don't have a keyboard, probably works with a USB mouse too (for text will appear the virtual keyboard), didn't tried...
Display MoreHello,
I am facing issue with LibreELEC 10.0.4, 10.0.3 and 10.0.2. There are green artifacts over whole screen each 15-30 minutes. This appear everywhere, I mean in live PVR, IPTV, or streamed movies with codec ff-h264_v4l2m2m-drm_prime streams. No issue with 10.0.1 and older. I've tried to search difference between 10.0.1 and 10.0.2 in change log but no luck there.
Running on Rpi4 4GB + Pi TV HAT, max temperature 57°
Any idea what it causing or how it solve? (Instead of downgrade, which helps)
Now I am running on 10.0.1 which has no issues.
Any reply much appreciated
Thank you
Hi,
If the that "greeen artifacts" appears mostly with Live TV, with drm-prime codec and deinterlacing, you should try the latest LE11 beta (10.95.1). If you have a spare SD-card, or make a backup and upgrade... Few weeks ago was added some kind of patch to ffmpeg to improve the deinterlacing (mostly for PVR). I have RPi3B, TVheadend, that "greeen artifacts" what I seen before too, I think now gone (true, I don't spent too much time watching the TV).
The webserver is turned off, so yatse and browser are not working. Remote Control is also not working.
Hi,
For first settings, always better to use a USB wired/wireless keyboard. For remote: go to System - Services - Control and enable the "Allow remote control via HTTP". If appear something about "Authentification", at same page you can enable the authetification (or just confirm if want to use without).
this basically means weak signal
things that could be a problem
- reception is too good and the tuner can't handle that -> attenuator for dvb
- reception is too weak and the tuner can't handle that -> dvb antenna booster
- USB cable has problems, USB switch has some problems -> try other cable or usb ports- driver is not properly working -> good luck
I couldn't exclude the posibility of the defective DVB device, even if new and Hauppauge.
If you can, try with another laptop/PC and/or another OS (Linux, Windows) to check if the hardware itself is working well.
If you know what is working well, you are a step closer to find the problem.
Yep... It's on...
Based on the output of running SSH, it seems it's a windows issue, not a KODI problem..
Which probably means I should be asking in a windows forum, but..
I'm using MobaXterm for terminal (and for litle upload-download) and Filezilla for SFTP (SSH File Transfer Protocol), now with Win11, worked well before with Win10 too. Don't remember to had any SSH issue with Libreelec.
Hi, I'm just asking.... in the Settings - Libreelec... the SSH client is enabled (disabled by default).
Uhm, no further comments, so I really understand the issue is within LE and I need to wait for LE11?
Yes, the "famous" deinterlacer in the LE10 and LE11.
Was added in the LE 11 nightly, to the ffmpeg, some kind of patch for better handling the deinterlace (the LE11 beta 10.95.0 don't have it, don't know if in the LE10 nightly was added or not). Make a backup (or better use another sd-card) and try the latest LE11 nightly, maybe you will see some improvement.
I'm using 3 RPi3's, one with LE 10.0.4, two with LE11 nightly. For FHD live TV streams (h264, tvheadend), in case of LE10, sometimes appears some green artefacts, only for milliseconds, at the bottom of pictures. With the LE11 nightly, instead of green artefacts, some pixelation appear sometimes, mostly when major changes in the picture. L11 nightly with HD ready display (720p, the third RPi3) works better. I still have some SD channels, with mpeg2, works always without issues (RPi3, no HW decoding for mpeg2).
Thanks for the advice. When I go to nightly downloads, do I want the 10.0 nightlies or the 11.0 nightlies to update my version from 10.95.0? I'm a little confused about the naming sstructure and which I'm currently on!
I don't know if you can return (downgrade) to the LE10 without problems. To move from LE11 beta (10.95.0) to nightly it's working, at least I didn't had any problem with that. I copied the LE11 nightly package to the /storage/.update/ folder and reboot. I have 3 RPi3, two with LE11 nightly (LibreELEC-RPi2.arm-11.0-nightly-20230208), one remains yet with LE 10.0.4, I didn't seen any significant difference as normal user.
I've since installed the original card and have wifi again, however libreelec keeps restarting randomly and I'm not getting picture on some live TV channels (audio works) that used to work. I'm thinking it could be related to the upgrade from 10.0.4 to 10.95.0? Is there any clues in the log file of what might be causing the restarts? http://ix.io/4nBR
Hi,
First... before any upgrade... BACKUP! It's took a few minutes, but sometimes save for you hours of reinstalling everything.
About LE11 beta, if you already upgraded to LE11, try the latest LE11 nightly, that first LE11 beta (the 10.95.0, the 10.95.1 what is in the chewitt's post, I think isn't released yet) have some issues with live TV.
And about the wifi card, you didn't mention your hardware, perhaps you can try to run an live-linux from usb (Ubuntu iso written to USB-stick) to verify if the suspected card is working or not.
Hi,
I have 3 RPi3B's, all with IR receiver connected to GPIO pins, and old HP Media center remote (RC6 protocol as MCE remote).
I'm using some buttons remapped, the "Power" to send the specific "Power" IR code for my TV (GPIO IR Diode), "Pause" remapped to "Stop", and the "subtitle" remapped to "PlayerProcessInfo" in case of playing media and to "ContextMenu" for anything else. And all is done using this remote.xml file in userdata\keymaps:
<?xml version="1.0" encoding="UTF-8"?>
<keymap>
<global>
<remote>
<pause>Stop</pause>
<power>System.Exec("/storage/.kodi/userdata/TV_Pwr.sh")</power>
<subtitle>ContextMenu</subtitle>
</remote>
</global>
<FullscreenVideo>
<remote>
<subtitle>PlayerProcessInfo</subtitle>
</remote>
</FullscreenVideo>
</keymap>
The "TV_Pwr.sh" is for sending to Kodi a player-stop command (kodi-send --action="Stop") and send the IR code for TV (ir-ctl -S nec:0x408 -S nec:0x408 -S nec:0x408 -S nec:0x408 -S nec:0x408 for my LG).
If your remote codes is recognized (as standard protocol: nec), did you tried to use only your remote.xml (...<one>seek(-15)</one>...) without anything else?
I've upgraded two Raspi4 from 9.2.8 to 10.0.4. One works just perfectly fine but the other one has some funny issue. After playing a file for quite some time (>30 minutes at least) the video somehow gets out of sync, it stutters for a short moment, then plays way too fast to catch up with the sound to stutter again and so on. This happens until playback is stopped. When restarting the video from the previous position, everything is fine again for some time before the issue comes up again. This happens for different formats, for example mk4 or ts streams so I would guess that this is not file related but some LE/Kodi issue.
Is there any setting I could check or could the Raspi be damaged?
I had too some strange audio-video desync...
At system display settings, try to change the display resolution, use same resolution with another frequency, ex. 1920x1080p 60Hz change to 1920x1080p 50Hz. As you have two RPi's, both display have same settings?
At least, that was the solution in my case. I think sometimes the player unable to correctly handle the "conversion" of movie resolution-FPS to display's FPS.
This is not quite correct, the kernel update PR (which fixes glitches on all RPis and "no signal with some TVs on RPi4) and an ffmpeg patch update (which can potentially fix playback issues) were merged after 10.95.0 was built
https://github.com/LibreELEC/LibreELEC.tv/pull/7426
https://github.com/LibreELEC/LibreELEC.tv/pull/7410
so long,
Hias
Hi,
Thank you for informations, that ffmpeg patch could be the difference.
I had picture issues with theadend stream, h264, fullHD and the "famous" deinterlace...
Works far better with the LE11 nightly (LibreELEC-RPi2.arm-11.0-nightly-20230129, device: RPi3B+).
Select manual updates, change to the LE11 update channel, then select/download the 10.95.0 update and reboot.
Make backup before update to 10.95.0!
I tried (RPi3B+) and after a day changed back to LE11-nightly, far better.
Well it is a Raspberry Pi 3B, if i am not mistaken it is not fully supported by the latest version. There may be some incompatibilities. Anway, it is no big deal. I will just turn it on after i turn on the tv
I have 2 RPi3B and 1 RPi3B+, all have the edid data saved and didn't seen any issue because that. I think that edid data is used only at startup, instead to be read thru HDMI cable. And probably starting with the LE10, is the only way the RPi-LE to "know" what display have connected even if the display is switched off.
And I'm waiting too, for to be the RPi4 available again on the market, without waiting time or too high price.
Can anybody confirm that this release actually reads the config.txt. Because even when i add the line "hdmi_force_hotplug=1", i can't get any output on my tv if i turn the tv on "after" the pi. That wasn't the case before. After adding this line, i could turn the tv on anytime (before or after the pi is on) and could get tv output. Now i have to first turn the TV on and then plug in the pi. Which makes me think that this version ignores the lines added to config.txt.
Hi,
Start with TV on, SSH to RPi and use the "getedid create" command. That will save your display/TV parameters and will use it at every startup (even if the TV is off). If you want to know more: https://wiki.libreelec.tv/configuration/edid
Display MoreHello,
as I installed LibreELEC 9.x on a Raspberry 3b as an IPTV for my Mum, I ran into a problem:
If the Raspberry is turned of by a switch socket (or e.g. after a blackout), on the new start the wifi will not connect automatically. I then have to access the option entry and manually connect to the wifi, which is quite impractical as I'm not always around if this happens.
The goal is to use LibreELEC/Kodi as a turn-on-turn-off TV, which would be the perfect solution but with this issue it seems unpossible for now.
Is this a known problem or do I miss something?
Thank you for any advice!
Hi, Check if at "System-Libreelec-Connections-Yourconnection-Edit" the "Connect Automatically" is enabled.
Many times when the network connection is edited, that changing to "off" and need to enabled again.
