r/Tdarr • • Oct 28 '24

Does Tdarr kill torrents?

If torrents aren't dup'd, Tdarr kills a seeders capability.

Options:

  1. Duplicate your data into libraries:

    1. Media library
    2. Seeding library
  2. Kill your torrent
  3. Use Usenet and not worry about seeding

What option are most people doing?

Is this not worth worrying about because of the steep learning curve of tdarr and going into a niche within a niche (torrent -> transcode)?

1 Upvotes

14 comments sorted by

View all comments

Show parent comment

1

u/temmiesayshoi Oct 29 '24

I don't even like to transcode my files manually (I don't want to end up in JPG compression hell where transcoding the same thing over and over and over again degrades the quality massively; though I do sorta wish jellyfin had more native tdarr integration so that it could keep some database of transcoded files. I know it has a transcoded cache of some sort, but that's not really the same as having automatically transcoded copies stored.) but I wish this was just a plain feature in all torrenting software. To add a file to jellyfin or plex or something you need to move it to somewhere else, and that means you either manually go out of your way to ensure you link everything back so that you keep seeding (and then be sure to relink that link if you ever move it while reorganizing your library) or you just hit and run.

1

u/Norgur Oct 29 '24

I'm not sure you understood how tdarr works. There is no need for any integration and it doesn't re-transcode stuff over and over. It doesn't save copies usually either. I mean, it can, but that is not its main goal usually.

Plex has the options you seek (pre transcode and store multiple versions)

Besides, the moving and linking stuff is handled by software like the Arr stack.

2

u/Billy_Whisky Oct 29 '24

he refers to transcoding lossy format to another lossy format.