Posts by chewitt

That linked file was already asked about in another thread and it played fine on RPi5.

It requires someone to flag that newer updates are available on the back-end and in recent years that manual process is often overlooked due to life/work/etc. You can download it manually in the GUI and update.

Have you read https://wiki.libreelec.tv/configuration/4k-hdr ? - the configs discussed should generally help with most media playback.

Probably fixed by https://github.com/LibreELEC/LibreELEC.tv/pull/6159 which has gone off the team radar..

Have a read of this, the content is applicable to 1080p media as much as other types: https://wiki.libreelec.tv/configuration/4k-hdr

Kodi always outputs progressive so you need to enable adjust-refresh and rate doubling, and set the mode whitelist to NOT include 1080p @ 30/29.97/25 modes. Kodi will then switch to 1080@50 with each interlaced half-frame rendered in a single frame. Normal PAL content will be output at 1080@50 too (each frame is rendered twice).

Banned add-ons are installed. No support.

Official:Forum rules/Banned add-ons - Official Kodi Wiki

One of the goals of our codebase is that everything functions the same regardless of the hardware; the notable exceptions being boot/install which are often dictated by hardware type. Stats also show that 80% of our userbase has an RPi board and 10% Intel x86_64 devices so 90% of users should be covered by those general catch-all subforums. In the past (in OpenELEC days) the forum also had more dedicated subsections with the result of each subforum having lower traffic and lower engagement, whereas with only a couple of main sections those forum areas are naturally higher traffic and overall more users enage and contribute to the forum. It's something we've thought about too, but it always ends up with the team being 50:50 for/against .. so it never happened.

HEVC files will play but where 1080p was mostly possible under the legacy codebase 720p is probably the maximum now, and for encrypted streams like Netflix where DRM needs to be handled SD will likely be the limit.

RPi5:~ # ls -l /usr/sbin/*fsck*
lrwxrwxrwx    1 root     root             8 Oct 21 13:52 /usr/sbin/dosfsck -> fsck.fat
-rwxr-xr-x    1 root     root        749016 Oct 21 13:54 /usr/sbin/e2fsck
-rwxr-xr-x    1 root     root         68736 Oct 21 13:53 /usr/sbin/fsck
-rwxr-xr-x    1 root     root         68800 Oct 21 13:52 /usr/sbin/fsck.exfat
lrwxrwxrwx    1 root     root             6 Oct 21 13:54 /usr/sbin/fsck.ext2 -> e2fsck
lrwxrwxrwx    1 root     root             6 Oct 21 13:54 /usr/sbin/fsck.ext3 -> e2fsck
lrwxrwxrwx    1 root     root             6 Oct 21 13:54 /usr/sbin/fsck.ext4 -> e2fsck
-rwxr-xr-x    1 root     root        133688 Oct 21 13:52 /usr/sbin/fsck.fat
lrwxrwxrwx    1 root     root             8 Oct 21 13:52 /usr/sbin/fsck.msdos -> fsck.fat
lrwxrwxrwx    1 root     root             8 Oct 21 13:52 /usr/sbin/fsck.vfat -> fsck.fat

^ LE uses the full e2fsck binary not busybox.

I built a Generic/GBM image here: https://chewitt.libreelec.tv/testing/LibreE…_64-11.80.0.tar which should reinstate mkfs.ntfs and include the ntfsfix tool from ntfsprogs. The image is not tested since I don't have any Intel CPU hardware around these days, but please have a play with the binaries to ensure they compiled okay and to see if ntfsfix can resolve the dirty-filesystem issues you're seeing?

The two files are 4K@60 8-bit (BT2020_RGB colourspace) and [email protected] 8-bit (default colourspace). There is no mode whitelist for adjust-refresh active and the HDMI panel (which looks like a monitor not a TV) offers only 1080p@60/59.94 so Kodi must resample the media to 1080p@60 for output.

I would repeat the test using only 1080p@60 SDR media as this will eliminate DRM colourspace changes and the impact of resampling 4K media to 1080p.

Yup. And the utility that's been dropped with NTFS-3G is "mkfs.ntfs" not "fsck.ntfs" .. and if you do some reading around this topic there is a conspicuous absence of fsck or similar tools for NTFS on Linux. There's an older "ntfsfix" which simply clears the dirty flag; which will probably allow the drive to mount in some/most cases, but risks causing damage in scenarios when proper chkdsk.exe is required to resolve a more serious problem with the filesystem (and due to that, isn't something we'd try to use). It looks like we (and the the rest of the Linux using world) is needing Paragon to clean-up and submit their fsck tool code.

I'll look at building a test image (will be LE12) that you can be the test guinnea-pig for..

Quote from palle_c

I'm just thinking of the next poor person who installs LE11 and says what i said "why isn't "enablehighqualityhwscalers" working

You're the first person to notice since LE11 shipped and nVidia active-install numbers continue to decline over time (we've been telling people to avoid nVidia cards for years now) so the chance that someone else spots the problem is fairly low.

Quote from e123enitan

Any suggestions.

Read the message on the screen?

LE10 and earlier use NTFS-3G via FUSE to mount NTFS drives. LE11 switched to new(er) in-kernel drivers so you'll see a significant increase in file read/write performance. However the in-kernel drivers appear to be a little more enthusiastic about flagging issues; hence the change in behaviour that users are seeing.

LE normally does fsck before mounting drives but there is no fsck.ntfs utility to do this (ext2/3/4 etc. use /usr/sbin/e2fsck). In the past there was an fsck tool from NTFS-3G and I'm wondering if we might need to restore the package; not to switch back to the older driver, but to build and pick the fsck tool to the image.

Kodi allows drives to be selected and unmounted in the file browser, but otherwise the GUI doesn't have an easily accessed option and you'd need to create an unmount-all script and then map the script to a custom remote keymap.

Team Kodi didn't decide on a 20.3 release yet, but it would be good to send the PR in case it happens (the idea has been made). It's always better to merge patches upstream instead of adding them downstream at the LE repo.