Posts by atoulmin
-
-
At the current time "you get output" .. what bit-depth, colourspace and colour-range I've no idea. It's probably not brilliant as we're forced to use the elFarto VAAPI shim until Kodi gains NVDEC support. There are also quite a few things to unwind/redo in Kodi's EGL rendering path to resolve. The x86 world is oriented towards RGB rather than YUV but this isn't an issue as long as things are being done right, i.e. fixing some of the limited/full range issues in the display chain; which is actively being worked on. So no advantages over Intel/AMD that I can see (both suffer from some of the same RGB issues) and I'd still advise anyone considering new purchases to avoid nVidia cards until more of the plumbing has been straightened out.
NB: Support for nVidia now means only GPU's that can use the 580.xx driver series; and we've intentionally held off bumping to the latest driver because that orphans eveything before RTX cards. Current stats show nVidia tiny user numbers on the 580.xx driver, though to be fair we have been telling users to avoid nVidia cards for the last decade so there's an element of "built it and they will come" in-play. I'd expect numbers to increase once there is clear direction on support.
Thanks for the reply. I am currently running a N150 and its output is obviously RGB. However its plugged into a Lumagen and it prefers YUV. I would prefer YUV does AMD output that? Or are we generally stuck with RGB for now.
-
The default boot partition was enlarged from 512MB > 1GB last year to accomodate nVidia driver increases over time, and Generic now (since yesterday) supports current nVidia GPU cards hence the sudden size increase.
The fastest workaround is to use the backup function in the settings add-on (captures /storage/.cache|.config|.kodi) and move that off box, reinstall to create a clean instance with larger boot partition, then restore the backup. Beware anything outside of those ^ folders that you also want to preserve. Resizing partitions can also be done using e.g. Gparted on an Ubuntu LiveUSB, but it will be significantly slower (10x slower if not more).
With support of current Nvidia GPU's now enabled. What are the benefits over Intel GPU? Can nvidia offer YUV ouput instead of RGB?
-
Add to above, i have refresh rate switch turned on etc. If i have the Kodi menu at 1080p60p a 24p 4k file will not output at 4k but 1080p. A 4k23.98 file will output at 4k however as it should.
If i change kodi menu to 4k60p the 4k24p file will output as it should 4k24p, and a 4k23.98 file will output correctly.
This also occurs if i install windows and Kodi. Its got me stumped lol
-
I have a N150, i have an issue where any 4k file that is 24p (not 23.98) is output as 1080p24p not 3840p24p. I've tried different TV's both do the same. I've tried coreelec on a odroid n2 which outputs correctly. Both the odroid and N150 formatted and setup identically but the N150 always outputs 1080p24p files at 1080p24p. Not at 4k. However 23.98 files are fine and outputted correctly.
Everything points to the N150 and libreelec. I've tried 12.2 and nightly releases. Any ideas?
-
Just plug the video into one of the HDMI ports, then plug the audio into the other. Then configure the audio to the port you plugged it into. No need to configure the video.
-
Yeah it was 23.95, and my lumagen reported that as well. I ended up using a new build and applying the 10bit patch to it. All fine now.
-
Display More
portapro I made a quick rebuild of my last community version with the force YCbCr 4:4:4 patch.
download image here https://sky42.libreelec.tv/testing/intel-yuv444/
here is the full source https://github.com/sky42src/Libre…-240324y-yuv444
this commit you can pick for your own build if it works for you https://github.com/sky42src/Libre…7d8a8158956b078
Edit:
Short test on my N100 -> X6700H -> OLED55E6D show it does what it is suposed to do. All is in YCbCr 4:4:4 says the info screen of my Denon with or without HDR10.
You may run into audio trouble when playing 2160p @ 23.976 Hz and using pass through.
quick workaround is to only use 10 bit not 12
systemctl stop kodi && intel-gpu-max-10-bit.sh && systemctl start kodiThis works perfect, i have to use the 10-bit option otherwise i get dropouts.
However i noticed that the video output refresh rate is 23.95, not 23.976 which creates stutters. Any ideas?
-
4K60 is only two movies in my whole collection. Where we need is HDR10+ support, which is backwards compatible to HDR
-
LibreELEC doesn’t support playing 4k60 HDR files yet. Also you should set the gui to 1080p 60.
-
Any update on playing 4k60 files?
-
I just leave my NUC running. No issues so far.
-
I went for an Asrock N100M

Still installing and configuring, but first impression is 👍🏻
HDR working ok and gigabit LAN?
-
Is there any newer build available? I'm still using build devel-20220807005106-45816fd
If there is no newer one available, could you provide one? smp

Or is HDR available on official builds already?
I'm using Intel NUC7PJYH2
HDR is in the nightly builds.
-
I built a 12th gen ITX system and it worked fine for HDR except any 4K60 files. Everything else is fine with my JVC projector.
-
LE spent a lot of time doing performance testing on chipset specific flags during OE days when our Generic userbase was larger and hardware was somewhat slower that it is today (and thus such flags had greater impact). Our conclusion back then was that the flags do technically make a difference, but the gain is so marginal in the wider context of things that influence system "performance" (esp. I/O performance) that it's not worth the effort. And then we killed off chipset specific builds. The idea (re)surfaces from time to time; mostly among the retro gaming crowd who constantly seek overclocks and optimsations, but (still) never seems to hold up to any real scrutiny..
I understand, I’m more interested in the YCbCr output. No performance advantages.
-
It should boot on NUC11. It boots fine on my Tiger Lake box.
The image was built with -march=tigerlake gcc flag. It would probably be unbootable on non-tigerlake CPUs.
What about a Nuc 10th gen. I have one of those I can test with
-
This image will use YCbCr 4:4:4.
This build won’t boot for me on Nuc11
data leaks possible via Spectre v2 BHB attacks! 1.4590913 fail to initialize ptp.kvm