Posts by popcornmix


    EDIT: When I check the status using "tvservice -s", then a difference is shown. But I cannot see any difference on the TV visually.

    There shouldn't be any visible difference if TV respects the signalling.
    The setting will change both the (limited/full) range of the pixels output, and the signalling of limited/full range to the TV.
    So if the TV understands the signalling (it should) then it should display very similar pictures in both cases.

    The setting is only useful when the TV fails to respect the signalling, and e.g. if interpreting the pixels as full range when they are actually limited.
    Forcing the pixel encoding will solve that, but it is rarely required (only when TV is causing the problem).

    So, I don't think this is the issue.

    The TV may have different presets for colour/contrast/brightness from different sources. You may want to experiment in the TV menu.

    Can you try with the latest Krypton (or Milhouse) build?

    Pi2 has plenty of RAM for Kodi. You are obviously hitting some bug (which could have been fixed in Krypton build) which should be solvable.

    Try a newer build with a clean install. Check if it's reliable before installing too many add-ons (which may be the cause of the issue) or changing too many settings.
    If you get a problem then post a debug log and instructions for how to reproduce the issue.

    Some TVs will assert hotplug when powered on and deassert it when powered off (but some leave it always asserted).
    Run "tvservice -s" (e.g. from ssh) with TV powered and unpowered and check if the number after "state" changes.

    If that doesn't work you may be able to monitor events. Run "tvservice -M" and then power off and on. Does it report anything?


    Different world how? I don't get this statement about having two operating systems. It's simply a compiler switch at build time, there's already 64 bit ARM support in LE.

    You need a 64-bit kernel to run 64-bit code. The current 64-bit kernel build is limited in features (e.g. no hardware video decode).


    Well, my raspberry pi came with a SD card that already contained some images. During the installation procedure, I chose to install LibreElec. The root of my SD card looks like: see attachment

    Yes, that is NOOBS. If you press shift when booting, you can stop in NOOBS configuration. That includes a menu option to edit config.txt.

    But if you only ever want to use LibreELEC then a fresh install of LibreELEC may be advisable - it saves some sdcard space and simplifies things like editing config.txt.

    The basic rule of the performance governor is to use turbo mode whenever any arm core is above 50% busy.

    Use the "p" option of bcmstat to get each core's cpu usage.
    Use the "m" option of bcmstat to disable colourisation if you are copy/pasting the output (your stats.txt wasn't really readable).

    There is a complication with live streams (like PVR) that the clock of the backend is probably not synchronised with the clock of the frontend.

    The clocks will typically be driven by a crystal oscillator with an accuracy of around 100ppm (0.01%).
    If it turns out that the frontend clock runs 0.1% faster than the backend, the amount of buffered data will gradually deplete until it is empty and kodi will pause to buffer again.

    It is possible you are hitting this issue and by pausing you are giving more time before the buffered data runs out.

    The good news is that if this is your issue then Kodi Krypton has a solution for this (audio resampling is used to manage the amount of buffered data, so synchronising the backend and frontend clocks).

    You could try a LE 17 Kypton alpha build, or a Milhouse nightly build to see if the issue is still present.


    Everything says "edit config.txt" but nowhere does it say where this file exists on the system. Nowhere. I mean I went to like 10 web pages and they all say "edit config.txt" and you know what? When I log in via SSH there is no config.txt. Where is it?

    Are you using a pi? It wil be /flash/config.txt

    By default /flash is mounted read-only so you need to:

    Code
    mount -o remount,rw /flash

    before you can edit it.


    After upgrading from OpenELEC 7.0 beta 3 to LibreElec 7.0.2, I found that HDMI passthrough was only providing sound on two channels, regardless of the source data. This occurred in local file playback with every file I tried as well as playback of MythTV PVR recordings.

    Debug log with you trying to play a file with passthrough please.