Jellyfin Forum
SOLVED: Issues Hardware Decoding MPEG2 - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Issues Hardware Decoding MPEG2 (/t-solved-issues-hardware-decoding-mpeg2)



Issues Hardware Decoding MPEG2 - FactoriedMyAuth - 2024-05-06

I am running a JF server with a Beelink EQ12 (N100). The system is just running the Windows JF install, since I didn't want to go too far into the weeds with this box until I know I want to keep it. 

I tried playing an SD movie with hardware acceleration turned on (QSV selected) all codecs selected. The videos refused to play. 

The UI reports: 

"This client isn't compatible with the media and the server isn't sending a compatible media format."

When I go back to hardware acceleration and turn off decoding for MPEG2, the videos play just fine. From what I can tell, this CPU fully supports QSV and should be able to decode MPEG2. I have had some issues with some 4k videos playing properly from this device as well. I am not sure if it's related or not. 

I have checked the source files with VLC, and they play just fine (this seems to be an issue with all of my DVD rips). I have attached logs.


RE: Issues Hardware Decoding MPEG2 - TheDreadPirate - 2024-05-06

Does this only happen with mpeg2 -> H264 transcodes? Or all transcodes?


RE: Issues Hardware Decoding MPEG2 - FactoriedMyAuth - 2024-05-07

It was only for MPEG2.

After posting and putting up logs, I started tinkering (since I had the issue reported before messing with settings). I started playing with settings and the "Prefer OS native DXVA or VA-API hardware decoders" box was checked. I unchecked the box and saved the settings (with MPEG2 decoding selected). That change fixed my issue. I am going to do some diving into what that box does, but that seems to have solved my issue.


RE: Issues Hardware Decoding MPEG2 - nyanmisaka - 2024-05-07

https://trac.ffmpeg.org/ticket/10274

I reported this issue one year ago. I will try to look into it again.