What I thought would happen is that as soon as the HDTV 720p release shows up, THEN the 4 hour timer starts. When the timer is up, itāll grab whatever is the highest quality in my profile at that time.
However itās just grabbing all the HDTV 720p releases straight away.
Honestly Iām not sure what the difference is between First, Cutoff and Always, as they all kind of sound like the same thing to me.
Youāre right about how itās supposed to work, thatās exactly it. The timer starts when its posted, so if drone doesnāt see it for an hour it would only wait another 3 hours.
The delay is also skipped for searches, since it doesnāt fit with the idea of searching.
In history you can see the age at the time drone grabbed the relwaee. (On the grab event). What does it show?
Thatās obviously not true as it was just put up, but I see that a lot with the indexers (the age is often pretty whacky). Thatās a problem then. Is it possible for Drone to start the timer when it first seeās the release show up, rather than what the indexer reports? That means keeping a bunch of data for each NZB though which isnāt great
EDIT: Unless itās a timezone thing? Iām in Australia so perhaps itās being offset?
Depends on the indexer, but drone should be handling the time in most cases and taking timezones into account. Either that indexer reports the time wrong or drone is misinterpreting it.
Knowing the indexer and the release might help figure it out.
I think for most indexers thatās the time is was posted to the newsgroup itself and not the time it was indexed. I know for a fact that sometimes there is a release Iām looking for and itās not on my indexer at 2PM but it is at 3PM, at which point it will say it was posted 3 hours ago. Iām not sure if Drone uses this time or its own internal timekeeping to determine how old a release is. I think the latter would be a safer bet.
I am too in Australia and with the time difference new shows are released at between 12pm and 3pm on average here so perhaps you can work out what you need so it fits within that time frame each day
These are covered in the tooltip, Iām not adding a lot of info.
Cutoff - always delay for the full length of the delay until the cutoff is met or exceeded, once its reach the release meeting or exceeding it would be grabbed immediately
Always - Always delay for the full length of the delay for all qualities, including the cutoff being met or exceeded.
All options will grab immediately if its the quality matches the top wanted/allowed quality in the profile.
@simonk83 found the issue with Wombleās it was treating the publish date as a local time, instead of UTC/GMT, in your case that resulted in times appearing in the past by 10 hours, whereas I was seeing them in the future by a few hours.
I just pushed a fix that will correct this behavior for Wombleās, so you should be able to keep using it if you want.
With a delay of 6 hours, First will wait 6 hours from the first release and grab the best release at that time, so at 12am it would grab WEB-DL 720p (assuming WEB-DL 1080p wasnāt available as well).
Always will always delay, no matter what, in your example, if WEBDL 720p was the cutoff it would delay the full 6 hours before grabbing it, then another 6 when WEBDL 1080p came out.
Cutoff if WEBDL 720p was the cutoff, it would immediately grab the WEBDL-720p when it became available
Oh right, OK. So Cutoff works like first (once the first release pops up, the timer starts), but rather than waiting for the timer to expire then grab the best release, itāll grab the cutoff release immediately without waiting (assuming itās available of course)?
Not exactly, cutoff will reset the timer for each quality, but it will immediately grab when the cutoff is met or exceeded, whereas always would still wait for the full timer to expire.
First is the only one that uses the oldest release as the timer for all releases.
Sorry to open an old post but I have similar question regarding the original post. Being in Australia - the use of the delay option is very important to me. Having just moved from sickbeard to Sonarr - I was intrigued to see the option of a delay - something that sickbeard does not have.
markus101 - you said that the setting of āalwaysā in the example above -
āFirst will wait 6 hours from the first release and grab the best release at that timeā
Just to clarify - does that mean Sonarr will wait 6 hrs from itās air date time and not go looking for an episode for 6 hrs - or - it will be looking for an episode from the release time in the US and once it finds a copy it will then wait 6 hours?
The āwill wait 6 hours from the first releaseā is throwing me a bit.
As an example -
Brooklyn Nine-Nine
Airs Fri. Jan. 02, 8:00 PM on Fox
San Francisco (U.S.A. - California) Friday, 2 January 2015 at 8:00:00 PM PST UTC-8 hours
Melbourne (Australia - Victoria) Saturday, 3 January 2015 at 3:00:00 PM AEDT UTC+11 hours
If Sonarr is running on my system - starts looking for the show on Fri 2nd Jan 8PM - it will not actually air for another 19 hours. Probably wonāt see a posting for 20-21 hours at the earliest. As you can see - I really donāt want Sonarr to go off every 1-2 hours for 20 hours looking for something that is not there.
So - if the āalwaysā option is truly a delay looking for episodes for x hours - that would be fantastic for me.
When its posted to usenet, the time it airs is irrelevant.
Sonarr doesnāt find episodes by searching and the times it stores are UTC, so they show properly in your timezone, this answer in the FAQ explains how episodes are found: https://github.com/Sonarr/Sonarr/wiki/FAQ#how-does-nzbdrone-find-episodes (Currently times are off due to losing the provider we were using for UTC times, but those will be back).
IN the next release delays are going to change quite a bit, so its not worth going into much detail; always is going away and it will be based off of first (delay off the first post and grab the best quality available at that time). There will be a separate delay to delay all usenet grabs by X minutes to deal with propagation issues.
