mirror of
https://github.com/RandomNinjaAtk/arr-scripts.git
synced 2026-03-02 22:57:35 -05:00
[FEATURE] - Lidarr/Readarr - Soularr/slskd support #176
Labels
No labels
Needs Triage
Not Reproducible
Upstream Issue
User Error
bug
documentation
enhancement
good first issue
help wanted
invalid
lidarr
lidarr
question
radarr
readarr
sabnzbd
sonarr
synology (host)
unraid (host)
waiting for logs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/arr-scripts#176
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @OCT0PUSCRIME on GitHub (Oct 24, 2024).
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.
@SickProdigy commented on GitHub (Oct 28, 2024):
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.
@OCT0PUSCRIME commented on GitHub (Oct 28, 2024):
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.
@RandomNinjaAtk commented on GitHub (Oct 29, 2024):
Interesting, first I've heard of this project... No promises might look into it when I have the chance.
@hockeygoalie35 commented on GitHub (Jan 3, 2025):
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.
@duckmaster175 commented on GitHub (Jan 5, 2025):
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.
@hockeygoalie35 commented on GitHub (Feb 8, 2025):
I've add a pull request to Soularr #https://github.com/mrusse/soularr/pull/86, to allow the functions be used independently. It'd be nice to be able to write a script that can be called by the Audio service, and then be tagged by beets and Lidarr/Plex notified.
@hockeygoalie35 commented on GitHub (Feb 24, 2025):
Just a small update, working on a proof of concept that hooks Audio script to Slskd. I'm using a lot of the same logic as Soularr, but my script is tailor-made to accept Audioscript's input.
Script output:
Slskd Search:
@OCT0PUSCRIME commented on GitHub (Feb 24, 2025):
Awesome thanks for the update. Happy to test!
@Deekerman commented on GitHub (Apr 2, 2025):
I assume the best idea would be to have this built into lidarr ext, but another option could be have soularr drop the downloaded files into an import file on lidarr and then have it go through the same tagging process and lyric look up.
there is a community script now for slsk and soularr. I dont know which would be easier but if there was an import folder people could drop in music acquired from anywhere.
@OCT0PUSCRIME commented on GitHub (Apr 2, 2025):
The lidarr plugins branch now has a slskd plugin that I am planning on testing.
Edit:
Testing now. The plugin is working great. Not sure how to tell if it does the beets processing and stuff, but it searched and downloaded just fine.
I would not recommend doing this right now until plugins are moved to stable or the plugin branch has an alpine 3.21 base. Right now it has a 3.20 base which causes the arr-scripts to fail unless you manually edit the container to add the 3.21 alpine package distro.