Posts by HiassofT

Please also check the following command on RPiOS (this uses the same audio parameters as kodi will use):

speaker-test -t sine -c 2 -r 44100 -F S24_3LE -b 200000 -p 50000 -D iec958:CARD=Audio,DEV=0

so long,

Hias

Can you check if the USB firmware is up-to-date (in Settings->LibreELEC->Updates)? If it's not please update it.

dmesg shows that the USB controller can't set up the required parameters for your USB device, kodi then falls back to the default (HDMI) audio device

pr 21 22:28:37.569965 LibreELEC kernel: usb 1-1.2: Not enough bandwidth for new device state.
Apr 21 22:28:37.570686 LibreELEC kernel: usb 1-1.2: Not enough bandwidth for altsetting 2
Apr 21 22:28:37.571228 LibreELEC kernel: usb 1-1.2: 3:2: usb_set_interface failed (-28)

I've found a couple of similar reports on the RPi forum (most of them with multiple USB audio cards though), eg Not enough bandwidth for new device state. - Raspberry Pi Forums so that could still be a compatibility issue with the RPi4's USB controller and that specific USB audio device.

If updating the USB firmware doesn't help it's best if you test with Raspberry Pi OS (ex Raspbian) and if that fails too open a thread on the raspberrypi forum where the RPi USB dev(s) will hopefully pick it up.

so long,

Hias

I've noticed you have an odd path in your PATH variable: ~/.local/bin - not sure where that comes from and why the tilde isn't expanded into $HOME (that seems to have worked for /home/work/perl5/bin and /home/work/bin.

Might be worth tracking down where that comes from and getting rid of it - maybe that's what the build system trips over (the other linked bug report also had a non-expanded tilde in the PATH). Look at .profile, .bash_profile, .bashrc etc files in your home directory and also for profile/bash stuff in /etc.

so long,

Hias

Quote from harun-cuk17

When I want to download a video it says that too many people have download it and it is not possible to download.

That happens quite regularly - keep trying, I had most success in the morning (UTC), quota counters seem to be reset during the night (no idea when exactly).

so long,

Hias

Quote from harun-cuk17

I got it. And the BT2020 is also in the last nightly build?

yes.

so long,

Hias

Test with the latest nightly instead - from one of your posts it looked like you had installed an earlier testbuild without the final BT2020 fix.

Edit: I've now removed the testbuilds from my server to avoid confusion - all HDR changes are available in nightly builds.

so long,

Hias

Quote from harun-cuk17

Do you have a sample file to test the hdr on the rpi4 with your latest build? If yes could you upload it by wetransfer?

I will put the file on usb stick and test it on LE 9.2.6 and on 10.0.

Just head over to 4kmedia.org, you'll find plenty of samples there - eg Samsung Wonderland Two HDR UHD 4K Demo | 4K Media

There's not much point in testing with LE9.2 (as it doesn't support HDR output), check with the latest nightly and compare the same file with the internal player of your TV our your UHD BR player - if you do that, make sure the TV settings are identical, lots of TVs store separate settings for each HDMI port and also internal player.

so long,

Hias

Quote from nsnhd

Ok, it's sad. So, if not the RPi4, then any other box running LibreElec or CoreElec could do tone-mapping better ? Lots of HDR stuffs are there and I dont want to buy any HDR display soon.

IIRC tone mapping is only supported in Kodi for Windows (via d3d shaders) and Android (via the mediacodec framework, if implemented by a device). I've read reports that it works fine on the Nvidia Shield, not sure about other devices.

so long,

Hias

Quote from nsnhd

How the Pi 4B performs the HDR to SDR tone mapping ? I got 1080p projector and 4K monitor, both are SDR.

It doesn't. Tone mapping requires a quite powerful GPU (or fast processor) which the RPi4 doesn't have and also this isn't implemented in Kodi yet. Mapping 720p or maybe 1080p might be possible but 4k most certainly is way above the RPi4's capabilities.

So, stay away from HDR media if you only have SDR displays or recode it with tone mapping on a PC.

so long,

Hias

Quote from Phoskam

And which nightly do I need for rpi4?

There are so much versions when I look at the nightly list.

Filter by "rpi4" and use the latest tar file to update (or img.gz if you want to write a fresh sd card).

so long,

Hias

FYI: The BT.2020 HDR fixes have been merged into our master branch and are included in the latest nightly build - so you can switch back to using nightlies instead of the test builds from this thread.

so long,

Hias

Quote from linuxuser

Are there any uptades on the dolby synch audio problem?

If you mean DolbyDigital+/E-AC3 then no, this is a kodi issue.

If it's important to you then just subscribe to the kodi issue on GitHub Garbled sound with DD+/EAC3 passthrough and official Dolby DD+ 7.1 sample · Issue #19182 · xbmc/xbmc · GitHub to get notifications when something changes (but I don't expect this to be fixed any time soon TBH).

so long,

Hias

Quote from noggin

Update - just compared the captured bars from the Pi 4B with the native bars from the EBU test file in Resolve and they appear identical. I think this suggests that things are good.

Awesome, this is really good news! Huge thanks for going through all the effort and checking this!

so long,

Hias

Downloads->Raspberry Pi 4->LibreELEC 10.0 Beta

so long,

Hias

Here's a new testbuild, now with - hopefully - correct BT.2020 YCC->RGB conversion matrix:

LibreELEC-RPi4.arm-10.0-devel-20210412194217-d08d2e1.tar

noggin do you have a possibility to verify with your HD-fury if the conversion matrix is OK now? popcornmix's HDMI analyzer doesn't seem to have picture/color analysis features and visual testing is quite a PITA as I don't have an easy-to-use known-good reference to compare against (my TV's built-in player sucks, it completely exits after switching to HDMI input so I can't easily switch back-and-forth).

Of course feedback from others is highly welcome, too!

so long,

Hias

Quote from Da Flex

Even on LE 10 Beta?

yes, config.txt is still the place to configure overlays and bootloader/firmware specific settings.

so long,

Hias

Yes, /flash/config.txt is the correct place for it. Add a line with eg "dtoverlay=cma,cma-384" at the end of the file to reduce CMA memory size to 384MB. See the README in /flash/overlays for more info about syntax and allowed options.

so long,

Hias

Video decoders and the graphics driver now use CMA memory which can be shared by other (userspace) programs.

By default we use 512MB CMA, previously we used 384MB but that was not enough to handle all 4k HEVC files. This can be tweaked with the cma dtoverlay - but keep in mind that if you reduce CMA memory you risk running into video decoder / graphics issues.

No idea about docker, best you open a separate thread about it or discuss in the thread you linked.

so long,

Hias