Mounting a folder lidarr-deemix-certs

[Druidblack]

I wanted to clarify. At the end of the program description, there is a footnote that the folders should be monitored.

Note

The folder /lidarr-deemix-certs must be mounted to /usr/local/share/ca-certificates within the Lidarr container.

Also /var/run/docker.sock/ is needed, so lidarr-deemix can connect to lidarr and execute update-ca-certificates. If this is an issue, you have to manually execute that command, each time you restart the Lidarr container.

Previously, there were lines in the docker compose example that they needed to be mounted. This is not in the example right now. I wanted to clarify. Do I need to do this now or not?

[ad-on-is]

Ooh... need to update the docs, but it's not necessary to do that anymore.

Just disable Certificate Validation in Lidarr, so you don't need to deal with certs.

[Druidblack]

Then I have a question. We haven't noticed any oddities in the program lately. I have a priority for deezer in the settings. Since recently . After the next artist update, the albums added from deezer were deleted. If you set it to use the deezer api priority, then albums are downloaded from deezer. I don't understand what this is related to

[Druidblack]

==> /root/nohup_deemix.txt <==
==> /root/nohup_server.txt <==
> lidarr-deemix@ start /app
> tsc && ts-node --project tsconfig.tsnode.json dist/index
Lidarr++Deemix running at http://0.0.0.0:7171
200 GET /api/v0.4/artist/ce6fd239-96ff-4a6b-a84f-91ea68c0947c
200 GET /api/v0.4/album/16921068-edb7-4835-8b33-dbca0b5eb275
200 GET /api/v0.4/album/1561937f-bdb7-4ec8-9eb9-8d6c009c2d8b
200 GET /api/v0.4/album/ea66ab7a-9ae4-41c4-be41-101bc695af3e
200 GET /api/v0.4/album/b2e83b34-6375-4706-b6ae-7ba4c794609b
200 GET /api/v0.4/album/8f4bda45-bb71-4be4-9ac0-31bfe6e97769
200 GET /api/v0.4/album/38c77680-0e29-4808-bbe0-bb063a79852b
200 GET /api/v0.4/album/84a9a90d-af50-4ef0-84b7-988f3b29cc4d
200 GET /api/v0.4/artist/aaaaaaaa-aaaa-aaaa-aaaa-aaaa10412096
200 GET /api/v0.4/album/bbbbbbbb-bbbb-bbbb-bbbb-bbb526204432
200 GET /api/v0.4/artist/ce6fd239-96ff-4a6b-a84f-91ea68c0947c
200 GET /api/v0.4/artist/ce6fd239-96ff-4a6b-a84f-91ea68c0947c
200 GET /api/v0.4/album/16921068-edb7-4835-8b33-dbca0b5eb275
200 GET /api/v0.4/album/bbbbbbbb-bbbb-bbbb-bbbb-bbb526205992
200 GET /api/v0.4/album/1561937f-bdb7-4ec8-9eb9-8d6c009c2d8b
200 GET /api/v0.4/album/bbbbbbbb-bbbb-bbbb-bbbb-bbb526202502
200 GET /api/v0.4/album/ea66ab7a-9ae4-41c4-be41-101bc695af3e
200 GET /api/v0.4/album/bbbbbbbb-bbbb-bbbb-bbbb-bbb526201332
200 GET /api/v0.4/album/bbbbbbbb-bbbb-bbbb-bbbb-bbb523248382
200 GET /api/v0.4/album/b2e83b34-6375-4706-b6ae-7ba4c794609b
200 GET /api/v0.4/album/bbbbbbbb-bbbb-bbbb-bbbb-bbb526200202
200 GET /api/v0.4/album/bbbbbbbb-bbbb-bbbb-bbbb-bbb526200192
200 GET /api/v0.4/album/8f4bda45-bb71-4be4-9ac0-31bfe6e97769
200 GET /api/v0.4/album/bbbbbbbb-bbbb-bbbb-bbbb-bbb526200182
200 GET /api/v0.4/album/38c77680-0e29-4808-bbe0-bb063a79852b
200 GET /api/v0.4/album/84a9a90d-af50-4ef0-84b7-988f3b29cc4d
200 GET /api/v0.4/search?type=all&query=%D0%B2%D0%B8%D0%BA%D0%BE%D0%BD%D1%82
200 GET /api/v0.4/artist/ce6fd239-96ff-4a6b-a84f-91ea68c0947c
200 GET /api/v0.4/artist/ce6fd239-96ff-4a6b-a84f-91ea68c0947c
200 GET /api/v0.4/album/16921068-edb7-4835-8b33-dbca0b5eb275
200 GET /api/v0.4/album/1561937f-bdb7-4ec8-9eb9-8d6c009c2d8b
200 GET /api/v0.4/album/ea66ab7a-9ae4-41c4-be41-101bc695af3e
200 GET /api/v0.4/album/b2e83b34-6375-4706-b6ae-7ba4c794609b
200 GET /api/v0.4/album/8f4bda45-bb71-4be4-9ac0-31bfe6e97769
200 GET /api/v0.4/album/38c77680-0e29-4808-bbe0-bb063a79852b
200 GET /api/v0.4/album/84a9a90d-af50-4ef0-84b7-988f3b29cc4d

