Posts by chewitt

Upscaling 720p to 2160p

^ to save repeating myself.

Update to 8.2.1 and if not resolved, report as a bug to Kodi developers via Kodi forums.

How are you connected to the Internet? Ethernet or another WIFI device?

Kodi upscales content to the base resolution configured. This was 1080p. It is now 2160p. More upscale processing = higher CPU temps.

In the past Kodi only had to scale SD and 720p to 1080p which was a small jump in resolution and rendering processing power, and it only changes refresh rate, not resolution, except on some Android devices. Handling 4k (and 8k in the future) requires a code level rethink. Increasingly people have low power devices that can hardware decode 4k media but due to slow ARM CPU's and internal memory bandwidth constraints they cannot handle 4k GUI and overlays. Kodi does a better job of scaling SD/720p to 1080p and it's easy, whereas AVR's and TV's typically do a better job of scaling 1080p to 2160p than Kodi. Kodi attempts to run at the max refresh rate supported so 29.97Hz runs at 59.94Hz etc. but new 120Hz capable screens double 60Hz which requires more processing than available. Kodi needs to evolve the concept of resolution switching in addition to refresh rates, but we nearly always need to manually intervene and impose limits rather than auto-detect capabilities. It's a complex topic with a web of interdependent variables. Kodi developers are currently in the process of figuring out how to technically deliver a solution for this without too much code spaghetti and a reasonable 'configuration' user experience. Oh, and at the same time we're rewriting the Linux graphics stack to support HDR, and other colourspace/metadata things that add complexity to the 4k process.

TL;DR .. today Kodi works as expected. In the future Kodi aims to be more flexible to get the best output from individual devices.

Test a Leia development build (if possible) to check it's not already been resolved. If not, report to Kodi developers via their forums.

On what LE version?

Quote from yummy_yum

I'm not using any illegal/streaming addon. I'm using Sabnzbd, which is usenet client, plus Sonarr/Radarr/Hydra - all from thoradia repo.

Stealing copyrighted media from usenet is still stealing copyrighted media. The tolerated presence of that repo on this forum needs to be revised.

Pastebin a Kodi debug log pls.

It's a problem for all devices bar the handful that have been widevine L1 certified and have device-specific certs embedded in their firmware. WP2 and Hub are certified devices, but we would need to implement OP-TEE secure boot on Linux. We are aware of work being done for a European telco IPTV project that uses Amlogic S905D devices that we would like to learn from, and may revisit things in the future once a mainline kernel codebase is available. It's not going to be an LE9 feature.

It's not a debug log and it looks to have been edited to remove information about the add-ons installed. This is normally done by people hiding their pirate add-on collection so we'll refuse further support. If you provide a complete (and clean) debug log we'll continue.

The short answer in respect to those DRM change is 'no' because having drivers that support HDCP is only one piece of a complex puzzle. You still need a secure boot environment which contains a widevine L1 decryption key. The current architecture for widevine requires keys to be associated with a single device type that has been certified (a closed unit of specific hardware and OS). There is no framework for generic hardware support. The Intel changes are more relevant for BR playback on Linux than netflix.

Easy. Change the system for something that supports power management in hardware, and has a kernel with support for those features.

Your "broken" installation is fine, just wget/curl the milhouse build .tar file to /storage/.update and reboot.

escalade Milhouse only provides .tar files, no .img

LibreELEC.tv/tools/docker at master · LibreELEC/LibreELEC.tv · GitHub

^ build inside a docker container, then we don't have to accommodate all the weird stuff in a Gentoo install.

No.

feed works fine here (using Vienna on macOS)

LE 9.0 will use a lightly updated (mostly the same) 3.14 kernel. Our mainline kernel efforts will not be ready in-time for the 9.0 release.

It's not possible to change the drivers.