3/20/2023 0 Comments Better than musicbrainz picardI bet they do it that way too, but I think you're throwing in the towel way too early here. > Spotify probably just makes an informed stab at "most popular" - which is a good heuristic and will work most of the time, but is hard to calculate when you don't have Spotify's stats. I totally realize "canonical" is a bad word choice on my part – but it's really how people think of these things! OK, so we might not need to nail down a "canonical" version when we live in a world with search ranking scores. So, do you think the "Smells Like Teen Spirit" recording by Francis Drake is the BEST first result, as MusicBrainz says it is? Is a live bootleg recording the BEST second result? In any locale? MusicBrainz is NOT primarily a search engine, but all that data has very little value if people (and other software) can't actually find it! This absolutely harms adoption. Yup! You are describing the problem literally any search engine faces. But that's subjective and likely to be significantly different for some non-trivial percentage of users, especially in different territories. > Most people's idea of "canonical" is really "The version I want to hear without having to specify other details". You've described the issue pretty well, and I understand (and agree with!) all of that – like I said, I've devoted a LOT of time to solving this. Spotify is absolutely amazing at figuring out what song in its entire catalog should be the top result even when I've only typed a few characters.) (FWIW, it's totally possible to build these heuristics on top of MusicBrainz today, but having better built-in support for determining this stuff would be nice. Consider a world where it's possible to stream every recording from every release in the MusicBrainz database: it should be easier to make "Alexa, play Dark Side of the Moon" work without it needing to ask whether I mean the 1994 Netherlands CD release. Answering simple questions about music is currently quite difficult to newcomers on account of the overwhelming amount of data. This is an area I've dedicated a lot of time to when integrating MusicBrainz with my project, and it strikes me as something that MetaBrainz could spend time on to make the platform more accessible. In my opinion this should be considered a bug. The second result is from an obscure live bootleg album. Heck, the first result isn't even a Nirvana recording. But MusicBrainz has no notion of popularity, common sense, or the real-world context of any of its entities, so the recording from Nevermind isn't even on the first page of results. Any human with cursory knowledge of pop music would point you at the Nirvana single from the 1991 release of Nevermind (in this particular case, it's likely even true in every locale). I find that the rankings from the search API are not nearly good enough for this.Ĭonsider a recording search for "smells like teen spirit". is the likely intended or "canonical" entity. For other software integration use cases, where there is any ambiguity involved whatsoever, a huge portion of code needs to be dedicated to deciding which recording/release/etc. It absolutely excels at the use case of tagging audio files (as a lot of people here are noting), and as an encyclopedic reference (its purpose). The amount of data is amazing – but I find that it's both a blessing and a curse.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |