Handbrake video converter output upside down

or got the massive high CPU usage and 'only one file in a row' issue.

either got no hardware acceleration availible.

Use the latest tag image (but i think i sorted out that is not the solution).

Played with UID und GID from 0 (root) to 1026 (my very own user) and 1024 (the admin) and the corresponding groups.

Did and did not use the privileged mode ('-privileged').

So there is no longer need to pass the 'device'.

Inserted a startup script to set those rights on every start as Synology seems to reset them.

Changed the rights to the 'dev/dri/*' path to 777.

Stopped using a command to create the container, only the Synology UI.

I tried a lot last night, put literally everything upside down and got a whole new setup. Maybe you wanna go there to discuss in german? There are a few guys with knowledge in docker and some with handbrake too.ДЄlright, lets go on here because i think this issue is somewhere arround 'user' and 'hardware acceleration'. I am from germany too, active in the kodinerds forum: I am sorry, for my knowledge there is no way to pass the '-device /dev/dri' command in the Synology GUI, thats why i use the command - but got problems with that too. Sudo docker run -name handbrake2 -net=host -restart always -volume /volume1/docker/handbrake/config:/config:rw -volume /volume1/NeueFilme:/output:rw -volume /volume1:/storage:ro -publish 5800:5800 -env USER_ID=0 -env GROUP_ID=101 -device /dev/dri jlesage/handbrake:dev-latest This is my command to run the container from a planed Synology Task: I have hardware acceleration running with almost the same configuration. Maybe i can help you or give you some information at least.Д«tw. Mevertheless my prefered way would be using the GUI because I'm not that firm with command line.

Unfortunately due to lack of knowledge I'm not able to see what's the reason. Your advice is to check the container's log for the issue. Poorly when I open the HandBrake-GUI nevertheless there is no 'H.264 (Intel QSV)'. But after all a new container was started. Took me a longer time to realize that I have to make sudo to make it. Sudo docker run -d -name=handbrake -device /dev/dri -e USER_ID=1026 -e-GROUP_ID=1000 -p 5803:5800 -v /volume1/homes/christian/HandBrake/config:/config:rw -v /volume1/homes/christian/HandBrake/storage:/storage:ro -v /volume1/homes/christian/HandBrake/watch:/watch:rw -v /volume1/homes/christian/HandBrake/output:/output:rw jlesage/handbrake My stupid question is: where do I have to write down the command '-device /dev/dri' in the Docker GUI?ДЄs there was no clue for me, I tried this command via ssh form my pc: I own a DS218+ with Intel processor listed for hardware acceleration. So likely it's an absolute silly question.ДЇirst of all: The experience with your HandBrake solution is great so far (after an longer time with problems caused only by myself until I got the conclusion between your written down start command and the transfer to the synology docker GUI).

Handbrake video converter output upside down