I’ve been trying to setup Tdarr to transcode using my AMD GPU instead of my CPU, but all I’m finding online is people using nvidia cards…well, I don’t have one of those, but I have an AMD card, so I wanted to use that, but apparently that’s extremely uncommon and I can’t find any working solutions.

  • ChickenBoo@lemmy.jnks.xyz
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    I have AMD hardware acceleration working for Plex in an LXC container with an AMD APU so I’d assume it’s possible.

    Tdarr seems to use ffmpeg under the covers, so I’d focus on getting that working with amd. If I remember I had to install the mesa drivers and pass in the /dev/dri folder. Then you can check ffmpeg for the amf encoders (AMD media framework).

    • ExcessShiv@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      4 months ago

      I actually just got it working, after spending all day yesterday. The speed is magnificent, but the compression rate is absolutely abysmal. When i use the integrated GPU an h264 encoded file end up taking up 5-10% more space as h265, whereas when just use CPU an h264->h265 is around a 45% reduction in size. I have no use for speed if it doesn’t reduce file size at all.

      • myersguy@lemmy.simpl.website
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        4 months ago

        Uh… What?

        GPU you are converting from 265 to 264 and expecting smaller file sizes, but CPU you are going from 264 to 265?

        If compression methods/codecs are equal, the hardware shouldn’t affect compression

      • exu@feditown.com
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        Besides maybe confusing the codecs, hardware encoders, especially the AMD ones, are always less space efficient than software encoders.

        If you want to convert video for long-term storage, please use a software encoder.