Posts by popcornmix

Quote from pieranjua

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.

Just insert the sdcard into a windows (or mac/linux) machine and you should see config.txt in the root directory that shows.
(assuming you installed LibreELEC directly, without using NOOBS).

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).

Does it help if you disable omxplayer in video/acceleration settings?

Can any other Hifiberry user confirm they have working audio?

Your kodi log doesn't have debug enabled.
You could try a Milhouse/nightly build as I have seen recent reports of I2S audio working with it:
LibreELEC Testbuilds for RaspberryPi (Kodi 17.0)

Might help if you mentioned the platform you are using and perhaps post a debug log.
I've not seen others reporting this not working.

In system/display settings there is a "video calibration.." option.

Make sure settings level is set to advanced or expert.
If you use "adjust display refresh rate to match video" you may need to calibrate each framerate you use.

Do you have passthrough enabled? (That will stop amplification from working).
Does it work better with omxplayer disabled?

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.

Quote from jglazer63

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:

mount -o remount,rw /flash

before you can edit it.

Quote from nxnw

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.

Quote from CandyLuv

LibreELEC:~ # grep gpu_mem /flash/config.txt
gpu_mem=128
# SDRAM size based GPU memory split, uncomment and setup to override 'gpu_mem'
gpu_mem_256=112
gpu_mem_512=160
gpu_mem_1024=256
gpu_mem=320
LibreELEC:~ #

Display More

The gpu_mem_xxx options have precedence over gpu_mem, so your 320 setting will be ignored.
However you should get 256M on a Pi2/Pi3 (which has 1024M total) and 160M on Pi1 (with 512M total).
Are you using a Pi1, Pi2 or Pi3?

I'd suggest you comment out (insert a # at the start of line) the gpu_mem_256, gpu_mem_512 gpu_mem_1024 lines, and just insert "gpu_mem=256" at the end of the file.
You can run (after rebooting):
vcgencmd get_mem arm
vcgencmd get_mem gpu

to confirm the setting has worked.

Quote from fTdOmen

There's a lot of variation in how far you can overclock a Pi3, I've got one that can operate at 1550mhz with no problems and another that I can't get past 1330. Start with small steps

Really? I've tested many Pi3's and not found one that's reliable at 1500MHz.
I've got one that's *almost* reliable at 1450MHz, but I have backed off a little as I got very occasional crashes.

You might want to confirm with "vcgencmd measure_clock arm" as I think there may be a hard limit of 1500MHz from the arm's clock.

Quote from CandyLuv

That is strange because "gpu_mem=320" is what I have it as in my configuration file and I just checked it to confirm.
*I fail to mention that sometimes freezing occurs and movie thumpnails etc also have problems showing up.

ssh in to pi and report output of:

grep gpu_mem /flash/config.txt

07:11:37   9.585470 T:1962696704  NOTICE: ARM mem: 848MB GPU mem: 160MB MPG2:0 WVC1:0

Your gpu_mem is 160, which is less than the default of 256M (on Pi2/Pi3). Why is that?
That, coupled with using a heavy skin is probably the cause of the issues - running out of GPU mem and so unable to display textures.

Set it back to 256M. If that is not enough you may want to try 320M or more.

Quote from jogger

TV tested with TVheadend: RPi will not easily switch channels from SD to HD. Need to start a movie in between. All other directions work.

Is the SD channel MPEG-2 (without a codec licence) and the HD channel H.264?
There is a known issue with switching between hardware and software codecs without stopping. It has been fixed in Krypton:
VideoPlayerVideo: Need to clear pictures before switching decoder by popcornmix · Pull Request #9861 · xbmc/xbmc · GitHub
mmal_renderer: Use shared pointers to maintain the pool until the decoder has been destroyed by popcornmix · Pull Request #9975 · xbmc/xbmc · GitHub

I'd be interested if you have the problem in a Milhouse nightly build.

That appears when you press a number on the keyboard (it allows entering an explicit seek time).

So something is sending button presses. What do you have connected to Pi? How are you controlling it?

Remove this from advancedsettings.xml:

<gui>
<algorithmdirtyregions>1</algorithmdirtyregions>
<nofliptimeout>0</nofliptimeout>
</gui>

That's not supported on any GL ES platforms.