Playlist Creation Is A Pain

ListenBrainz
#1

So fellow MBrainz’er @UltimateRiff showed me that I can make playlists on LB, which is a cool feature I could work on.

Have an idea for a playlist (doesn’t really matter to this problem) and create it, then to add tracks.

First track is Purple Rain by Prince and the Revolution; pretty popular song, most people probably know it.

So I type in Purple Rain, the query results are:

image
image782×442 22.4 KB

OK not great, it’s managed to pull a load of covers (probably) instead of the original.

So I type

Purple Rain Prince

image
image788×464 24.6 KB

The first result, although the wrong artist (but lets take this from the laymans point of view of what would they chose) goes to a demo recording:

OK so let’s now say we chose the Prince and The Revolution option:

Nope that’s a different live version, not even the one from the album

So I find the album:

Now I have the correct recording entity:

But I can’t paste it into the query box like I can with every other query box on MB

So…

In Short: how do I add Purple Rain to my playlist.

In Long: is there not some additional logic that could be introduced here, for example weighting recordings which have lots of links against them (such as recording entity 85a752f8-cbad-42e6-8828-bd81318e3c7d) over recordings which don’t?

#2

This isn’t consistent however, for example the next track is Lay Lady Lay by Bob Dylan.

Type it in, first result is:

Perfect!

And yet it’s not like there’s only one Lay Lady Lay to possibly choose from (200+ possibles):

1 Like
#3

Hiya!

Thanks for your feedback – I totally see your point. The backend that supports this track search is actually an internal service we’ve exposed, mostly as a “lets use it, it should work ok. then we’ll see what users say” kind of moment. So, very likely not ideal from a user or from a hosting perspective.

I’ve got a number of ideas for how to improve this:

  1. Use a different data set and search technology that is more suited for user interaction. (the data index we have now is geared toward the automated MBID mapping process). A user centric index would our new canonical recordings index with results being weighted towards album tracks, rather than all the other guff that you find getting in your way.
  2. Allow a user to past a recording MBID into the search field and add that specific track to the playlist. This should work as a stop-gap measure until we can put #1 in place.

A good start would be for you to open a ticket on tickets.metabrainz.org and dumping the essence of this post into a ticket for ListenBrainz so can can track this issue and plan for an improvement.

Thanks!

5 Likes
#4

I have created a ticket:

I hope this has enough detail, as I think this is the first one I’ve ever raised

4 Likes