This is the log that the program outputs

[ad-on-is]

PRIO_DEEMIX just means, if there's an album on MusicBrainz and Deezer with the same name, it should take all the info (tracks, image, etc.) from Deezer and not that of MB. I've seen some albums on MB with 15 tracks, but Deezer has only 14 for example.

OVERRIDE_MB means, to ignore MusicBrainz completely. So no info is ever pulled from MB itself.

[Druidblack]

OVERRIDE_MB = false OVERRIDE_MB = true Previously, when OVERRIDE_MB was turned off, albums were added from both MB and deezer. Currently, albums are not added when updating information.

[Druidblack]

I haven't changed anything since the last setup. I just updated the artist one day and saw that some of the albums were deleted. And now it doesn't work as it used to. I've tried changing lidarr versions. It didn't help. What could be the reason is not clear to me. For all the time, only the ARL has changed, which I changed to the correct one.

[ad-on-is]

Could you expand the album section and see which of the 2 albums are missing?

Does this only happen if you turn override_mb on/off or did it stop working at all, regardless.

[Druidblack]

OVERRIDE_MB = false OVERRIDE_MB = true

https://musicbrainz.org/artist/ce6fd239-96ff-4a6b-a84f-91ea68c0947c

Added a new example.

The connection of all albums from MB and deezer stopped working under any settings. The suspicion is that something broke in MB, because when the proxy server is turned off, the data from MB is still not added, although they were previously added to this filler (I'm talking about the one in the new examples).

[Druidblack]

I am giving those examples of performers who used to work exactly correctly.

https://musicbrainz.org/artist/516ab2c8-0b66-4e31-8cde-062046592fb3

[Druidblack]

[ad-on-is]

because when the proxy server is turned off, the data from MB is still not added

I'd suspect it has something to do with MB then, or a mismatch of the Lidarr assignment process with data from MB and existing albums.

How are other artists?

[Druidblack]

I haven't added artists to my lidarr yet, but of all the test requests, only these two artists (whom I cited above) had problems adding albums. By the way, when these artists are initially added, all the albums (from MD and Deezer) appear, but then they disappear.

Strange behavior. If lidarr can't get data from MB, why doesn't it add data from Deezer? I have a setting to give priority to albums from Deezer.

[ad-on-is]

oh wait... you're mistaking something here.

the albums that show up are indeed found, but Lidarr has an issue assigning the already downloaded stuff.

So it's not an issue with MB/Deezer, it's an issue with matching the downloaded files to the appropriate folder.

[Druidblack]

Are you talking about files that contain information about albums? (because I don't have the music yet) Strange. And what could have changed in Lidarr's work to start such behavior? Apart from a few Lidarr updates, there were no other changes. Yes, and I tried a new (clean) Lidarr installation. the behavior remains the same.

It will work if Lidarr does not find (does not compare information about albums) then he won't be able to download music.

P.S. Maybe you have a telegram for faster communication with you?

[ad-on-is]

Sorry, I have no clue whats going on, seems like a display issue in Lidarr.

the fact that you have more albums/singles etc with this library shows it's working correctly.

I'm closing this one since it's unrelated.