so my understanding is, when hdtv is found, it will download it 55 mins later from usenet, then after 300 minutes, torrents will evaluate the search then find web dl and download it
is that correct? if not, what settings sohuld i use?
The only thing you can be sure of are the delays (minimum age and torrent delay).
Depending on the preferred protocol in your delay profile and when a release becomes available on an indexer, sonarr may grab a usenet or torrent download.
The “then” in this sentence is not correct. There is no relation between these events.
Sonarr just regularly gets the RSS feed from your indexer and applies the rules (minimum age and torrent delay).
If a torrent is seen on the RSS feed, the 300 minutes will start ticking from the moment sonarr saw it. There is no relation with when a previous release was seen or downloaded or something like that.
once HDTV is detected, it is usually detected in both nzb and torrent, so after 55 mins it will download the usenet hdtv version, and in 300 mins from the time it discovered the first hdtv in torrent indexer, it will find the web dl and upgrade the first version right?
Not entirely All torrent releases are delayed for 300 minutes from the time they are seen on the RSS feed. Not from the time it discovered the first hdtv in the torrent indexer.
Consider this scenario:
00:00 HDTV torrent is available on RSS. It is held until 05:00 (300 minutes torrent delay).
01:00 HDTV usenet is available on RSS. It is held until 01:55 (55 minutes minimum age delay).
01:55 HDTV usenet is sent to your download client and downloaded. The torrent “on hold” is given the boot because a comparable release is downloading via usenet and it’s not 05:00 yet.
(So far following your reasoning)
Then:
04:00 WEBDL torrent is available on RSS. It is held until 09:00 (300 minutes torrent delay).
Scenario A:
No WEBDL becomes available on usenet RSS between 04:00 and 09:00
09:00 WEBDL torrent is sent to your download client and downloaded.
Scenario B:
07:00 WEBDL usenet becomes available on RSS. It is held until 07:55 (55 minutes minimum age delay).
07:55 WEBDL usenet is sent to your download client and downloaded. The WEBDL torrent on hold is given the boot again because it’s not 09:00 yet.
You don’t need a delay profile to achieve that, just set the cutoff in the quality profile to WEB-DL (or higher) and Sonarr will upgrade to it when it sees it.
One use for a delay profile is to prevent gabbing one quality then a few hours later grabbing another quality (save bandwidth), the other is to add a delay to the non-preferred protocol, such as a delay on torrents to prevent Sonarr from grabbing a torrent when it’s first posted and instead wait for usenet, but if usenet is too slow (past the torrent delay) grab the torrent.
That’s not how tags work, the tags would be used to used to limit indexers to series with the same tags, same as how tags limit notifications to series with the same tags. IE you want to use a public tracker for some series you can’t get anywhere else, but don’t want to use it for every series.
Why are you wanting to limit WEB-DL to torrents and HDTV to usenet?
because what happens is, sonarr grabs hdtv from torrent, then deletes it and download webdl later, so now i am seeding both files (which is odd since sonarr deletes the hdtv file tho it still seeding)
i want to stop this since i dont even understand how it is seeding a file that dont exist anymore
Sonarr doesn’t move the file when it imports a seeding torrent, it copies or hardlinks it. The file it deletes isn’t the seeding file, so seeding continues.
If you don’t want the HDTV release immediately you could put a longer delay on both usenet and torrents and have it grab the best quality release when the delay expires.
The granular control you’re looking for isn’t something that Sonarr supports and not something we intend to support either.
i know it hardlinks it, but once sonarr upgrade hdtv to webdl, it deletes the hdtv version but somehow the seeding for both torrents continue, this should not be possible…also most private trackers have HnR rules, so when sonarr upgrade hdtv file it should keep seeding for x mins, but i highly doubt this is written in sonarr code, so when it does upgrade and the old file is removed, how is it still seeding?
The file the client downloaded is not deleted, moved or otherwise altered. When the hardlink is deleted that original file is not altered in any way so it continues to seed.
Look at the file your download client is pointing to and you’ll see that is still there, after Sonarr imports it and even after Sonarr deletes the hardlink or copy that it imported in order to import the upgraded file.
thats the thing tho, once sonarr upgrade the file to webdl and the client is still seeding the old hdtv file, the actual and hardlinked hdtv is gone…if i click “open container” it opens an empty folder, it is seeding nothing…
ok after some researching it seems download station create hidden files and keeps seeding fine