Than this is the wrong topic I think
That answers my question, thanks. I would not have assumed that adding a MB URL gets me where I want though, maybe this should be explained somewhere a bit more.
Small request:
Can you move the link for ISRC submission
to the left:
This would be less disruptive when using an extension such as Linkclump to open multiple links. Otherwise, when the external ID link(s) are present, it will overlap with the icon links:
Regarding release group type detection. The Spotify API doesn’t distinguish EP and single. Would it be viable to scrape the Spotify website?
<title>Everything is mental - EP by Nous Klear | Spotify</title>
Or guess the type from other fields like the description on Beatport:
https://www.beatport.com/release/everything-is-mental/4649070
3 Likes
In order for Harmony to provide the link to a MB release it needs to look this up in some way. It does not need to be the MB release URL necessarily. It could also be a Spotify link with MB provider enabled. If Harmony would find a matching release by barcode on MB then it would also show the actions link.
1 Like
Of course it needs to look it up, it just didn’t match the UI flow I was used to from atisket I guess. With atisket, you would always get a link to the ISRC import tool (not MagicISRC though) on the page where you could also start the MB import process, and I often used this when updating releases someone else had already created.
From the way it is described at the link you gave, it doesn’t sound like artist intent, just a “dumb” track count/length threshold.
Might not be the right place, or it might be - could we have it so we can seed ISRC’s from the first page please?
Atisket used to have this and its really useful for filling in blanks left by prior editors!
3 Likes
I think that’s exactly what I asked for above 
oops, I didn’t read 
i just went straight to the bottom
so yeah, what @elomatreb said 
I’d love to be able to see composer credits in the harmony UI somewhere. I spend quite a bit of time awkwardly clicking through songs in the spotify UI to get those, would be super helpful to have those just presented in a nice way. (Not suggesting automatically creating works since that seems a stretch currently, although it’s nice to dream of.)
3 Likes
I don’t think Spotify exposes any composer information in its API.
Would love to see something like this as well. In the last few days i’ve been thinking about doing it with a userscript somehow but i’m not quite there yet, skill wise
Exposing songwriters and producers has been in their “to do” list for a long time, apparently - Songwriter & producer credits in API · Issue #779 · spotify/web-api · GitHub
1 Like
I just ran across first class songwriter credits on the song El CLúB from the new Bad Bunny album, linking to MAG is a songwriter.
Have a doubt about recording relationships. Right now spotify links (and similar) point to the release, and thus are added as relationships to it
Would it be possible to add the actual links to every track also at the recording level? (since we are importing digital releases from these streaming services, there is no ambiguity about them matching the recording or being other versions)
One of the main problems ListenBrainz is facing when exporting playlists to Spotify is the linking (it misses a lot), but if there were links already populated at MB it would be much easier.
1 Like
- that would give more reasons to make BrainzPlayer use recorsing urls
I’ve already created tickets for this, both on Harmony and MBS
I agree that this would be an extremely handy feature to have, and adding it to a major importer like Harmony would be a way to get through the chicken-and-egg problem we’ve got currently
6 Likes
Is the tidal api malfunctioning today?
No matter what I enter as URL, it always says the API returned no results.
For ex:
Not working for me either. That is weird. I just checked at TIDAL and it seems to be working there. Gives info:
Bob Dylan - Highway 61 Revisited
Type: ALBUM
Total Tracks: 9
Copyright: Originally Released 1965 Sony Music Entertainment Inc.
Barcode (UPC): 827969239926
Hmm, it looks like Tidal has silently changed something in their public API 
All requests to https://openapi.tidal.com which I’ve tried return empty responses with 404 error status (I only see a x-cache: Error from cloudfront response header), regardless of whether I am using an API token or not.
Having a look at the official documentation, it seems that they’ve introduced a new “v2 - beta” API, must have been in July 2024, only shortly after the Harmony provider has been implemented…
So far I’ve found no trace of the v1 documentation, no deprecation announcement or an entry in the changelog!?
I will try to find out if I can get the v2 API to work…
P.S. Xythium’s tool still works as that is using a different API (listen.tidal.com, which is intended for internal use).
9 Likes
Unfortunately the Tidal v2 API changes so many things that it looks easier to me to write a new provider rather than carefully comparing and implementing all the differences between v1 and v2…
Especially as we would still need the current implementation which handles the JSON data of the cached v1 API responses in order not to break old permalinks 
Having two provider implementations for the same service also opens a new can of worms since Harmony currently has no mechanism to register multiple handlers for the same release URL format etc.
There are some other parts of Harmony I’ve been slowly working on in my spare time, so I’m going to be honest: Right now I don’t feel motivated to tackle the Tidal provider and the silent shutdown of the v1 API doesn’t increase my will to work with the v2 API. Had the API changes been communicated better or announced a month earlier (in June 2024), we wouldn’t have this problem now…
So I don’t expect this to be fixed fast unless someone volunteers to help.
Until that happens, we can only hope that the x-cache: Error from cloudfront response header is an indicator of the v1 API having been turned off by accident.
I don’t see any reports in Tidal’s discussion section on GitHub either, but maybe it is worth asking over there? Preferably someone else, Harmony’s usage of the API may not 100% confirm to their terms of service.
P.S. Why do all streaming platform APIs have to suck? First iTunes and Deezer decided to return unwanted releases for a different region, then Spotify did the same with tracks (and dropped many endpoints which were useful to others but fortunately didn’t affect us) and now the Tidal disaster 
9 Likes