Can't find JSON-files when artist folder is different from artist's name about docker-amvd HOT 11 CLOSED

So far so good, files in cache are populated with periods, instead of spaces.

I'll report back in the morning.

from docker-amvd.

Should be fixed with:
0f4d09d
fce4286

Keep in mind, I have not tested...

from docker-amvd.

The original issue seems fixed, at least my perception of it - nothing is downloaded though.

2020-09-09 01:31:53 50 of 314 :: ArtistName :: Processing
2020-09-09 01:31:53 50 of 314 :: ArtistName :: Normalizing MBZDB Release Info (Capitalization)
2020-09-09 01:31:53 50 of 314 :: ArtistName :: IMVDB :: Aritst Link Found, using it's database for videos...
2020-09-09 01:32:10 50 of 314 :: ArtistName :: MBZDB :: 604 recordings found...
2020-09-09 01:32:10 50 of 314 :: ArtistName :: MBZDB :: Checking 604 recordings for videos...
2020-09-09 01:32:10 50 of 314 :: ArtistName :: MBZDB :: 32 video recordings found...
2020-09-09 01:32:10 50 of 314 :: ArtistName :: MBZDB :: Checking 32 video recordings for links...
2020-09-09 01:32:11 50 of 314 :: ArtistName :: MBZDB :: 0 video recordings with links found!
2020-09-09 01:32:11 50 of 314 :: ArtistName :: Skipping...
find: ‘’: No such file or directory
2020-09-09 01:32:11 50 of 314 :: ArtistName :: 0 Videos Downloaded!
2020-09-09 01:32:11 50 of 314 :: ArtistName :: MARKING ARTIST AS COMPLETE

That log-output is from a an artist without spaces or special characters, and with a IMVDb-link present in musicbrainz.

It seems, from the downloading-section of the logs, that I am either hitting a missing imvdb-link, or this error.

from docker-amvd.

If none of your artist are working, you'll need to provide more specific info to see if the issue can be replicated. If it can be replicated then I can look into finding the problem.

Example, few artist names, any specific lidarr configuration (folder naming) and etc

from docker-amvd.

So quick update, I just did a fresh install of both apps (lidarr/amvd) and only configured one artist and its working in my testing (with and without folders enabled for youtube)...

For reference, this is the script version I'm on: SCRIPT VERSION 1.1.21

Make sure you have the latest code, and you may want to setup a test setup to attempt to replicate the issue. If it cannot be replicated, it cannot be fixed...

from docker-amvd.

I am on latest, even watched the build-process on docker hub.

I'll setup some testing and report back.

from docker-amvd.

Really weird, there's definitely something on my end - but I can't see what.

On a new config, with the same setup in Media Management (i.e. naming convention) as my original - this works just fine - but on my "proper" setup, it still fails.

I'll see if I can come up with something, but at least your findings are the same as mine.

from docker-amvd.

I'm going to close this, feel free to re-open if you can find a way to re-produce it.... But the few issues that were found were resolved with the changes

from docker-amvd.

Yeah, fair enough.

For the record, I have Lidarr running on a remote server, but when I spin-up the container from home, but connected to the same Lidarr, with the same options - it works.

If I do the same from the remote server, it doesn't work.

Was going to write up something with regards to that, otherwise I'm just going to hack together an sshfs-mount or something and call it a day.

from docker-amvd.

I don't think it should matter where lidarr is located, since it's really only using it's api data. Unless it's having issues communicating lidarr/musicbrainz...

Also, make sure your using cookies.txt, that could be an issue....

from docker-amvd.

No, other way around - it is where amvd is running. Lidarr is staying on the same server.

But thanks for your help, and this software, I'll post back if there's anything usefull to add.
Otherwise consider it closed and resolved. :-)

(and I'll check up on cookies.txt, already had it in mind.)

from docker-amvd.