Tdarr icon indicating copy to clipboard operation
Tdarr copied to clipboard

Docker HandBrakeCLI does not support qsv hardware encoding

Open makzdot opened this issue 2 years ago • 0 comments

Describe the bug QSV does not work for HandBrakeCLI inside the Docker install. Due to missing Debian packages related to: https://github.com/HandBrake/HandBrake-docs/issues/164

The Dockerfile is missing the following apt packages:

  • libmfx-dev
  • libmfx1

To Reproduce Steps to reproduce the behavior:

  1. Get a Docker container up and running with hardware encoding support: tdarr: hostname: tdarr container_name: tdarr image: ghcr.io/haveagitgat/tdarr:latest restart: unless-stopped environment:

    • PUID=1000
    • GUID=1000
    • TZ=Europe/Amsterdam
    • serverPort=8266
    • internalNode=false
    • webUIPort=8265
    • nodePort=8267 volumes:
    • /data/tdarr/config:/app/server
    • /data/tdarr/cache/:/temp
    • /media:/media
    • /data/handbrake/config:/config:ro
    • /mnt/tdarr:/cache devices:
    • /dev/dri:/dev/dri ports:
    • 8265:8265
    • 8266:8266
    • 8267:8267
  2. go into the docker container with "docker exec -it tdarr /bin/bash"3.

  3. Do HandBrakeCLI --help. 4.

  4. Under "Video Options" at the -e part the output should also list: qsv_h264 qsv_h265 qsv_h265_10bit But it does not.

Expected behavior It should also list the above encoders

Screenshots If applicable, add screenshots to help explain your problem.

Please provide the following information: Adding the packages to the Dockerfile should fix the problem (Tested locally)

  • Log files [can be found in /app/logs/ when using Docker or in the /logs folder next to Tdarr_Updater if not using Docker] Not needed

-Worker error [can be found on the 'Tdarr' tab by pressing the 'i' button on a failed item in the staged file section or in the transcode error section at the bottom] Not needed

  • OS: [e.g. Linux] Ubuntu 20.04.4 LTS
  • Browser [e.g. chrome, safari]
  • Version [e.g. 2.00.00] 2.00.18

Additional context Adding these packages after line 93 in the Dockerfile should fix the problem. I could not test if this breaks builds on other architectures though.

  • libmfx-dev
  • libmfx1

makzdot avatar May 28 '22 10:05 makzdot