Search the Community

Just migrated to a new QNAP (TVS-951X) and there was an issue getting vaapi working in my emby docker container. In QTS 4.3.6.0875 there are no default system groups (like video) and the /dev/dri folder is owned by admin:administrators with restrictive permissions, which are reset upon reboot. It was necessary to create an autorun.sh script to set things up for docker use. #!/bin/bash chown admin:video /dev/dri chmod 775 /dev/dri chown admin:video /dev/dri/* chmod 660 /dev/dri/* The docker needs to run as a user assigned to the video group (or have the video group's GID listed in GIDLIST), run in privileged mode, and have /dev/dri passed through as a device. This enables vaapi for me - qsv's a no-go. Edit: Something like this is (probably only) needed when running the docker as a non-root user.

When transcoding movies, even with hardware acceleration turned on on the server, all of the work load is being put on the CPU for both decoding and encoding. Im pretty new to this and dont have much knowledge about how this works. -More specific specs- Processor: AMD FX-3600 Six-Core Processor GPU: Nvidia GTX-960 4GB Ram: 8.00GB DDR3 It might just be something simple i am missing, but no matter what setting configuration i have set, all of the work is done via cpu. From what i am aware, a GTX-960 should be capable of both decoding and encoding. In a recent ffmpeg log file i noticed this following message, I'm not sure if it helps: [h264_nvenc @ 00000206e4fe00c0] Cannot get the preset configuration: invalid version (15)Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameterssuch as bit_rate, rate, width or heightConversion failed! Attatched are my transcoding options, ffmpeg log while transcoding a 1080p movie, and a hardware detection log. Any help to get my GPU to do something would be greatly appreciated ffmpeg-transcode-2d389333-b984-4ddc-8d5f-468abc80f562_1.txt hardware_detection-63686804671.txt