Posts by chewitt

Virtual is used daily by developers and is a valid project to use as an example. I added WeTek_Play_2, WeTek_Hub and Odroid_C2 to the page.

If you update using the .tar file in Index of /slice/ (same filename but newer file) the images now have Gordon's audio fixes included and analogue should work?

If our software accidentally doesn't like pirate add-ons, that's great, and I won't be encouraging anybody on staff to investigate

If you connect the HTPC directly to the TV this does not occur?

edit4ever: if the code in your add-ons is stable you're welcome to submit them to our repo, or if you need some webspace to publish your own repo instead of using dropbox links (and then add your repo installer to our repo) to make updates easier for users; let myself or other staff know.

The thermometer is only on when software decoding on the CPU. Current testing suggests 720p H.265 media (H.264 from the BBC converted with HandBrake) is perfectly okay but 1080p is borderline and drops frames in panning scenes. I'll see what I can bits I can fettle into a heatsink over the weekend

Something is borked on the Kodi servers. If/when/once they fix that it will work normally. Until that happens you'll need to either wait patiently or do the manual thing above.

LibreELEC.tv/kodi-100.08-setup-timezone.patch at master · LibreELEC/LibreELEC.tv · GitHub
autostart.sh

You need to set a value in /storage/.cache/timezone containing the timezone. I'd do this with an embedded autostart.sh script that detects whether that file already exists, and if not (which would be first boot) creates it to set the value.

Home · Zomboided/service.vpn.manager Wiki · GitHub .. follow the install instructions

If you (we) figure out how to autodetect the MAC address this could be something we bundle in to the distro?

Like RPi3 the CM3 has no hardware decoding support for H.265 and with the stock config.txt it can *almost* handle the format in software. If you apply a little overclock in config.txt it seems to cope. I haven't found the time to convert a large 40GB-ish Blu-Ray rip for testing but for normal HD broadcast things I record from the BBC and a couple of other online places it's been fine. NB: The thermometer icon shows permanently in the top-right corner of the screen due to the CPU load but Gordon has voiced good results adding a small passive heatsink, so that's on my to-do list.

"back in the day" when people spent hours in forums debating the merits of class10 cards over class4 etc. there was some value in splitting things over a USB, but if you have content on a NAS and with a decent branded 8GB SD card costing $peanuts, the extra hassle it brings around updates isn't worth it IMHO.

This is a LibreELEC image for the FiveNinjas "Slice" box based on the standard RPi and RPi2 image(s) with patches to support the CS4265 audio DAC and WS2812 LED ring in the Slice box. Other features like lirc disable and log submission have been incorporated into the main LibreELEC image. As the original SliceOS skin was never updated for Krypton (and has font licensing issues) the image uses Estuary. To achieve a more Slice-blue look set the "midnight" colour scheme.

GitHub sources for the images are normally up to date here: GitHub - chewitt/LibreELEC.tv at slice-8.0

Instructions for updating SliceOS and clean-install images for CM(1) and CM3 cards are on the website: downloads – LibreELEC

NB: Please post all questions to this thread. I will not answer PM messages!

Enjoy

Please post C2 issues to the General support forum LibreELEC where previous threads have been moved. The main reason for the change is wrxtasy needing to concentrate support threads from multiple forums (WeTek, HK, here) into a single place for his own sanity; plus we are moving towards Krypton where his efforts will be directed towards our official builds rather than doing something off-piste on his own.

S805 builds are 32-bit "arm" while S905 builds are 64-bit "aarch64" so things are not compatible. There is ongoing development in a couple of corners from team staff, but really we're waiting for Kodi to forks the v18 branch; then the rest of the retroplayer code will be committed.

That URL contained private builds that were not for public consumption, hence it has been changed.

Random guess; in LE settings use the badly named "wait for network" and put a 10 second startup delay. This setting actually has nothing to do with networking and just delays Kodi start by X seconds. I'm wondering if the audio driver needs more time to initialise before Kodi starts and auto-detects audio capabilities.

OSMC boots slower than LE and this is ultimately all about timing/sequencing. NTP is not considered to be an essential service so the OS doesn't provide methods to say "check at exactly this point in the boot sequence" so what's likely happening (can be proven with connman debugging active) is the first NTP check fails as the network stack isn't fully up yet (common on arm devices) and then it's another 15-30 mins before another NTP check. You can use autostart.sh to background an NTP check for 15 seconds (normally enough for the network to be up) and delay Kodi start (the wait-for-network option in LE settings) for 30 seconds to stagger things. Once it works you can tweak the values down to speed-up boot.