![]() So in this situation tracker A outweighs tracker B but when adding the quality weight, tracker B with 1080p outweighs tracker A with 720p. So you can weight tracker A as 5 and tracker B as 3 meaning tracker A is preferred to tracker B. With a weighted system the user can assign values to various variables. I'd just prefer that, all things being equal, oznzb be the source of the nzbs that get queued up.Īfter thinking about it more, I think a weighted system is the way to go. Not really what Sonarr's decision tree looks like for how it deals with getting multiple answers - maybe it just takes the first answer it gets? Anyways, I'd prefer not to have to disable all other indexes but oz to get the benefit of this sab feature, since having multiple indexes enabled gives a bit better coverage and reliability. I've noticed recently that oznzb is rarely getting nzbs pulled from it, even when the exact same release is available in it and other indexers. None of my other indexers support this integration however, so all things being equal, I'd absolutely prefer sonarr to pull nzbs from oz than elsewhere. SABnzbd+ has a delightfully useful integration with oznzb that auto-pulls and displays user ratings from queued nzbs, putting those ratings right inline with the download in the interface. The scenario below is what prompted me to google sonarr indexer prioritization, resulting in my finding this page and creating an account just to help clarify for the devs and the community why one user might care about this feature: ![]() Comment from erikneff on For what it's worth, 2) is exactly what I would like, and is the reason I'm here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |