Posts by chewitt

there's no size limits that we've ever been aware of .. what happens if you unpack and convert to .tar on another box and then try to unpack .tar?

There are no plans for a "new hardware" forum thread that people can subscribe to, but we can create (and multiple people have asked for) a "releases" forum thread. New software releases that support new hardware are likely to contain some kind of announcement.

in LE 7.0.1 or 7.90.001 ?

I can confirm the same on my Xtreamer box. This is a bug that needs to be fixed - thanks for flagging it.

echo "r8169" > /storage/.config/modprobe.d/blacklist.conf

that will blacklist r8169 so r8168 can be used (if that's the issue) but the Kernel drivers improved and I didn't see that problem for a while.

/storage/backup is the correct path .. the help text will get corrected once I figure out how to bulk modify the strings.po files

MPD should be backported to 7.0 (it already exists in the 8.0 repo) in the next couple of days

Ubuntu Pastebin

this was a stock 14.04 minimal install that's had the bare essentials added for building and then a later 16.04 update

cat /storage/.kodi/temp/kodi.log | paste

If you 'paste' the logs I'll look at them. I never download zip files from forums because you never know what people put inside them.

I merged this and the advancedsettings.xml thread.

If you are using WiFi you can test with an Ethernet cable and see if the problem goes away. If it does, some cache tweaking (increasing the cache size) can help to smooth out micro gaps when the cache dips to zero for a few milliseconds. If you're not using WiFi and/or Ethernet does not cure the problem it's because the congestion is upstream and you'll see the cache hitting zero for multiple seconds at a time. In that situation it doesn't matter how big you make the cache, it will not fix the problem. The image you shared shows a stream with <1Mb/sec which means the ratio between incoming data and the default cache is already quite good, so I doubt it's a local issue.

Fusion has nothing to do with network location, but that's not the point: Official:Forum rules/Banned add-ons - Official Kodi Wiki

It has nothing to do with H.265 .. second line from bottom on the far right shows 0% so the video cache is empty. It's possible to tweak the cache settings a bit, but no amount of cache tweaking can make packets arrive quicker from the internet, and in 99.99% of cases that's the issue.

You can enable HTTP debugging and look at kodi.log for retrieval/scraping problems. I have to say that the majority of music I have in my Library doesn't have upstream fanart though, so it may just be your taste in music.

Kodi Krypton contains a major reworking of video code and the Amlogic component is still "work in progress" so you can expect some issues - it's coming along but isn't as complete as the x86/Generic builds.

What (or who) and where are the sources for these builds?

I didn't look at the log .. but I clean built master twice yesterday so it's probably something to do with the build environment. I'm using an Ubuntu 16.04 base for personal and official builds.

This is on our radar but we're advised there are some issues (as well as fixes) with the newer firmware. When pi Foundation folks tell us it's a safe/good point to bump the default firmware we ship; we'll update.

These things happen in multinational development teams. Thanks for flagging it.