Handbrake local vs docker on Synology DS920+: same settings, very different results?

Comments

• XTL@sopuli.xyz ⁨4⁩ ⁨weeks⁩ ago

  If all the settings and options match, my first suspicion would be that there’s a library available on one system and not the other. Have you taken very verbose logs to see if there’s differences that stand out?

  source

  • Showroom7561@lemmy.ca ⁨4⁩ ⁨weeks⁩ ago

    Have you taken very verbose logs to see if there’s differences that stand out?

    Nope, but that could be a next step. I was hoping for an easy fix (like I did something wrong in the settings).

    Realistically, if this can’t be solved by using the built-in setting options, then it’s not worth the trouble to “fix” anything. It still works, so I’m glad to have the option.

    source
• bigredgiraffe@lemmy.world ⁨4⁩ ⁨weeks⁩ 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.

  source

  • Showroom7561@lemmy.ca ⁨4⁩ ⁨weeks⁩ 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.

    source

    • e0qdk@reddthat.com ⁨4⁩ ⁨weeks⁩ ago

      Are you running different versions of the software? (e.g. different versions of ffmpeg, maybe?)

      source

      • -> View More Comments
• scrubbles@poptalk.scrubbles.tech ⁨4⁩ ⁨weeks⁩ ago

  IIRC, presets are machine dependent, or at least they are optimized for the hardware. So if you have a weak machine, veryfast will use even worse encoding because you’re simply saying “I just want it done fast”, while on a more robust machine it may take more liberties. To match it completely I think you need to disregard the presets and set everything yourself, like CRF and everything.

  source

  • Showroom7561@lemmy.ca ⁨4⁩ ⁨weeks⁩ ago

    To match it completely I think you need to disregard the presets and set everything yourself, like CRF and everything.

    Is there a way to disable the preset completely? There’s no “none” option, just “speed, balanced, and quality”, but I set everything else up manually.

    source

    • scrubbles@poptalk.scrubbles.tech ⁨4⁩ ⁨weeks⁩ ago

      Sorry I usually work directly with ffmpeg and that’s how I had the hunch, those presets are h264 presets that go in. But does it matter, you said you were only curious, I think that’s why, so now you know

      source
• ClydapusGotwald@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

  Why are you encoding a file that’s already been encoded?

  source

  • Showroom7561@lemmy.ca ⁨4⁩ ⁨weeks⁩ ago

    Basically saving space. The dashcam I use records in h264, and I’ve been saving space (50%) by converting them to h265 (through my Samsung phone). Handbrake is far more convenient for these batch conversions.

    source
• isgleas@lemmy.ml ⁨4⁩ ⁨weeks⁩ ago

  What are the specs, hardware wise, of both your laptop and your nas?

  source

  • Showroom7561@lemmy.ca ⁨4⁩ ⁨weeks⁩ ago

    The NAS (Synology DS920+):

    • CPU: Intel Celeron J4125 4-core 2.0 GHz, burst up to 2.7 GHz
    • RAM: upgraded to 20GB
    • NVME cache: 256GB
    • HDD are all Seagate ironwolf 8GB x 3 and a 4TB.

    Laptop (Framework 13 11th Gen intel):

    • CPU: Intel Core i5-1135G7 (integrated Iris Xe Graphics 80EU)
    • RAM: 64GB
    • Storage: 2TB WD Black 770

    I would expect a difference in speed between the two, but does the hardware affect the output quality/size if the settings are identical?

    source

    • ms_lane@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

      but does the hardware affect the output quality/size if the settings are identical?

      Yes, your laptop has a much newer quicksync block with proper HEVC hardware-

      NAS is Gemini Lake, which uses QS from Broxton/Apollo Lake/Gemini Lake

      Laptop is Tiger Lake, which uses about 3 versions newer QS, for Tiger Lake, Alder Lake and Raptor Lake.

      Broxton QuickSync doesn’t actually have an asic encoder path for HEVC, it’s all via shaders.

      source

      • -> View More Comments
• non_burglar@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  Your settings are not 1 to 1 on both systems, you’ll have to identify what “auto” means in each context, it’s variable depending on where ffmpeg lives.

  source

  • Showroom7561@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago

    Unfortunately, the only other alternative to “auto” under Profile is “main”, which I have no idea what it does.

    And under level, it’s either “auto” or a bunch of numbers.

    That said, I was under the impression that any manual settings would override the settings in the “auto” profile. Is that not the case?

    source