Posts by popcornmix

Quote from smp

I'd like to know this myself. I noticed the inferior performance of kernel 4.9 back in December with Milhouse build #1215. The issue is easy to reproduce as long as you have a DVB tuner connected to the Pi and PVR server/client are on the same Pi. The difference in performance is huge, with kernel 4.8 I can run this setup without a single issue (with Advanced deinterlacing enabled). With kernel 4.9 I absolutely have to disable Advanced deinterlacing (even increasing arm_uc doesn't help).

I'll need to dig in to see exactly what changed between 4.8 and 4.9.
4.9 kernel uses more upstream drivers, including the upstream interrupt controller. 4.8 may have still been using the downstream one (I'd have to check).
That could mean either a difference in speed to dispatching the ISR (I would have thought that difference would be small) or a difference in precedence
(i.e. if a USB and a timer ISR are both pending which gets dispatched first) which may have more of an effect.

There is also a FIQ driver that USB uses.

Can you point sakos at your build to see if it helps his issue too?

Quote from smp

Use an older, pre-kernel 4.9 build (or my custom 7.95.2 build) + "arm_uc 12 0" and the errors should be gone.

Which kernel does your custom build use?
I can't think of a reason why an older kernel would work better, but if it does I'd like to know why.

There have been some libcec changes and some firmware changes between Jarvis and Krypton.
If you are having trouble with CEC on Pi, you can try reverting the firmware back. Download the following two file:
start.elf?raw=true
fixup.dat?raw=true

and replace the ones on the sdcard (take a copy of the old files in case you want to switch back after testing).
These files should be visible when the sdcard is inserted into a PC with an sdcard reader (assuming a direct LibreELEC install, rather than a NOOBS install).

Power off the TV from mains for a minute. Check you are seeing a problem. Revert the firmware. Power off the TV from mains for a minute. Report if any difference in behaviour.

Advanced (x2) deinterlace is very heavy on sdram bandwidth.
Some PVR backends have little tolerance to being delayed and may drop packets when sdram bandwidth is heavy.

As you have found, increasing the arm's uncached (sdram) priority can help.
Have a read here: showthread.php?tid=269814&pid=2373475#pid2373475
The v3d_limited is another dial you can adjust which tweaks how advanced deinterlace uses sdram.
You can also try overclocking sdram which will help. Overclocking core and v3d may also help.

Options are:
Run PVR backend on a separate Pi from the one you watch.
Switch to Bob (x2) deinterlace
Switch to Advanced (x1) deinterlace
Play with some of the overclock and sdram controlling settings. Perhaps we'll find a better set of defaults.

Note: Jarvis defaulted to Bob deinterlace for HD, so switching back to Bob on Krypton should behave much like Jarvis did.

prwnd Can you try disconnecting TV from mains for a minute and retrying?
Also see this post: How do I make additional buttons on my Panasonic remote work?

Panasonic sending PVR button presses is a choice the TV makes (you can affect it with the magic button code)
and it may have just got disabled.

Are your kodi CEC settings defaults? i.e. is "Switch source to this device on startup" enabled?

Quote from antonsn

<cache>
<memorysize></memorysize> <!-- number of bytes used for buffering streams in memory
<buffermode></buffermode> <!-- Choose what to buffer:
<readfactor></readfactor>
</cache>

That is the correct syntax for Krypton, but you need the <advancedsettings> / </advancedsettings> tags around the block.

The coloured square appears after firmware has loaded and remains until kernel replaces it.
If it stays up it means the kernel failed to start.

Most common cause is updating a Pi2 with Pi1 image (or vice versa).
But sdcard corruption or an interrupted update could also cause it.

A reinstall may be the simplest option.

Probably worth describing the platform you are using.

When you are watching live, are you also recording?

If the Pi3 is able to record a stream to your NAS fine then streaming to a single player should be exactly the same amount of work.

Does disabling deinterlace make any difference?

The end of the log contains:

00:11:20.720 T:1393554336   ERROR: Unable to open database: MyVideos107 [2003](Can't connect to MySQL server on '192.168.0.200' (101))
00:11:20.720 T:1393554336 WARNING: DoWork - Unable to open video database. Can not save file state!

Is it possible there is a problem with your MySQL server or network?
Can you try disabling MySQL and play some files and see if kodi is stable or not?

Post a debug enabled log.

By 4k do you mean 4k resolution? That is not supported on Pi.

Post a complete debug enabled log (use a paste site).

Your log does have some Emby compaints.

20:05:56.117 T:1778185120  NOTICE: EMBY.kodimonitor -> Item is invalid for playstate update
20:06:00.323 T:1778185120  NOTICE: EMBY.player -> Could not find itemId, cancelling playback report...

I'd suggest disabling Emby and first test playback of the file locally (e.g. copy to sdcard or locally attached USB stick).
If that is okay then try playing from a network share (without using Emby).

Testing with a clean install may be the best option if you have a spare sdcard.

Not really a RPi3 clone - it won't run any of the same software images.
It is a Rockchip SoC. Kodi has no support for Rockchip, so chances of LE support are low.

Do you have the same issue with recordings from tvheadend? If so then a sample file may be useful.
Otherwise post a debug enabled kodi log.

Post a debug log of you starting a movie.

Quote from MaDi86

I can select the Hifiberry AMP driver and hear the system sound over the Hifiberry. However playing movies I have no sound with the Hifiberry, but only via HDMI output.

Anybody with a similar observation or a hint where to look at?

It sounds like you have enabled passthrough and it is set to HDMI. Try disabling it.