What's your process for recoding? I'm nearing 120tb used space and would like to re-encode some of the stuff my *arr stack grabbed before I got my profiles tuned in.

[–] Darkassassin07@lemmy.ca 2 points 3 months ago* (last edited 3 months ago) (5 children)

https://home.tdarr.io/

I used to use the built in convert options in Emby server, but recently switched to Tdarr to manage all my conversions. It's got far more control/configurablity to encode your files exactly how you'd like.

It can also 'health check' files by transcoding them, but not saving the output; checking for errors during that process to ensure the file can actually be played through successfully. With 41k+ files to manage, that made it much easier to find and replace the dozen or so broken files I had, before I found them by trying to play them.

Fore warning; this is a long and intensive process. Converting my entire library to HEVC using an RTX 2080 took me over 2 months non-stop. (not including health checks)

[–] vulgarcynic@sh.itjust.works 1 points 3 months ago (4 children)

Awesome. Thanks for the info. I have been running Plex for years and started the switch to Jellyfin last year. Have a container running Emby but haven't put any work in to configuring or much yet.

Same situation with Tdarr. Threw together a quick container and got caught up in a billion other projects. I have an old 3600x / 1080ti system I'll likely use as a transcoding node. Just need to go over the docs and figure out how to setup input / output paths.

[–] Darkassassin07@lemmy.ca 1 points 3 months ago

Configuring input/output paths are only really necessary when you have multiple systems that don't see the media at the same paths. Such as a Linux server and a Windows node working together.

Honestly, I just wish I'd have known about and set it up sooner:

load more comments (3 replies)

load more comments (14 replies)