this post was submitted on 13 May 2024
21 points (100.0% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

52563 readers
297 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

💰 Please help cover server costs.

Ko-FiLiberapay

founded 1 year ago
MODERATORS
db0@lemmy.dbzer0.com
sunbrothersco@lemmy.dbzer0.com
dataprolet@lemmy.dbzer0.com
Flatworm7591@lemmy.dbzer0.com
RandomLegend@lemmy.dbzer0.com
21
Tdarr AMD GPU transcoding...how? (lemmy.dbzer0.com)
submitted 1 month ago* (last edited 1 month ago) by ExcessShiv@lemmy.dbzer0.com to c/piracy@lemmy.dbzer0.com
8 comments fedilink hide all child comments
 

I've been trying to setup Tdarr to transcode using my AMD integrated 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 CPU with integrated gpu, so I wanted to use that, but apparently that's extremely uncommon and I can't find any working solutions.

Edit: I'm running Tdarr in a docker container on my OMV media server.

Edit 2: I've gotten it working, but the compression is nonexisting. A h264 -> h265 transcode increases file size by ~5%.

Needed to add my Tdarr container to the render group and pass through the dev/dri/renderD128 folder.

you are viewing a single comment's thread
view the rest of the comments
[–] Stubborn9867@lemmy.jnks.xyz 4 points 1 month ago (1 children)

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.com 3 points 1 month ago* (last edited 1 month ago) (2 children)

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 when converted to 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.

[–] exu@feditown.com 4 points 1 month ago (1 children)

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.

[–] ExcessShiv@lemmy.dbzer0.com 1 points 1 month ago

Fair enough, I just saw so many using GPUs and how much faster it was and assumed it was the same size-wise with the files. I'm getting ~40fps with my CPU, so it's going to take forever to do all of it.

[–] myersguy@lemmy.simpl.website 2 points 1 month ago* (last edited 1 month ago) (1 children)

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

[–] ExcessShiv@lemmy.dbzer0.com 2 points 1 month ago

Maybe I worded it poorly, I'm doing h264 -> h265 in both cases, but it increases file size when using iGPU.