Hi all! I was importing my listening onto ListenBrainz, and it’s said some of my listens can’t be imported - roughly 70000. However, it doesn’t seem to say why. I imagine at least some of it may simply be down to music simply not being on MusicBrainz (which I can try my hardest to add!) but I didn’t know if it’s possible to get reasonings for why each one failed?
1 Like
Looks like roughly 70,000, not 7000.
I don’t think them being missing from MB would be the reason. I have plenty of Spotify listens that aren’t linked to a MB recording.
1 Like
Missed a zero and realised after I closed the tab earlier :’)
What would the reason be? Worth trying again, or nay?
2 Likes
Have you tried to use ListenBrainz - Unmapped Listens with Spotify Links
1 Like
I’m not sure; I tried again as well, and got the same error with the same number of listens imported. So I don’t think it’s a server timeout or something like that, maybe Spotify recently changed the format of their data export? Would be cool to get a sample JSON of what ListenBrainz expects during an import.
1 Like
Hello!
In theory all the rejected listens are skips (less than 30s listening, for one of many reasons) or incognito listens.
I do think we could word this in a better way, and also that we should have a standalone tool that anyone can run on their own machine to get a breakdown of the skipped listens.
I’ve created a ticket to track this:
5 Likes
It would be good to show the number of skips and incognito listens after the import ran.
2 Likes
I am working on adding that, it will certainly be a lot clearer
1 Like
Without your reply earlier in this thread I would not have guessed that “skipped” in this context meant less than 30s listen time, this should probably be explained in the message.
4 Likes
I think the problem is that “skipped” is ambiguous here, “skipped playback” or a similar wording (as opposed to “skipped import”) would be an improvement already.
4 Likes
Thanks for confirming, I wasn’t convinced by that choice.
I originally had “1 skipped (< 30s)” which I thought could be confusing too, but I was trying to avoid the lengthy “1 skipped (less than 30 seconds)” or “(under 30 seconds)”, but I supposed that will have to do.
2 Likes
OK, what is out now in production is better, but in retrospect I am still not very happy with it:
In particular the doubling up of “some listens were rejected” (which was here previously) followed by “Discarded” (which might be better wording, but does not match the previous line).
It might be as simple as removing the “some listens…” on the first line, but I also think the bold on the less important note is a clear miss.
So perhaps one of these options?
I also realized the count of rejected listens did not add up to the total, and the last missing rejects are invalid metadata, so adding that in would also make sense (also shortening phrasing so it fits nicely):
I thought I would do well to come here for more feedback. So please, have at it!
Maybe “skipped by listener” would be clearer? To make it clear that it’s not LB that is skipping stuff for an arbitrary reason.