Posts by chewitt

It reminds me of issues seen occasionally when people import configuration from other Kodi platforms (e.g. Win to Linux). Best thing to do is use the log upload function in the LE settings add-on, then share the URL so we can see the config of things and what kind of media is being [not] played?

If you have an RPi3 it's technically possible to boot from USB media (solely) instead of mSD cards.

Either use the USB/SD creator app linked at the top of the downloads page to create a bootable card *or* click the big drop-list link on the same page and select "Raspberry Pi v1 and Zero" and you will see the direct file links for that hardware.

I'm interested in the wireless chipset inside the USB dongle. The information you posted about the Ultra2 is irrelevant.

Our RK support is focussed on current generation SoC chipsets with ARM Mali GPU's because that's where RK themselves are focussed in their push towards mainline kernel support. From a project perspective it's not "economically viable" to look at older chipsets when current generation boards and boxes can be had for $40.

Please report the issue to Kodi developers via Kodi forums.

Kodi in LE v8/v9 uses VDPAU for nVidia cards, which is no longer developed, and VDPAU only supports 8-bit HEVC. LE v10 will not support X11, so unless nVidia get their VDPAU replacement sorted in the next year, LE 11 will not support nVidia cards

FWIW, the un-powerful Intel CPU supports 10-bit HEVC today, and the future GBM/V4L2 graphics architecture that will replace X11 in LE.

You need to tell us what chipset is in the device. Then (and only then) can we give an answer.

<sources>
    <video>
        <default pathversion="1"></default>
        <source>
            <name>SOURCE_NAME</name>
            <path pathversion="1">smb://user:password@SERVER/SHARE/FOLDER/</path>
            <allowsharing>true</allowsharing>
        </source>
    </video>
</sources>

^ that is how something looks in sources.xml .. I find editing the file directly is faster than figuring out things in the GUI.

Have a play with a Milhouse/Leia build to see if the issue still exists there. If it does, report to Kodi developers via Kodi forums.

The only affiliate link that would make sense for the project is digitalocean.com where we host things.

Good old fashioned cash via paypal is always appreciated, or a tee-shirt via teespring

Kodi alpha 1 is probably shortly after new year, but no guarantees. LE will probably release something soon-ish after Kodi, but not for all build projects initially as some of them are still a bit "work in progress" and need more time to settle.

If you want to render 3D images all that power is useful. If you simply want to play hardware decoded video, it's irrelevant.

You're in the wrong forum for advice on where to download content stealing acquisition tools.

The Intel GPU is perfectly good to use, and it works, so why bother with the nVidia one?

Quote from cabal2k

I don't know why these patches are not already in LibreELEC source addon chromium. Maybe it breaks something on other systems than Intel.

There are three reasons things might be missing from our official Chromium add-on:

1) Nobody bothered to submit the changes

2) Nobody bothered to submit the changes

3) Nobody bothered to submit the changes

True that some things can be GPU specific, but unless things are submitted and tried/tested we wouldn't know.

I'd also like to point out that add-on maintenance does not happen by magic and Chromium has proven to be a pain in the arse to maintain due to frequently changing dependencies. Greater community participation in the maintenance process would be welcomed.

service.libreelec.settings/defaults.py at master · LibreELEC/service.libreelec.settings · GitHub

^ it should only be backing up /storage/.config /storage/.cache /storage/.xbmc and /storage/.ssh

If you need to be more specific with backups you can always run your own "tar" archive command to include/exclude whatever locations you need using the "cron" scheduler. If you need to do fancy things like mount remote shares (to store the backup files on) first, schedule a script containing the command sequence instead of a single command.

It should be a good Christmas project to read-up and learn a bit.

OMX was necessary when RPi1 devices with limited resources were the thing. Since then MMAL has superseded OMX and is the active target for development. MMAL works, so use MMAL for everything. Forget about OMX.