Posts by popcornmix

Quote from Monie

I'm not sure about this, but I was thinking that maybe messing with color space using the "xrandr" command might make a difference. But LibreELEC does not seem to allow this command.

No, that is an X command and LE doesn't use X.

The PC may be driving the display in a DMT (monitor) mode, rather than a CEA (TV) mode.
You could try adding "hdmi_group=2" to config.txt will force a DMT mode.

Yes, add it to the end of cmdline.txt (on same line). E.g.

boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet nosplash smsc95xx.turbo_mode=Y smsc95xx.packetsize=2560

You can edid cmdline.txt either from a windows PC (it is in the FAT partition that shows up) or from the pi in /flash/cmdline.txt.
If editing on the Pi run "mount -o remount,rw /flash" to make /flash directory writeable.

There is a new Pi2/Pi3 build (22 October) that should be working again.

I wonder if the smsc95xx.turbo_mode or smsc95xx.packetsize settings of the ethernet driver may help. Have a read here:
Frequent buffering, high bitrate video playback from SMB share to RPi3 with OSMC

and then try adjusting the settings. I believe 4.7.6 kernel will default to "smsc95xx.turbo_mode=Y smsc95xx.packetsize=2560".
Might be interesting to try disabling turbo_mode and/or changing the packetsize value.

Can you test with latest Krypton build (v7.9.007)?
A lot has changed with Krypton, and Jarvis build won't be getting any more updates.

If still a problem then post a debug log.

Yes, it is likely the resolution. The hardware is designed for up to BluRay standards (1920x1080), and while your video has fewer pixels, it does exceed the height.

Note, we can play portrait iPhone videos but they are encoded as 1920x1080 with a rotate flag in the header.
Your video is actually encoded as 720x1280 without a rotation flag.

I'll have a closer look at the file and see if anything can be done.

Quote from bilbo

These files are all about 30Mb. Where shall I upload one?

Dropbox or google drive are good for me.

Can't see any problem in log. Can you provide a sample file?

Quote from Monie

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.

Quote from lrusak

In the latest alpha builds or milhouse builds we alread include the latest firmware

Lastest "master" branch firmware. Not latest "next" branch firmware which is still considered experimental.

I got this working on LibreELEC/Pi: Amazon Echo(Alexa) Skill and Kodi Addon

I was able to play some videos and control them, but it wasn't very accurate at recognising my voice.
This was before the UK release of Alexa, so it may have struggled with my accent - I'll need to test it again.

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?

Quote from escalade

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

Quote from majkreem

I changed my audio settings in kodi to 5.1, 5.1 passtrough, and etc. But it didn't work right. I downloaded some 5.1 channel test video, and i always hear the same.

Don't do that. Number of channels *must* be set to 2.0 when using spdif/toslink.
Number of channles is only used for multichannel PCM, which is a HDMI feature.
Passthrough will still work with number of channels set to 2.0.

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