IR controllable power socket? https://www.ebay.co.uk/itm/284397741540
Posts by chewitt
-
-
Absorb those bits ^ to the custom samba.conf then reboot and try to connect again. Working?
Nothing changed in Samba or our Samba config for aeons but if this is a removable drive, is it NTFS formatted? .. because we switched from using FUSE to native in-kernel NTFS drivers since LE9.2 and that may explain the difference in behaviour.
-
Please forgive my ignorance, but what do I need to instal for my Mecool M8S PRO L? Also on another note, is it possible to install these images on the internal storage instead of SDCARD?
Q1 - Read this wiki article https://wiki.libreelec.tv/hardware/amlogic
Q2 - No. Read the statement at the bottom of ^ that article
-
Just take a backup using the LE settings add-on and move the tar archive file somewhere safe. Clean install using the latest nightly image, and if things like previously watched status are super important to you; then put the file on the new install and manually unpack it somewhere to allow simple restore of things to where they need to be in the filesystem (easy to Google for that info). If you're not bothered with status then just go about setting up sources and scraping media again. I would caution against simply restoring the backup as a) this will restore Python2 add-ons to a system that no longer runs them and this is a frequent cause of update issues, b) most installs will benefit from not restoring the accumulated years of cruft from the old install (spring cleaning).
-
Any hints and ideas welcome. Would like to get this running asap.
Any difference with LE 10.0.4? .. or this nightly? RE: LE 10.0.1 / Rpi4 / No picture after update from LE 10.0.0
-
Kodi 20 stable is ready! We will be very happy if you (chewitt and the other LE team members) include all this Amlogic fixes and tweaks in LibreELEC stable release. Thank you for your support and good attitude towards us - the common users.
Current plan is to resume support for GXBB/GXL/GXM devices. Images are not perfect but more than usable for average users with average media media collections that are mostly 1080p based, although S905X/D and S912 do support 4k/HDR playback. The same images can be installed on newer devices but the hardware decode drivers have greater issues on newer hardware so those are really limited to software-only decoding (1080p max) and to set low expectations and keep things sensible we will state those are not supported. All recent changes in my branches are upstreamed to GitHub master branch yesterday. There is still more general stuff to get shipshape before an LE11 release can be announced .. I'd expect another 7-10days is required.
-
Are these FFMpeg changes already in the last image on test.libreelec.tv or only on chewitt.libreelec.tv? Would you mind writing who is behind these changes, someone has taken it upon themselves to fix it, or maybe it's to your credit?
https://github.com/LibreELEC/LibreELEC.tv/pull/7387 was merged yesterday along with a few other things so the next round of images on the test server should contain the same content as the images on my share. The FFMpeg changes are by John Cox @ Raspberry Pi foundation. He is not working on Amlogic support, but we have common goals for v4l2_m2m support in FFMpeg and care that the current codebase that he is working on supports a range of SoCs and not just RPi boards. To further that I regularly test his experimental changes and provide feedback (especially when regressions are involved). In this case, a change made definitely helps with HEVC seeking. It's not a full fix though; that will almost certainly need changes to the kernel driver (which is lacking developers for aeons) but an improvement is still an improvement.
-
-
When I put the 4 files from LibreELEC-RPi4.arm-10.0.4.tar into the update folder on the RPi and reboot it objects to one of the updates as having an incorrect md5 sum. I checked the md5 sum was correct before trying again but still the same error.
Just use the settings add-on. Put it in manual udpate mode and select the 10.0.4 file and let it download clean. Working?
-
Will LE11 be an update for LE10.x or will a clean install be advised?
You can update from LE10 to LE11. You cannot (or should-not) update from LE9.x or earlier to LE11 due to Python3 changes.
-
I can see the drive being detected, mounted, and samba services starting. No errors .. so no idea what the issue is
-
It looks like have reused an existing drive that's had Kodi installed (as without a GUI you wouldn't be able to install a pile of add-ons) so this ^ moves all Kodi configuration, add-ons and such out of the way to give a clean/vanilla Kodi instance. You can always stop/delete/move things back as they were. Does it work now?
-
Kodi caches the repo to reduce requests on infrasttructure so you may need to right-click and force the repo to be refreshed before the new add-on version will be shown/seen locally.
-
Kodi accesses media from "sources" and sources can be configured with different scraper settings. So you can have a source for commercial movies that uses the established conventions for filenames and online scraping and works with the TMDB scraper, and a separate source that uses the "local" file scraper only; that can reference local .nfo files and artwork created for each movie.
If you want personal movies to appear in a library view, the movie must be scraped to the library and that means the local file scraper requires a local .nfo file to scrape content from. Kodi itself will not auto-generate .nfo files but LE being Linux and thus scriptable (and with cron if the script needs to run repeatedly) it's not hard to script and automate creation of a basic .nfo files with minimal content. If there is no matching artwork for the local movie Kodi will grab a frame and show it, though the results can be a bit random.
The alternative is to access personal movies from the "Videos" menu. If you are accessing a source that has also been scraped to the Library Kodi shows the Library content overlaid, but otherwise it's just a raw view of files in folders and Kodi shows the filenames and a frame that has been extracted from the media file. This seems to be what you're looking for?
-
I store media on a NAS box in the network. The NAS shares files over SMB and has an SQL database so that I can start any LE client device in the network and see the same DB content. It also runs a Plex server because I spend lots of time in Hotels and Plex nicely handles transcode of media to different resolutions or quality levels to suit the sometimes limited bandwidths available. Plex also allows kids to play media from the native Plex app on a moderately-smart TV in their bedroom. The Kodi and Plex DBs are separate (not sync'd) because that's not important to me, but it's possible to use LE/Kodi as a pure player device for Plex using the Plex client add-on. There is also an add-on that syncs the Plex DB to Kodi so you have a native Kodi database but referencing the Plex-stored media.
It's technically possible to convert an RPi board to be the NAS, but my advice would be "If you want a NAS, get a NAS" as at some point the effort involved and better performance and reliability of a proper NAS outweighs the savings of using an RPi board.
-
Direct updates are not supported. You need to follow a backup > clean install > partial restore process.
Take a backup of essential things: sources.xml, advancedsettings.xml, add-on settings and DB files from Kodi. Download the latest nightly from https://test.libreelec.tv/11.0/Amlogic/odroid-c2/ then create a new SD card or reimage the emmc module. Then boot, stop Kodi, move the essential things you backed-up to where they need to be. Restart Kodi and start reinstalling add-ons.
-
-
I'm not sure why it's failing when the system was booting from the same SSD before. If the APPEND line in syslinux.cfg (on the SSD) shows boot=LABEL=LIBREELEC or boot=GUID=<long-guid-string> perhaps edit it to use boot=/dev/sda1 disk=/dev/sda2 instead. You can also try booting from an Ubuntu USB and using that to write the LE installer image directly to the SSD, then boot and run from itself (prob. called run from USB or such - it's years since I booted/installed Generic so I forget).