All I can say is .. it's not a software problem. It's about cables and physical connectivity.
Posts by chewitt
-
-
If the box is running Kodi Helix (15.2) I suspect you have a Slice (CM1) device not Slice (CM3) as the CM3 board was launched some time after we forked LE from OE (the original SliceOS was based on OpenELEC) and it's around the time 5Ninjas ceased trading. The simple way to check is the RAM size. If it's 512MB it's CM1, and 1GB it's CM3.
Either way, the original SliceOS was installed via NOOBS, and if you have a working install you should be able to cross-grade from SliceOS to LE after placing the .tar file in /storage/.update, but I would stop Kodi first (systemctl stop kodi) and rename /storage/.kodi to /storage/.kodi-old to move existing data out of the way as it's a large version jump and it's worth spring cleaning at the same time.
-
-
The concept of "pass-through" doesn't exist for video.
-
All the kernel + ffmpeg + kodi patches LE is using are either in the LE repo or the sources URL is clearly listed in package.mk files. In theory there is nothing to stop you replicating the LE experience elsewhere; although note that most Desktop distros are running Kodi via Xorg or Wayland which will create some limiations.
I'm not aware of any "download all the LE stuff for <distro>" tools, but our sources are all in our repo so feel free to write one
-
Is there something I need to do to enable your build(s) to play dolby vision files ? Is there any support ?
You can write code for the Linux media framework and FFMpeg to support Dolby Vision!
In other words, right now there is no support.
-
-
[provider_wireguard]
Type = WireGuard
Name = WireGuard VPN Tunnel <= make this OpenWRT (or WireGuard or anything one-word)
Host = <OpenWRT ddns ip>
WireGuard.Address = <my Client internal IP>/32 <= make this /24
WireGuard.PrivateKey = <client generated Private KEY> <= use the client private key generated by OpenWRT
WireGuard.PublicKey = <OpenWRT Server Public KEY>
WireGuard.DNS = 8.8.8.8, 1.1.1.1
WireGuard.AllowedIPs = 0.0.0.0/0
WireGuard.EndpointPort = WG Server Listening port
WireGuard.PersistentKeepalive = 25
^ OpenWRT prob. generated a set of keys to use on the client end, as that's what's imported when you scan the QR code on a mobile device to import keys and config. So use those instead of generating your own.
-
LE 9.2.8 is the most recent image https://releases.libreelec.tv/LibreELEC-Slice3.arm-9.2.8.img.gz .. there are no LE10 images for RPi3 based hardware at the current time and there are no plans for further Slice images (not enough users to warrant the effort) but some work will be done to ensure the RPi2 image has the needed device-tree bits for it to be convertable for Slice3. NB: Slice3 has the same capablities as an RPi3 so there is no 4K support at all.
-
Just use a current LE11 nightly. The rate of change on Kodi is quite slow and the images are stable.
-
Go read post #2 again.
-
popcornmix .. something missing for RTC in the upstream kernel?
-
https://wiki.libreelec.tv/configuration/edid <= follow the "getedid" instructions; LE10 uses a completely diffferent graphics stack to LE9.2
-
Share the system log (dmesg or journal) after startup.
-
As the title of this thread clearly states your intention to download media using torrent suits, the thread is locked and will be deleted. Pirates are not welcome in this forum.
-
is there a way for me to make it work on 9.2.6?
It can be done by backporting the newer kernel (with drivers that support the newer GPU) onto the 9.2 codebase. There are deliberately no guides and HOWTO instructions on that kind of thing. If nightlies work, you have a solution.
-
It's hard to describe my thoughts. The add-on name sounds like pirate shitware; but choosing dubious sounding names isn't against forum roles. Using a ton of code obfuscation isn't open-source minded, but again we don't have any explicit rules that say this is bad and against forum rules. The "I promise my code doesn't do bad stuff" is probably well intentioned but also seems to send the wrong vibe. TL/DR; it's all probably "legitimate" but my instincts are telling me this is shady and binning the thread will avoid drama.
-
If you poke around in Escalade's GitHub repo you'll find some prior art for adding an NFS server. It's not something we've ever felt the need for in core images as Samba works well enough and most folks will just get confused. FWIW, I've always used SMB and never had any issues (other than occasional self-inflicted mistakes). It might not be "fastest" but it's always been "fast enought" .. over Ethernet of course.
it works here