-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] - Lidarr/Readarr - Soularr/slskd support #320
Comments
I run slsk and just seen it too. Would be nice to just add another option and few config settings than downloading another separate instance to run a script in. |
Agreed. If possible it would be cool. If not I still would like some input on if it might not play well with the arr-scripts. |
Interesting, first I've heard of this project... No promises might look into it when I have the chance. |
I'm taking a look into this. The soularr project is great, but it doesn't have any of the beets tagging/ path naming / audio processing. Also ARL tokens are sort of going the way of the dodo, as Deezer is cracking down on ARLs. |
I've been using both. The only issue I've seen is one will try to download an album that the other one has already gotten. Otherwise, Soularr has been a great supplement to what Arr-script can't find. |
Is your feature request related to a problem? Please describe.
Finding niche tracks
Describe the solution you'd like
Looking for slskd integration to use soulseek to import niche tracks that can't be found with trackers or arr-scripts
Describe alternatives you've considered
Soularr - see below
Additional context
Apologies if this is the wrong forum. I thought you used to have a discord, but I can't find it.
There is a new project Soularr (and it's fork with readarr support) that I am interested in trying out. I currently use slskd to manually download niche tracks that my trackers and the arr-scripts can't find.
Do you see any conflicts with deploying this alongside the arr-scripts?
I marked this as a feature request in the event that you might be interested in implementing a similar solution.
The text was updated successfully, but these errors were encountered: