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
If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.
Expected Behavior
hevc (native) -> h264 (h264_omx) transcodes should not automatically uncheck h264 hardware decoding.
Current Behavior
Transcoding a h264 -> h264 file right after enabling h264 hardware decoding works:
That's an upstream issue and they seem to be aware: jellyfin/jellyfin-ffmpeg#29 (comment)
You can open an issue in the jellyfin repo if there isn't one already
If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.
Expected Behavior
hevc (native) -> h264 (h264_omx)
transcodes should not automatically uncheck h264 hardware decoding.Current Behavior
Transcoding a
h264 -> h264
file right after enabling h264 hardware decoding works:However, after attempting a
hevc (native) -> h264 (h264_omx)
transcode:h264 hardware decoding will be unchecked magically.
When trying the same
h264 -> h264
transcode on the same file, we see this:Steps to Reproduce
Environment
OS: Raspbian (RPi4B 4GB)
CPU architecture: arm32
How docker service was installed: Running k3s on cri-o
Command used to create docker container (run/create/compose/screenshot)
Docker logs
Nothing in the logs reflects why it happens.
The text was updated successfully, but these errors were encountered: