[Feature Request] changing the way listens counts

ListenBrainz
1

im new here, so any mistake should be ignored

i dont find any topic related to this, so im writting about it, but there one, let me know, here i go

currently, if i listen diffrent versions of a track, like remixes, features, remastered, slowed, sped up, live, special edition, dance performance, other performances etc.

then they gets counted as diff. tracks, as of there titles & mbids

which is’nt a issue of that kind, but here me out, i think it can be improved by a little tweaks

what if all versions counts could be merged into the main track listen count, and on the stats list, if i click the track, then it shows me counts of all versions i listened

example for better understanding, if i didnt able to explain it

i listened,

  • supernatural by ariana grande 50 times
  • supernatural (live version) by ariana grande 30 times
  • supernatural (feat. the weeknd) by ariana grande, the weeknd 12 times

on the stats page it should show

  • supernatural by ariana grande 92(50+30+12) times

[note: not the “(50+30+12)” part on listen count feild, it just for reference, but if you have additional opinion about adding that, reply below]

and when i click on it, it’ll then show me another chart or just simple text telling me which version i listened how many times

maybe many of you wondering, “is’nt that possible if all versions added in a release, then the it’ll do exactly what this stupid asking for”

well, i thought about that, but i dont think it would be that much ideal, and not always all versions are listed in release for all tracks, even if they do, i have to map my listens to that release instead of the main album release, which gonna reduce my count to the main album, and many of us dont want it i guess, or can i add multiple release for single listen, i dont think so, i never thought of it yet now, but that will not gonna be so ideal i think

feel free to raise questions & counters, im here to learn & distrubute, not fight, so be polite

and sorry for a long article type request, im actually a daily blogger

have a better life…

2 Likes
2

I had the same idea before and it can be answered with a simple sentence: Work stats.
Different versions should have the same work, and thus have the total amount of listens

… And I made a tool to calculate them. Just download Alistral and do:

  • alistral stats work for the stats

  • alistral stats work --w-recursive if you want to have the parent works of the works be counted as well (Useful to know the total for game osts)

  • alistral stats work --w-recursive --sort-by listen-duration to use the total time you listened to a track instead of the listen count

Just be wary that it can take a long time to get the data… Spin it up in the background and check back later

7 Likes
3

I love this idea, but I have different suggestion.

I don’t think all the versions of recordings linked to the same work should be counted together for listens. Remixes, for example, are usually substantially different from the original versions, and should be counted separately. the same goes for instrumental/karaoke versions, acapella versions, versions that feature a new verse by other artist. All these are usually linked to the same work.

In my opinion, what should be counted together are edits and dj-mixes of the track. These are essentially the same version of the song, except they’re not the entirety of it, removing the beginning and/or the end. This could be achieved merging that listens of recordings that have the “edit of” and “dj-mix of” relationship

3 Likes
4

thanks for creating such an amazing tool, seems like it will do everthing i asked for, not tried yet, was busy on other stuffs, i’ll let u know how it worked, and i also think this feature is finishing touch

1 Like
5

ya, ur right, but i never mentioned to merge all counts entirely, what i meant is to merge them on main page but add another sub-page by clicking the track stat, which will show which version have how many listens

but heres another idea, since you have a point, wouldnt it be better if they let users decide which versions are same & should be counted along, what do you think, pls let me know?

1 Like
6

TBF, I planned to do that level of precision too (the --w-recursive is part of that system), but I need to redo all the code as it’s actually too messy to continue.

So much to do, so little time…

2 Likes
7

The way to decide which versions are the same would be to check which recordings have the “edit of” and “dj-mix of” relationship in MusicBrainz. I figure it would be an easier way to do this, since these relationship types already exist in MusicBrainz

1 Like
8

If this thread yields a solid feature suggestion, please open a ticket for it, if that hasn’t already happened!

9

TBF, I never actually made any ticket due to previous comments on not being able to calculate all the different stats for every users.

Although could be a good thing for LB local… Whenever it will come out… On demand stats ould be easier due to being the user’s machine, and with Alistral’s experience, I can attest that it takes less than a second to generate any stats (not counting relation fetching). I know it’s written in rust but the underlying algorithms are often O(N) or O(N x M)
The only thing it really needs is how mbids map to eachother (what recording MBID is on what release MBID), but that can probably be done using LB’s MB cache, or even recached on the user’s machine.