You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using HEVC hardware transcoding with jellyfin results in a bad picture.
The CPU is a Intel Celeron J4105.
Using software transcoding, direct play works fine.
Also VP8, VP9 and x264 hardware transcoding results in good picture with a little higher than expected CPU utilization.
Examples of the bad quality:
Big_Buck_Bunny_1080_10s_30MB_X265_OUTPUT.mp4
The package maintainer thinks the drivers are problematic, which are also a guess from the jellyfin dev.
So here I am, hoping it is a easy and quick fix! :>
looks it is an hevc encode issure? the artifacts is exist in output bitstream playback?,
I do not have a display attached, the weird output happens with different drivers.
There was a change in behavior with a different driver in the alexbelgium jellyfin add-on.
See this comment: alexbelgium/hassio-addons#537 (comment)
I've also run commands which other "jellyfin" users/devs mention to have no problems with.
I would like to refer to these two issues I've created at both alexbelgiums repo (jellyfin on home assistant add-on) which bases off the linuxserver.io add-on, which in turn uses jellyfin from the jellyfin repo.
These people have tried to troubleshoot me, there's also multiple commands listed which I've tried but did not solve the issue.
Which component impacted?
Decode, Not sure
Is it regression? Good in old configuration?
No, this issue exist a long time
What happened?
Using HEVC hardware transcoding with jellyfin results in a bad picture.
The CPU is a Intel Celeron J4105.
Using software transcoding, direct play works fine.
Also VP8, VP9 and x264 hardware transcoding results in good picture with a little higher than expected CPU utilization.
Examples of the bad quality:
Big_Buck_Bunny_1080_10s_30MB_X265_OUTPUT.mp4
The package maintainer thinks the drivers are problematic, which are also a guess from the jellyfin dev.
So here I am, hoping it is a easy and quick fix! :>
Link to the issue with the package maaintainer
Link to the issue with the jellyfin github
What's the usage scenario when you are seeing the problem?
Transcode for media delivery
What impacted?
No response
Debug Information
libva info: VA-API version 1.16.0
libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_16
libva info: va_openDriver() returns 0
Trying display: drm
vainfo: VA-API version: 1.16 (libva 2.16.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.5.4 (e461c05)
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileVP8Version0_3 : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
by-path
card0
renderD128
3 provided in step 1
4 does not work in the add-on, or I'm doing something wrong
Do you want to contribute a patch to fix the issue?
No.
The text was updated successfully, but these errors were encountered: