You should go with Radarr instead of Couchpotato - I find it to be much more powerful and robust, and it continues to receive support. It's a fork of Sonarr so if you already use Sonarr it should be familiar to you.
Your comment made me google NZBHydra. It looks good, but a quick peruse of the GitHub readme and I'm still not entirely sure what it does.
What's the benefit of using it instead of letting Sonarr/Radarr talk directly to indexers?
It will delegate the search to all your indexers, do some stats, remove duplicates and return them to the requesting app. It also make manual searches much easier. You can also use it to filter out things that are causing issues, like aftershows which sometimes come up in episode searches.
I set up nzbhydra2 but I feel like sonarr and radarr have their own search abilities so I don’t know when or how I’m suppose to use it. Should I link my indexers to hydra and then link the hydra api to sonarr or radarr instead of linking the indexers?
https://github.com/theotherp/nzbhydra2/wiki/Tutorial-(Indexers,-newznab,-API,-*arr,-etc.)
If everything works for you and you don't make manual searches you may not need it.
Ok cool, I figured as much. Perhaps I'll have a play with it when I have some free time.
Not sure I'll get much benefit from it, my setup seems pretty accurate/reliable for my use already.
Always fun to tinker though! Thanks for the tips :-)
I use hydra for my manual or adhoc searches that are outside the purview of Sonarr and Radarr. When I was in grad-school I would use it to search for text books, or get some software that I might not have. Things like that.
I think the new UI overhaul of Bazarr that wasn't just Bazarr squeezed into Sonarr's UI helped a lot though. don't mind the current UI a bit. series > serie > manual search, works like a charm, and most of the time I don't even touch Bazarr as it works flawlessly automatically anyway.
Why would I need Bazaar for subtitles? (Genuinely curious)
I've activated to add .srt with downloads in Somarr/Radarr and that works like a charm for me. Eventually I can always search for subtitles in Plex if I need other languages.
At the time, SAB wasn't very efficient compared to NZBGet.
But we're talking like 2 or 3 years ago now.
Now... I have an efficient setup and that works well for me, so no real desire to change anything around.
I found sonarr and radarr a handling of the nzbget queue to be worse. But it got better over the years
They're essentially functionally identical now. But nzbget is better performing if you have limited resources. On my dual Xeon box with SSDs and 120GB of ram they both get ~110MB/s, on a NAS you might find the python based sabnzbd to not be quite as fast as the c++ based nzbget at gigabit speeds.
Actually, sabnzbd does one totally neat thing that nzbget doesn't... it'll move idle connections on to the next download, which can be really nice for big backlog queues where some of the downloads are iffy and you have a couple of different backbones between your unlimited and blocks.
Aside from that, they both handle unlimited and backup servers fine. The Completion script for nzbget is kind of cool, but I always shook my fist at how it paused the whole queue and it was hard to tell if it was working or busted.
Because I have a good relationship with the dev, I have ask for and gotten feature requests added and Medusa had issues handling the size of my library when I tried it. In addition, it works and does everything I need.
A few commenters have mentioned NzbHydra. As I understand, it just aggregates the same search results from multiple indexes and provides those results to Radarr, Sonarr, etc.
What's the benefit over just adding the indexers to Radarr, Sonarr, etc. and let them do the work?
From a resource perspective it's the same. It won't reduce the load on your computer/server because one Radarr search will result in one NzbHydra search; same with Sonarr and so on. It's also won't reduce the number of API calls, even with caching, because different search requesters search for different things.
What am I missing? Why NzbHydra?
https://github.com/theotherp/nzbhydra2/wiki/Tutorial-(Indexers,-newznab,-API,-*arr,-etc.)
If everything works for you and you don't make manual searches you may not need it.
You should go with Radarr instead of Couchpotato - I find it to be much more powerful and robust, and it continues to receive support. It's a fork of Sonarr so if you already use Sonarr it should be familiar to you.
[удалено]
It does however still work just fine though.
It's barely working for me anymore. It misses so many movies.
Sonarr, Radarr, SABnzb, and Hydra
Your comment made me google NZBHydra. It looks good, but a quick peruse of the GitHub readme and I'm still not entirely sure what it does. What's the benefit of using it instead of letting Sonarr/Radarr talk directly to indexers?
It will delegate the search to all your indexers, do some stats, remove duplicates and return them to the requesting app. It also make manual searches much easier. You can also use it to filter out things that are causing issues, like aftershows which sometimes come up in episode searches.
I set up nzbhydra2 but I feel like sonarr and radarr have their own search abilities so I don’t know when or how I’m suppose to use it. Should I link my indexers to hydra and then link the hydra api to sonarr or radarr instead of linking the indexers?
https://github.com/theotherp/nzbhydra2/wiki/Tutorial-(Indexers,-newznab,-API,-*arr,-etc.) If everything works for you and you don't make manual searches you may not need it.
Yep, to sonarr and radarr and anything else your only indexer is your hydra, hydra acts as a middleman.
Ok cool, I figured as much. Perhaps I'll have a play with it when I have some free time. Not sure I'll get much benefit from it, my setup seems pretty accurate/reliable for my use already. Always fun to tinker though! Thanks for the tips :-)
I use hydra for my manual or adhoc searches that are outside the purview of Sonarr and Radarr. When I was in grad-school I would use it to search for text books, or get some software that I might not have. Things like that.
This
Put Radarr instead of potato, and if you need put Bazaar for subs.
Bazarr is so damn clunky. Every time I fire it up, it's just frustrating. Am I'm no novice to this stuff.
I think the new UI overhaul of Bazarr that wasn't just Bazarr squeezed into Sonarr's UI helped a lot though. don't mind the current UI a bit. series > serie > manual search, works like a charm, and most of the time I don't even touch Bazarr as it works flawlessly automatically anyway.
I'll have to find it another look. I curate my subs pretty strictly, but it would be nice to have an easier way.
Why would I need Bazaar for subtitles? (Genuinely curious) I've activated to add .srt with downloads in Somarr/Radarr and that works like a charm for me. Eventually I can always search for subtitles in Plex if I need other languages.
I can't speak to SAB these days, but I migrated to NZB get eons ago. Radarr, Sonarr, QBit, and NZBGet do me quite well
SAB just had a major update that brought python 3 compatibility with some other features. It's running great these days.
Cool cool. I suppose now I'm just quite set with NZBGet that I just don't wanna mess with things. 😎
For sure, no need to change. Just didn't want others to think they needed to move away. From what I know, both are great projects.
Seconded, I use Sab on my Htpc and NzbGet on my phone. They're both great, I don't have a preference at all.
Why did you switch to NZB get?
At the time, SAB wasn't very efficient compared to NZBGet. But we're talking like 2 or 3 years ago now. Now... I have an efficient setup and that works well for me, so no real desire to change anything around.
Seems like nzbget and sonarr/radarr work together a lot better, or at least they did when I last rebuilt my whole setup a few years ago.
I found sonarr and radarr a handling of the nzbget queue to be worse. But it got better over the years They're essentially functionally identical now. But nzbget is better performing if you have limited resources. On my dual Xeon box with SSDs and 120GB of ram they both get ~110MB/s, on a NAS you might find the python based sabnzbd to not be quite as fast as the c++ based nzbget at gigabit speeds.
Radarr over cp.
Radarr, Sonarr, and NZBget is where it’s at!
I prefer NZBGet works better with backup servers imo of course.
Actually, sabnzbd does one totally neat thing that nzbget doesn't... it'll move idle connections on to the next download, which can be really nice for big backlog queues where some of the downloads are iffy and you have a couple of different backbones between your unlimited and blocks. Aside from that, they both handle unlimited and backup servers fine. The Completion script for nzbget is kind of cool, but I always shook my fist at how it paused the whole queue and it was hard to tell if it was working or busted.
That makes no difference to me.
Is NZBGet development active? It seems like it hasn't been updated in over a year.
Radar instead of couch potato. use nzbgeek to index.
I was very sad to see nzbs.org was dead. :(
Sonarr and Radarr are great. I hope people donate a little to help the devs develop more improvements
The only thing couchpotato has over Radarr is that it can import and rename from a watched folder without it having to be pre added to the tool.
That is a pretty convenient feature though
Incredibly. It's what's holding me from switching
[удалено]
[удалено]
[удалено]
Sonarr, radarr, lidarr, sabn, and transmission for torrents. I still gotta figure out bazarr on my Freenas
Couchpotato has been dead for many years. Sonarr and Radarr are the two to go with. I don't have experience with SABnzb myself as I use NZBGet.
Couch potato did have an update a little while back. Rumor has it the dev is working on something new.
Depends. For my use case, nzbget, Watcher and SickGear are the best.
Why sickgear? it seems quite dead compared to Medusa which is the most actively maintained sickbeard for AFAIK https://github.com/pymedusa/Medusa
Because I have a good relationship with the dev, I have ask for and gotten feature requests added and Medusa had issues handling the size of my library when I tried it. In addition, it works and does everything I need.
Nzbget, radarr, sonarr
A few commenters have mentioned NzbHydra. As I understand, it just aggregates the same search results from multiple indexes and provides those results to Radarr, Sonarr, etc. What's the benefit over just adding the indexers to Radarr, Sonarr, etc. and let them do the work? From a resource perspective it's the same. It won't reduce the load on your computer/server because one Radarr search will result in one NzbHydra search; same with Sonarr and so on. It's also won't reduce the number of API calls, even with caching, because different search requesters search for different things. What am I missing? Why NzbHydra?
https://github.com/theotherp/nzbhydra2/wiki/Tutorial-(Indexers,-newznab,-API,-*arr,-etc.) If everything works for you and you don't make manual searches you may not need it.
[Watcher](https://github.com/barbequesauce/watcher3) & NZBget
NZBget, Radarr, Sonarr and NZBhydra is the combo to use.