[Issue]: Trickplay image generation failing about jellyfin HOT 6 CLOSED

The mjpeg encoder has a very limited hardware platform support, and I don't think it is compatible with anything but Intel atm.

from jellyfin.

Try disable hardware encoding for trickplay and see if it would success.

from jellyfin.

@gnattu thanks, seems like the following option was the culprit:

Unchecked it and ran the task again and now it's progressing fine.

I am using VAAPI though; maybe an incompatibility with AMD GPUs? Feel free to close the issue if this is intended behavior.

from jellyfin.

Closing as hardware compatibility issue

from jellyfin.

@gnattu I'm seeing this using an Intel GPU (A380) with 10.9.1 when hardware encoding is enabled - for whatever reason, though, I'm seeing ffmpeg's stderr in logs. The error I'm seeing is [mjpeg_vaapi @ 0x557871ed2480] Invalid quality value 472 (must be 1-100). Is there anything actionable that could be done (on Jellyfin's side) to fix this or is it just a matter of needing to leave hardware encoding off until the hardware encoder matures?

FWIW, execing into the container and manually running the ffmpeg command with lower qscale values does yield changes, but the only value that works is 0, which isn't even in the documented valid range for that value (1-31). 1 still yields Invalid quality value 118 (must be 1-100)

from jellyfin.

@gnattu I'm seeing this using an Intel GPU (A380) with 10.9.1 when hardware encoding is enabled - for whatever reason, though, I'm seeing ffmpeg's stderr in logs. The error I'm seeing is [mjpeg_vaapi @ 0x557871ed2480] Invalid quality value 472 (must be 1-100). Is there anything actionable that could be done (on Jellyfin's side) to fix this or is it just a matter of needing to leave hardware encoding off until the hardware encoder matures?

FWIW, execing into the container and manually running the ffmpeg command with lower qscale values does yield changes, but the only value that works is 0, which isn't even in the documented valid range for that value (1-31). 1 still yields Invalid quality value 118 (must be 1-100)

Hardware encoders use different definition of quality. For VAAPI, what you are specifying is the quant and will be multiplied by 118 to get the real quality but that one ranges from 1-100. Such conversion probably should be handled by server otherwise the user can only use the default value.

from jellyfin.