Posts by Stereodude

That latest nightly builds of LE 12 (after 08-29) can play 10-bit VP9 now.

Quote from smp

I can reproduce this on my Tiger Lake-U box. I opened a Kodi github issue.

Based on your discussion with Intel back in 2021 it looks like the issue is not the driver, but the way Kodi interfaces/interacts with the driver since the same iHD driver on the same LibreELEC system when accessed by FFMPEG can decode the 10-bit VP9 clips.

Quote from Da Flex

Thanks. I'll send the feedback back to the dev.

Thanks!

It looks like from smp79's discussion with Intel, the iHD driver in Linux does work to decode 10-bit VP9. It worked decoding the clip for smp79 using the Intel iHD driver for Intel via FFMPEG on the same system running LibreELEC. Whereas when using the driver through Kodi it failed. Maybe Kodi doesn't interface with the driver correctly whereas FFMPEG does?

Quote from Da Flex

Can you please test with disabled hardware decoding anyway? It could also be a driver issue, not the hardware itself.

I tested with hardware decoding disabled and it plays as expected (within the limitations of the CPU's ability to decode it fast enough).

Quote from Da Flex

A dev has replied to me. FFMPEG is capable to play the VP9 codec, but probably not the accelerated chip. Turn off hardware decoding.

The hardware supports it. It works under Windows. 10-bit VP9 HW decoding seems to be broken under Linux for all Intel chips that support 10-bit VP9 (8th gen and newer).

SMP79 reported it here after duplicating my findings: https://github.com/xbmc/xbmc/issues/23649

FWIW, I also confirmed the same behavior on a Whiskey Lake-U powered laptop.

Quote from chewitt

HDR support in Kodi is still a little WIP but I'd start investigation with the current 'Generic' nightly as this will have newer kernel and drivers and that may (or may not) help with recent-ish Intel hardware.

The latest nightly does not fix it. Same issue.

http://ix.io/4Ec0

Seems like the decoder doesn't like it.

2023-08-21 17:41:57.503 T:972     debug <general>: CDVDVideoCodecFFmpeg - Updated codec: ff-vp9-vaapi
2023-08-21 17:41:57.515 T:972     error <general>: ffmpeg[0x55e6620]: [vp9] Failed to end picture decode issue: 18 (invalid parameter).
2023-08-21 17:41:57.516 T:972     error <general>: ffmpeg[0x55e6620]: [vp9] Not all references are available
2023-08-21 17:41:57.516 T:972      info <general>: Skipped 1 duplicate messages..
2023-08-21 17:41:57.516 T:972     error <general>: GetPicture - avcodec_receive_frame returned failure
2023-08-21 17:41:57.516 T:972     debug <general>: CVideoPlayerVideo - video decoder returned error
2023-08-21 17:41:57.516 T:972     error <general>: ffmpeg[0x55e6620]: [vp9] Not all references are available

Also discussing it here: RE: NUC recommendation for 4k HDR, hi-def audio

Quote from Da Flex

If not, share a log from the nightly...

Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

The latest nightly does not fix it. Same issue.

http://ix.io/4Ec0

Seems like the decoder doesn't like it.

2023-08-21 17:41:57.503 T:972     debug <general>: CDVDVideoCodecFFmpeg - Updated codec: ff-vp9-vaapi
2023-08-21 17:41:57.515 T:972     error <general>: ffmpeg[0x55e6620]: [vp9] Failed to end picture decode issue: 18 (invalid parameter).
2023-08-21 17:41:57.516 T:972     error <general>: ffmpeg[0x55e6620]: [vp9] Not all references are available
2023-08-21 17:41:57.516 T:972      info <general>: Skipped 1 duplicate messages..
2023-08-21 17:41:57.516 T:972     error <general>: GetPicture - avcodec_receive_frame returned failure
2023-08-21 17:41:57.516 T:972     debug <general>: CVideoPlayerVideo - video decoder returned error
2023-08-21 17:41:57.516 T:972     error <general>: ffmpeg[0x55e6620]: [vp9] Not all references are available

Quote from chewitt

HDR support in Kodi is still a little WIP but I'd start investigation with the current 'Generic' nightly as this will have newer kernel and drivers and that may (or may not) help with recent-ish Intel hardware.

Okay, I will give the latest nightly a test later today and report back.

Quote from w46n3r

Indeed a very attractive alternative.

Does the Beelink S12 Pro you mentioned has any kind of issues with HDR switching, framerate switching, or any BT 2020 color space weirdness? I'm about to pull the trigger but just wanted to be sure about the capabilities of the box.

I have a Beelink EQ12 (also a N100 SoC) and 11.0.3 does not play 10-bit VP9 HDR content from a mkv or mp4 correctly using hardware acceleration. No image is displayed from the video. AV1 and HEVC hardware acceleration seem to work okay. I need to try the LE 12 nightly and see if it resolves the issue.

Using LibreELEC 11.0.3 on a Alder Lake-N (N100) system. I've found 10bit (HDR?) VP9 HW decoding seems to be broken. HDR VP9 videos at 1080p, 1440p, UHD/4K don't play correctly. I did not try lower resolution versions. Audio plays, but nothing from the video is drawn on the screen and the GUI gets a bit corrupted. Nothing crashes and the video can be stopped and the GUI returns to normal. The HDR clips will play displaying an image with HW acceleration turned off for VP9.

I don't have a 10-bit non HDR VP9 video to test with (my understanding is that all YT non-HDR VP9 is 8-bit), so I don't know if it's 10-bit HDR specific or not. The standard non-HDR UHD/4K VP9 version plays fine.

The test videos are extracted from this Kodi sample library clip:

FWIW, the UHD/4K HDR AV1 version plays fine with HW acceleration. Also, if anyone is curious the N100 isn't able to play back the 8K/HDR AV1 version (to a 1080p screen) smoothly at the full 60FPS. It can only achieve ~33fps, but I suspect that's a lack of graphics processing capability in the Xe cores.

The UHD/4K HDR version info:

Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/mp41)
File size                                : 908 MiB
Duration                                 : 4 min 27 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 28.5 Mb/s
Frame rate                               : 59.940 FPS
Writing application                      : Lavf60.10.100


