HEVC on G12 hardware will take a while as a 10-bit video pipeline and some other 4K related things need to be completed first. Please stop testing and reporting HEVC crashes until we tell you that it's usable. Currently there is no firmware and it will crash (needing reboot) 100% of the time.
Posts by chewitt
-
-
Win10 requires an authenticated connection so you will need to set a Samba password in LE settings. The samba server is using SMB2/3 so you will need to manually configure the LE source in the Win10 Kodi instance via hostname or IP (and user/pass).
-
It would be easier to just run LE from a USB stick; at the syslink boot prompt (before the installer runs) type "run" and it you'll end up with a bootable USB with persisitent storage. There are threads elsewhere in the forum if you search for them which explain the sequence and bootloader changes needed to dual-boot. It's not something we support (and have no plan to support) as it's not a straightforward process.
-
someone could adapt acestream_3.1.42_Py2.7.16 + _LinaroNDK_webUI_ARMv7.tar.gz
to work on amlogic S812?Anything involving acestream is piracy .. so you are asking for help in the wrong forum.
-
In other news .. we have multi-channel LPCM working on GX hardware. Amlogic's older audio hardware technically supports only 2.0 and 7.1 (2-ch/8-ch) output so the next step will be to fake other output configurations like 2.1/4.0/5.1. No pass-through yet either, but it's a step in the right direction. I also need to test the same changes on G12 hardware - maybe in the next couple of days if I have time. Once current patches are cleaned up a little they will appear in testing images.
-
I have a brand new install of LibreElec on a RPi3. Movies are downloaded by CouchPotato from Thoradia and processed to my usb-hard-drive/movies folder.
In other words you are a movie pirate. You appear to be asking for help in the wrong forum.
-
You're missing the obvious submission of information about the hardware and logs from the box that might help us understand what the issue is. We are not clairvoyant.
-
Show us the whole log file instead of the edited file .. that edited out the bits that help us.
-
No, because the 3.10 kernel codebase is too old to sensibly patch overlayfs support in.
-
Update is part of the libreelec settings add-on, and judging by the bump in users for the latest version that takes place when we enable a release for auto-update the system generally works fine - but you may run into some local issues. Our userbase keeps getting larger and we've noticed the response times for the JSON file that provides available files info are getting slower and sometimes this times out - and my guess (without debug log evidence we can only guess) that the request fails and thus update isn't triggered. There are also some traffic management controls in-place on the update server that you could run into if there are many LE devices in your network, but that's also unlikely. Kodi debug log (as the settings addon runs under Kodi) would be a starting point.
-
720p HEVC media is normally fine and lower-bitrate 1080p will work with a good heatsink, good PSU and some overclock. I'm thinking that 11Mb/sec is probably pushing the board beyond the boundaries though.
-
Index of / has image files, but not add-on files. Old versions of add-ons should still be on the server and will be visible to the OS versions they were compiled for. LE 9.0 will not run old versions compiled for LE 8.0 (when we stopped TVH 4.0 support IIRC).
-
LE ended iMX6 support at v8.2 and Kodi removed all code support for iMX6 as part of the v18 development cycle (it was broken and unmaintained). So i'm not sure what droidbox are testing, but I can 100% guarantee that it's not LE 9.0
It might be possible to reinstate iMX6 support in the future using the next-generation Kodi GBM/V4L2 video pipeline (LE10.0) but last time we checked there were still performance issues with some iMX6 configurations (non-quad ones IIRC) so it's not guaranteed.
-
Another user with the N5 Max 4/32, told me about this build: "LibreELEC-AMLGX.arm-9.1-devel-20190524165808-a41fdf1-box.img"
I don't know WTF is going on with the content of images if people are booting G12 hardware on a GX image.. but to make any progress on creating a device tree for the N5 someone needs to pop the case open and explain which WiFi and Ethernet chip(s) are in the box, and whether it uses internal or external PHY?
-
Differences in boot configuration require you to do a clean install but "backup > clean install > restore" should work fine. You will need to reset the audio config as the device names will change.
-
AMLGX is for GXBB/GXL/GXM hardware
AMLG12 is for G12A/B hardware
-
LE official Amlogic mainline images will be "arm" for libwidevine compatibility so I don't build "aarch64" add-ons for the amlgx repo. Anyone who wants to run aarch64 images are welcome to do so, but you will also need to source/provide your own add-ons. If you already installed the "arm" version of the add-on and are flip-flopping between arm/aarch64 for testing.. the arm addon is not going to work in aarch64 userspace. TL/DR; all bug reports of "no access to tvheadend" will be ignored because "PEBKAC" and it's not a bug.
-
balbes150 revert WIP: drm/meson: fix primary plane disabling · chewitt/linux@076cd72 · GitHub with drm/meson: revert "fix primary plane disabling" · chewitt/linux@8e848fc · GitHub or video only renders when the OSD layer is visible. I flagged the problem to Neil but the commits are still in his branch.
