Hi,
Unless I’m missing something here, Sonar doesn’t pass to Transmission the the download folder, but just copies the downloaded file in the end of the download.
As Sonarr already knows my tvshows hierarchy, I wonder why it doesn’t pass the download dir to Transmission in the following format //.
This way I can continue seeding without having duplicate content on my disk.
OS: Windows 8.1
Download client: Transmission 2.8.4
Because it wouldn’t be renamed properly in the series folder.
Use hardlinking to keep a single copy of the file on disk and it will continue to seed (it will appear as two copies, but the disk space will only be consumed once).
Hard linking is an overkill in my case, but I’ll use it if I must.
The thing is that I’m not interested in file renaming, just placing them in the right folder hierarchy.
And it’s totally doable using the flexibility given by Transmission RPC.
I suspected that might be the case for you, but its a matter of overall usage as this is a very specific usecase that the larger audience of users wouldn’t use or be confused if they accidentally used it.
I realize this probably isn’t what you want, but I don’t see the effort to add and support this worth it to Sonarr at this time.
I started making a new topic and the very nice forum software found this one for me so I’m replying here instead.
Adding a +1 to the request.
I must be missing something, because I really can’t understand why this is a rare use case. I get all my TV from a tracker that is a supported indexer. Prior to starting to use Sonarr I manually selected the download directory for everything - I put it straight in my media library and seed it forever. I don’t copy anything, I don’t rename anything - I just download it and let Kodi’s scraper pick it up and I watch it. Years ago people did strange things with names, but these days (on a private tracker at least…) things are named well enough that a reasonable scraper can figure out what it is. Why does anyone care what the directory or file names look like on disk?
Edit - been thinking some more. I (think) I understand the default behaviour for Usenet which I understand is Sonarr’s “heritage”, but is there really any reason do have this “download directory and move library” workflow for torrent downloads? Maybe people use combinations of Usenet and multiple torrent Indexers…
Thanks for reading my first post here
BTW, I’m a UNIX admin. I understand how hard links work etc. It just seems messy… (and my misc., default, download directory is on a different filesystem than my media library.)