[FEATURE] Easier Bulk Downloading

[TheGMan1776]

[FEATURE] Easier Bulk Downloading

[nathom]

Does downloading the artist link work?

[TheGMan1776]

Does downloading the artist link work?

I have 2 installs of StreamRip on 2 different PCs and for some reason they seem to be acting a little different when I use the same commands, signed into the same Tidal account, with the StreamRip config configured the same way.
I mentioned part of it here (#475 (comment))
But in relation to using the artist link. On PC 1 (Which is the PC I said gave the message of the file already existing in my other comment) I try to use the artist link and then it downloads 1 random album from the artist and gives the message saying the file already exist and doesn't download (or redownload) anything else. (Which as mentioned in my other comment might be because its trying to redownload the same thing but finding the file and saying it already exists PC 1 is at least) On PC 2 if I use the artist link it appears to go through and start downloading more then 1 album BUT it has the problem me and "CHJ85" were talking about here "#475 (comment)" where it's downloading multiple versions of the same songs. Sorry if this is confusing to read and for all the back and forth but as typing this it dawned on me that that is probably why just using the artist link doesn't work or has issues

[TheGMan1776]

PC 1 config.txt
PC 2 config.txt

Those are the 2 config files from each PC (Changed to .txt files so I could upload them to GitHub) but like I said they should be the exact same

[nathom]

Try using v2 on the dev branch. It ignores existing files.

[Carter0108]

Another idea for bulk downloading: would it be possible to use the search function to simply write the URL to a file so you could gather a load of artists together and then download all at once? It would be less tedious than gathering the URLs manually.

[nathom]

@Carter0108 Yes I could do that. Can you make a separate enhancement issue for it?

[nathom]

Creating new issue for proxy support. Remaining issues raised seem to be resolved in v2.