Hey, I had the same issue. I’m guessing that you enter a tag and click Save straight away.
Rather than doing that, just press tab or something, then you’ll see the tag you just entered appear in the box in blue, with a small x to remove it again… then click Save.
I’m really not getting tags. In Delay Profiles, isn’t the tag just the name of the Delay Profile (must be at least one per profile and cannot be used in more than one profile). If so, why not just list the Delay Profiles by the tag and call it the name, and select them in Series from a dropdown list?
You can set more than one tag for one Delay Profile, but why would you ever want to do this?
I feel like tags need their own area, for defining, viewing, organizing. I’m sure they’re incredibly powerful, but less than immediately intuitive-- to me anyway. If there’s a wiki (hopefully with real-world examples), could someone please direct me there…Thanks
Also, how do we define the cutoff delay in Quality Profiles now? With tags too? How? wiki?
During the conversion we created tags that were the “name”, but it doesn’t have to be done that way. We didn’t want to limit/require a delay profile per series, so we let them be assigned by tags. While you don’t need to use more than one tag, you could, really depends how you want to organize it.
They definitely do and its something we will be adding in.
I think I’m getting delay tags now, but a few questions…
Am I correct in assuming: If a delay tag is set for a series, as soon as a release is found for a wanted episode an attempt is made to grab it if the quality is equal to or higher on the list than the cutoff quality (higher on the list preferred). If successful, it stops searching and we’re done. If not, the delay timer starts as per the delay tag. It continues to search for those qualities, but when the delay timer runs out, if it still has come up with nothing, it removes the cutoff restriction and now includes all qualities enabled in the profile (higher on the list preferred), stopping if and when a qualifying quality is found and successfully grabbed. This algorithm would never see two different qualities grabbed for the same episode, since the first successful grab stops the search. Is this correct?
I think I read on reddit that the delay is applied twice, once as above, but also before that, before anything is grabbed. Is this right? I hope not. I want to try for SD for 24 hrs (delay after first release appears) but proceed to HD after 24 hrs if no SD shows up. However, I don’t want to wait 24 hours for the SD, if it’s there from the start, and I don’t want the HD if SD is found.
If there were two delays I would like the first to be a separate grab-nothing (propagation) delay, which would typically be set low, like 20 minutes to wait for full propagation to usenet servers, and then the regular delay, typically longer, that waits to remove the cutoff. At first I thought the default delay profile was essentially a propagation delay, but it appears no, it’s the delay for series with no delay tag set, and therefore have no delay value to use for the quality profile’s cutoff.
It will only grab immediately if the quality is the best wanted on in the profile, in the default HDTV 720p profile that would be Bluray 720p, if it was HDTV 720p that it found (the default cutoff) the delay would apply, same for WEB-DL 720p, since its not the most preferred in the profile.
Only if the cutoff is reached.
The propagation delay will apply to all qualities and like you mention later, is a shorter time frame, just to let things propagate, the delay from a delay profile would extend past that, but not added to it, a 20 minute propagation delay and a 1 hour delay from the profile would result in a 1 hour delay total.
Set you profile to have SDTV and HDTV 720p with the cutoff at SDTV.
The propagation delay (minimum age is separate), the default applies to any series that doesn’t have another delay profile applied via tags.
Is the “best” determined by what’s at the top of the list? Am I correct that best wanted simply means enabled and highest on the list, or are you referring to highest vid quality (resolution)?
So if the highest preferred quality (top of the list) is not found we run the full delay period waiting for it. After which, from any releases we may have found thus far we immediately grab the most preferred. If it’s found nothing the cutoff is removed and then does it wait through the delay period again before determining what is most preferred to grab, or is the delay at this point essentially the sync interval and it grabs immediately whatever it finds that’s enabled…?
What would you recommend for the minimum age setting to reasonably account for propagation? Not sure, I was thinking maybe 15 minutes?
I am seeing unexpected behavior. Today an episode file that was grabbed successfully 21 days ago (HD) was deleted by Sonarr and replaced by a more preferred (SD) file that was posted today. Why would it go back and upgrade this episode from 21 days ago that was already grabbed? I thought that once the delay period expired (I have it set to 7 hours) it would take the most preferred available at that time, and stop. Causing a lot of unnecessary downloading.
I guess I don’t understand the purpose of the cutoff, but if it means a particular quality is required to stop the monitoring and surprise deletes/re-grabs on all my shows’ past episodes – then I definitely don’t want it. This makes me very nervous, and defeats the purpose of my preferring SD (preserving metered data). I want to know it’s stopped trying at some point (in time) once its grabbed something, anything.
Maybe I should just get rid of cutoff by setting it to my least preferred quality, and increase the propagation delay to 7 hours hoping it will then take the most preferred that’s available at that time and keep trying only if NOTHING is found.
If you only want to grab an episode once and never upgrade then cutoff needs to be set to the lowest quality in the list, otherwise it will continue to look for upgrades. Setting the cutoff higher means Sonarr will keep looking for a better release until the cutoff is met or exceeded.
OK I’ll give that a shot, thanks. I would like to upgrade, but only for a set period of time, at which time take most preferred and stop. Hopefully the propagation delay will provide that time for competing releases to appear.
So what will the Usenet Delay value do when the cutoff is set to lowest preference on the list? Will it be ignored or will it wait the delay before choosing which to grab?
I don’t want Sonarr to just grab the first release that appears and stop, I want to set an initial time delay to allow competing releases to appear, and then grab the most preferred and stop. Can I use the Usenet Delay to achieve this, or would it be better to set Usenet Delay to zero and use the propagation delay? Usenet Delay would be better, if it can work for this, because its per-Profile while the Min Age setting is global.
and should be making it’s way into develop and then master soon.