ASRock N100M fails to play UHD HEVC HLG Channels via Enigma2 Plugin

KaNo · March 30, 2025 at 6:20 PM

Hello everyone,

right now I'm evaluating a replacement for my >>Odroid C4 with CoreELEC-NG 21.2<< with a bit more bums, so I decided to go for a N100M motherboard from ASRock.

In general it does all what it need to do beside when it comes to playback UHD HEVC HLG Channels (RTL UHD or Pro7Sat.1 UHD or UHD1 by ASTRA / HD+) via the built-in Enigma2 Plugin from the Kodi's repository.

Switching to an UHD channel isn't really fast (kind of choppy), and sometimes after a while, there is only audio playback, but a picture is never drawn onto the screen.

On the contrary, ripped BluRays transcoded from AVC to HEVC are playing without any problems - including PGS-Subs without elevated CPU usage.

The N100M is on its latest BIOS (2.01) and I've tried several approaches under Kodi 21.0.2 with:

- Windows 10
- Windows 11
- openSUSE Tumbleweed with Packman - latest zypper dup
- LibreELEC Generic x86_64 12.0.2 (currently in use)

Strange thing is, when I'm using VLC on each of the system, and stream those UHD channels via OpenWebIF of my Vu+ Duo4K, none of the systems/OSes I've tried, have any problems with it and are playing fine.

I guess the culprit is the following related to ffmpeg:

Display Spoiler

2025-03-30 17:36:11.516 T:1471 debug <general>: CVideoPlayerVideo - Stillframe detected, switching to forced 25.000000 fps

2025-03-30 17:36:11.758 T:1471 debug <general>: CVideoPlayerVideo - Stillframe left, switching to normal playback

2025-03-30 17:36:11.759 T:1471 error <general>: ffmpeg[0x23fc3ee0]: [hevc] Could not find ref with POC -24175

2025-03-30 17:36:11.759 T:1471 error <general>: ffmpeg[0x23fc3ee0]: [hevc] Could not find ref with POC -24173

2025-03-30 17:36:11.759 T:1471 error <general>: ffmpeg[0x23fc3ee0]: [hevc] Failed to end picture decode issue: 18 (invalid parameter).

Kodi.log via pastekodi uploaded to Google Drive: https://drive.google.com/file/d/1b8b9F6…iew?usp=sharing

But I'm kinda lost right now and cannot find a solution for it...

Any help would be greatly appreciated.

Thanx in advanced
KaNo

**smp** · March 30, 2025 at 9:52 PM Best Answer

This is a known issue. No fix as of yet.

VAAPI hw decode failure with 4K HEVC HLG DVB stream · Issue #23699 · xbmc/xbmc

Bug report Describe the bug Here is a clear and concise description of what the problem is: I'm having an issue with "Hot Bird 4K1" TV channel that is…

github.com

Disney+ Addon not playing properly the stream when VAAPI is enabled · Issue #25383 · xbmc/xbmc

Bug report Describe the bug Here is a clear and concise description of what the problem is: Disney+ Addon creator and Inputstream.Adaptive maintainers think…

github.com

KaNo · March 31, 2025 at 12:20 AM

Ah, damn.

Thanx for the hint smp.

**emveepee** · March 31, 2025 at 3:30 PM

I am using an N100 with LE 12.0.2 (with NextPVR as my PVR service) and I tested HEVC 4k via PVR and don't see any issue playing for maybe 30 minutes (streamed via http).

I do see this logged when it starts streaming before playback but not afterwards, it takes time for my capture device

Code

2025-03-31 10:11:23.014 T:1211    error <general>: ffmpeg[0x39aa1de0]: [hevc] Failed to end picture decode issue: 23 (internal decoding error).
2025-03-31 10:11:23.014 T:1211    error <general>: ffmpeg[0x39aa1de0]: [hevc] hardware accelerator failed to decode picture

yamcenutzer · March 31, 2025 at 10:53 PM

Yes it is a known issue mentioned from different sources (see above). and the workarounds are:

a. use http (and lose time shift)

b. with tv-headend you can start a recording and watch from the recording buffer. dunno if that is an option on your service

Something different:

does your n100 do hd Audio Passthrough (DTS-MA HD, TrueHD, Atmos?, anything else?)

yamcenutzer · May 29, 2025 at 5:12 PM

BTW, the (first) github issue above https://github.com/xbmc/xbmc/issues/23699 has been dropped so no one cares anymore

**chewitt** · May 30, 2025 at 5:27 AM

If ffmpeg fails to decode the stream the issue is most likely with ffmpeg support for VAAPI or the Intel GPU driver which provides VAAPI (or an edge case with mesa) so I would start by reproducing the issue on a general purpose distro (in part to prove it's not LE specific) and then report the problem to ffmpeg developers via their 'trac' reporting tool.