Video
ID                                       : 1
Format                                   : vp09
HDR format                               : SMPTE ST 2086, HDR10 compatible
Codec ID                                 : vp09
Duration                                 : 4 min 27 s
Bit rate                                 : 28.3 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Variable
Frame rate                               : 59.940 FPS
Minimum frame rate                       : 58.824 FPS
Maximum frame rate                       : 62.500 FPS
Color space                              : YUV
Bits/(Pixel*Frame)                       : 0.057
Stream size                              : 903 MiB (99%)
Language                                 : English
Color range                              : Limited
Color primaries                          : BT.2020
Transfer characteristics                 : PQ
Matrix coefficients                      : BT.2020 non-constant
Mastering display color primaries        : R: x=0.677980 y=0.321980, G: x=0.245000 y=0.703000, B: x=0.137980 y=0.052000, White point: x=0.312700 y=0.328980
Mastering display luminance              : min: 0.0000 cd/m2, max: 1000 cd/m2
Maximum Content Light Level              : 1100 cd/m2
Maximum Frame-Average Light Level        : 180 cd/m2

Quote from chewitt

It's hasn't moved .. it's always been there

Oops... I guess my memory was bad. I've generally only used Kodi as an audio player. I only started dabbling with 3D video playback yesterday.

Quote from chewitt

Setttings > Playback > Adjust refresh .. set to start/stop

Thanks! I didn't realize the setting had moved to elsewhere in the menu.

How do I get the RPi3 to automatically switch refresh rates with a clean install of LE 9.2.6?

The connected display supports:

tvservice -m CEA
Group CEA has 21 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive 3D:FP|TopBot
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced 3D:SbS-HH
mode 14: 720x480 @ 60Hz 4:3, clock:54MHz x2 progressive
mode 15: 720x480 @ 60Hz 16:9, clock:54MHz x2 progressive
(prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive 3D:FP|TopBot
mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced 3D:SbS-HH
mode 29: 720x576 @ 50Hz 4:3, clock:54MHz x2 progressive
mode 30: 720x576 @ 50Hz 16:9, clock:54MHz x2 progressive
mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive 3D:FP|TopBot
mode 34: 1920x1080 @ 30Hz 16:9, clock:74MHz progressive
mode 35: 720x480 @ 60Hz 4:3, clock:108MHz x4 progressive
mode 36: 720x480 @ 60Hz 16:9, clock:108MHz x4 progressive
mode 37: 720x576 @ 50Hz 4:3, clock:108MHz x4 progressive
mode 38: 720x576 @ 50Hz 16:9, clock:108MHz x4 progressive

at the gui:

tvservice -s
state 0xa [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 59.94Hz, progressive

For example enable Full HD HDMI modes for Stereoscopic 3D is set. But when I play 3D MVC content this is the mode I get:

tvservice -s
state 0xa [HDMI CEA (16) 3D T&B RGB lim 16:9], 1920x1080 @ 59.94Hz, progressive

If I manually change the refresh rate to 23.98 in the GUI before starting playback I will get:

tvservice -s
state 0xa [HDMI CEA (32) 3D FP RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive

I've whitelisted all the 1080p resolutions my display supports (like 1080p24, 1080p23.98, etc.), but it won't switch into any of them automatically for 2D or 3D content. It just always stays at what the GUI is set to. There is no option to enable automatic refresh rate switching in the GUI like I've seen in older versions on other HW, I checked both Advanced and Expert modes.

I have a AWOW NV41 Celeron J4105 (Gemini Lake) mini PC that I installed the 9.2.2 (x86_64) LibreELEC on. It looks like it enters sleep (judging from the power LED going red for a moment and the screen going blank) when I tell it to suspend and then immediately kicks back to the GUI with the power menu still up on the screen.

Is there a way I can tell what might be causing the issue / provide useful information to the devs to help get this resolved/fixed?

Quote from noggin

Yep - though I guess you're then in a world of Rec 601 vs Rec 709 vs Rec 2020 YCrCb conversions (as they are all different) if you play back a Rec 601 DVD and output it in Rec 709? (And that's ignoring gamut conversions - which you kind of can with 601/709 tolerably, but you can't with 709 vs 2020)

Arguably taking stuff back to RGB rather than doing YCrCb.601 - > YCrCb.709 conversion in the YCrCb domain is a six and two threes?

My understanding is that for HDR content there are flags in the HDMI stream to indicate the color space. I think that takes care of 709 and 2020 for folks with a HDR capable display. The source doesn't have to do any conversions, just enable the right flags in the output. I'm not sure how 601 is handled.

There's going to need to be a lot of LE work done if people are expecting the RPi 4 to play pretty much everything and get reasonably correct results on all display types. That will require handling just about about every possible color space conversion, HDR to SDR tone mapping, and who knows what else.

Quote from noggin

The Pi Devs have said 4:2:2 support is there - but it looked like they suggested the vertical subsampling for 4:2:0 meant that wasn't an option. If that is the case, then that means 4:2:2 12-bit will be the only HDR HDMI 2.0 output mode for 2160p50-60 supported I guess (as there is no 10-bit 4:2:2 defined for HDMI 2.0 - so 10-bit HDR HEVC content is output at 4:2:2 12-bit not 10-bit)

For 2160p24-30 content you can run RGB or 444 and output HDR, without needing 4:2:2 (though 4:2:2 12-bit is valid at these frame rate resolution / combos as well, whilst there is no 4:2:0 support in HDMI 2.0 at <50p). For the bulk of HDR HEVC PQ content - which is 2160p23.976 movies an tv drama - RGB or 4:4:4 YCrCb output in 10-bit is a supported HDMI 2.0 mode and is fine.

I guess if you render Kodi to YUV-space you'll need to have both Rec 709 and Rec 2020 RGB->YCrCb conversion implemented, unless you mind GUI rendered stuff being a bit out (are photos gui-rendered)

Well, if the YUV 4:2:2 support on the Pi works anything like a PC everything will be done in RGB colorspace and then be converted to YCrCb right before it's output with a conversion of nebulous quality / correctness.

Most BD & UHD-BD players output in YCrCb color space and play back YUV video content from files without a conversion to RGB and then back to YUV. It would be nice if the RPi 4 could do the same. Unfortunately the BD & UHD-BD players have all sorts of limitations on codecs and containers.

If it doesn't support YUV4:2:x it won't be able to do 10-bit 2160p60. If it can only do 8-bit RGB 2160p60 HDR playback is going to be gimped.

However, I don't know if the Videocore VI is capable of decoding YUV video, leaving it in YUV color space, and rending the Kodi GUI/OSD either directly into YUV color space or rendering it to RGB and converting it to YUV for blending and output so that the video can be passed unmolested without two color space conversions.

Quote from relkai

Somehow I expected exactly this behavior.

I never wrote a single word to you before and just tried to explain the situation to you above.

You again decided being arrogant and insulting me.

Look, I want to personally thank you for coming here and posting. Now no one will have to take my word for it that the CE developers are thin-skinned and unprofessional. I'm a little disappointed though. You swooped in and stole my glory by perfectly illustrating and demonstrating it.

I will PM you some links to threads on a few other forums where I'd love for you to come and make similar demonstrations to backup my posts.