It's on by default and accessible with libreelec/libreelec credentials. You can change that in the LE settings add-on. If you want to fiddle with deeper samba features you can rename /storage/.config/samba.conf.sample to samba.conf, make edits, then reboot and your conf will be used instead of the embedded one.
Posts by chewitt
-
-
Can I do this with libreelec?
LE runs a Samba server in the background, so shouldn't be an issue.
-
Have you tried a different USB flash drive?
-
would really appreciate if LE or the ConnMan developers consider to give LE such a basic functionality back.
We have not 'removed' anything that broke proxy support. Proxying in Kodi works. Proxying in the OS works too, but proxy config methods are application specific (not OS-wide/catch-all) so you will need to follow whatever conventions the apps require.
TrinitronX /storage/.profile can be created and used with LE for interactive shell config. If you want to export the variables to the system environment on boot this should be achievable from /storage/.config/autostart.sh.
-
Thanks for the confirmation, good to know it works
-
darktigrous I've pushed updated images to my webshare that should contain the dtb files again. I'm interested to know whether this is working or not as I've rather forgotten status of things recetly (work/life is rather busy).
-
Probably best to report/flag to the devs working on inputstream.adaptive in the Kodi forums. It looks (to my very-ignorant on the topic eyeballs) to be something unsupported in the stream manifest which results in a stall, and then a recovery.
-
This PR will add support eventually add support: https://github.com/LibreELEC/LibreELEC.tv/pull/7864 - note that the RK3588 device does not have HDMI support currently (will come in a future kernel bump) and the PR is already 18-months old, so unlikely to be merged soon.
-
If you're already using the autostart.sh file, you might as well add the workaround there too, no?
-
Code
2001.A.Space.Odyssey.1968.UHD.BluRay.2160p.REMUX.Dolby.Vision.DL.DTS-HD.MA.5.1.HEVC.HUN-TRiNiTY/2001.a.space.odyssey.2160p.dolby.vision.dl.remux-trinity.mp4You stole movies in the wrong format.
No further support.
-
ConnMan manages /etc/resolv.conf and assumes ownership so manual edits can be overwritten at any time. If the host has a static IP assignment it's probably easiest to add an entry in /storage/.config/hosts.conf and reboot.
-
I didn't see anything banned, but it's not a debug log and there's nothing obvious in the log .. hence 'nope' answer.
-
can you describe what happened ?
Nope.
-
Kodi allows you to fiddle with the type of input stream that uses buffering (it differentiates between online and several different types of local sources), the size of the buffer, the buffer fill-rate, and (separately) the SMB/NFS read-chunk size. Note that since K21 the buffer settings have all moved into the GUI so config in advancedsettings.xml will be correctly ignored.
Users generally (and wrongly) believe that "bigger buffer is better" but when you have insufficient bandwidth the buffer always drains to zero and then you stall playback until the buffer is full again and can resume. Having a larger buffer or a slow fill rate means you will wait for longer before playback resumes. Fast fill rates also imply the availability of faster/higher bandwidth. In practically all scenarios, smaller buffers and moderate fill rates (small changes on defaults, not radical ones) give best results.
NB: Cache tweaking is never a cure for "insufficient bandwidth" and you will probably spend more man-hours of effort trying to find a combination of settings that is best (or least-worst) than it will take to fix the real problem: the NIC is negotiating 100-BaseT not 1000-BaseT. Check the router, switches, cables, ports, etc.
-
RPi5 2GB is our minimum recommendation. The 4GB/8GB board variants aren't necessary unless you want to run other services in the background via Docker or add-ons.
-
RK3588S2 is merged to mainline kernel 6.3.
Current state for RK3588 upstreaming is tracked here: https://gitlab.collabora.com/hardware-enabl…nline-status.md - the Mali GPU has been supported since Linux 6.10 but LE images also need HDMI support (1080p is merged/queued for Linux 6.13) and once 4K is working we'll need HEVC/VP9 media codecs working (WIP).
It has platinum support in Armbian.
Feel free to use Armbian then. It's a project that undertakes commercial work to support devices; meaning they will tolerate vendor kernels with horrible code and patching to make something work. Their primary user audience is developers of industrial products who have use-cases that don't need media features, and hobbyists needing a desktop environment who again aren't so needing of the media capabilites. I have no knowledge of the current state of their RK3588 support .. but since most of the media stuff is simply not upstream yet, they are either managing a load of WIP patches and/or the media features aren't in great shape.
RPi5 proves that a fast board can handle software-decoding everything at 1080p so a little patching on Linux 6.12 can probably result in a usable but basic LE image, but I doubt anyone on staff or community will take serious interest in trying to assemble images until HDMI 4K support lands. So the realistic target will be after LE13 ships (2025/Q1).
If you want a functionally complete and well supported SBC for LE use, it's an RPi5. The 2GB board is enough for normal use. You only might need more RAM if you want to run Docker containers with other services in the background. The spec on paper isn't as impressive as the Rockchip board, but it shipped with functional support on day1 of release vs. RK3588 is now 3-years on from it's release and the board only just got upstream HDMI support. Hardware specs are nothing without supporting software
-
If it's a small library and you're planning to move content over from USB drive to the SSD it's probably easiest to move the content over and rescrape everything from the new location.
If it's a larger library and/you care about the watched status, the following /storage/.kodi/userdata content can be copied over:
- DB files
- sources.xml
- passwords.xml
- addon_data
- thumbnails
As the original /var/media/USBDRIVE path will have changed to /storage/videos/something you will need to use path substitution to map old paths to new ones, see https://kodi.wiki/view/Path_substitution
NB: No add-ons can be copied over as LE9 uses Python2 and we switched to Python3 since then.
-
Interesting. I suspect the solution is in the AVR config options then. Perhaps the port is tagged for some specific output/purpose and isn't doing the usual "mirror upstream capabilities" that normally happens.
