Yesterday, 02:01 PM
(This post was last modified: Yesterday, 02:02 PM by TheDreadPirate. Edited 1 time in total.)
The parameters of that command won't use the GPU for encoding (libx264 is a CPU encoder).
If this is a plain version of ffmpeg7, and not jellyfin-ffmpeg7, you may not have all the media drivers needed to use hardware acceleration.
You could open a bash shell into the Jellyfin container and use jellyfin-ffmpeg from within the container. JF ffmpeg comes bundled with all the Intel media drivers needed for transcoding.
Here is how a hardware accelerated ffmpeg command would look like.
BACKING UP A BIT. Can you share your ffmpeg logs from jellyfin? Dashboard > Logs. So we can see why the playback failed. I'm thinking the video is some variety of Dolby Vision.
If this is a plain version of ffmpeg7, and not jellyfin-ffmpeg7, you may not have all the media drivers needed to use hardware acceleration.
You could open a bash shell into the Jellyfin container and use jellyfin-ffmpeg from within the container. JF ffmpeg comes bundled with all the Intel media drivers needed for transcoding.
Here is how a hardware accelerated ffmpeg command would look like.
Code:
ffmpeg -init_hw_device vaapi=va:,driver=iHD,kernel_driver=i915 -fflags +genpts+igndts -loglevel error -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel qsv -hwaccel_output_format qsv -i "/path/to/video.mkv" -map 0 -c:v h264_qsv -c:a copy -c:s copy -max_muxing_queue_size 2048 -max_interleave_delta 0 -avoid_negative_ts disabled newFile.mkv
BACKING UP A BIT. Can you share your ffmpeg logs from jellyfin? Dashboard > Logs. So we can see why the playback failed. I'm thinking the video is some variety of Dolby Vision.