Comment on Handbrake local vs docker on Synology DS920+: same settings, very different results?
bigredgiraffe@lemmy.world 1 week ago
I had a few ideas, I’m suspicious that handbrake is falling back to CPU, maybe check the logs of the container to make sure it isn’t falling back to CPU decoding. Otherwise here are a few things I would check next:
- If you are not using docker locally so you are already doing this, you will need to configure the docker container to pass through the GPU for quicksync to work inside the container.
- If you are already doing that then I would make sure the device is the same name on the synology, it probably is but just to be sure.
- you will likely need to add your user to the video and/or render group on the synology if you haven’t, especially if you are running the container as your user instead of root
- make sure you are reading and writing to volumes that use bind mounts and not docker volumes, overlayfs is not what I would call fast and writing especially.
Showroom7561@lemmy.ca 1 week ago
Thanks for the ideas.
GPU does seem to be passed onto the docker container, not only because of the dramatic increase in speed, but also because the CPU isn’t being maxed out like it was before adding the GPU hardware line.
Volumes are bind mounts.
I experimented with permissions and user groups, and noticed no difference to the behaviour in render output.
For these videos, quality isn’t super important, but file size is. I spent most of yesterday tweaking settings on my local Handbrake install to get the right balance. So, I assumed transferring the settings over would give the same results.
e0qdk@reddthat.com 1 week ago
Are you running different versions of the software? (e.g. different versions of ffmpeg, maybe?)
Showroom7561@lemmy.ca 1 week ago
Same version of Handbrake (1.9.2), but I’m not even sure how to check for the ffmpeg version on my NAS, or what Handbrake is using. The system panel in the Handbrake info window doesn’t list ffmpeg at all.