Skip to content
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

MusicBrainz album ID not returned in getAlbumInfo2 #444

Closed
phw opened this issue Dec 29, 2023 · 1 comment
Closed

MusicBrainz album ID not returned in getAlbumInfo2 #444

phw opened this issue Dec 29, 2023 · 1 comment

Comments

@phw
Copy link
Contributor

phw commented Dec 29, 2023

gonic version: 0.16.2

git commit: g2e2a6c3

The getAlbumInfo2 endpoint does not return the MusicBrainz album ID, even if known. E.g. this is the response for an album from my collection with ID al-350:

<subsonic-response status="ok" version="1.15.0" xmlns="http://subsonic.org/restapi" type="gonic" serverVersion="0.16.2" openSubsonic="true">
  <albumInfo>
    <notes></notes>
    <musicBrainzId></musicBrainzId>
    <lastFmUrl></lastFmUrl>
  </albumInfo>
</subsonic-response>

Note the empty musicBrainzId. Looking at the database the album_infos for this entry is the same:

id created_at updated_at notes music_brainz_id last_fm_url
350 2023-12-28 13:24:40.554462075+01:00 2023-12-28 13:24:40.554590233+01:00      

But the album table does contain the necessary data:

id tag_brainz_id
350 9cf39057-52d2-4271-adaf-49cc339a7aaf

I'm not sure why there are redundant fields for the MusicBrainz release ID. But it is either not properly transferred to the album_infos table or the getAlbumInfo2 endpoint uses the wrong data field.

@phw
Copy link
Contributor Author

phw commented Dec 29, 2023

Thanks for the fix. Now I also understand this better and see how the Info endpoints are primarily populated by last.fm API data.

But the new behavior makes a lot of sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant