Play count not updating as expected

Hi All,

Thanks for the additional information. I have been attempting to reproduce this issue on my end but have yet to succeed. Are there any details that may help us reproduce this behavior? Which screen in Roon do you notice the play count increase on?

I tried to pause/unpause both TIDAL and Qobuz tracks that were in and out of my library without success in reproducing.

If you temporarily disable/log out of Last.FM do you still notice the issue occurring?

:open_mouth:
… in which Roon’s screen does play count show?
:roll_eyes:

Along the lines of view in my tracks, album details, playlist plays, etc. Where do you notice this increase?



in Album view: that’s what I use!

My play count shows elevated plays on the tracks page.

Hi everyone,

The crucial missing component here is whether or not you see duplicate plays reflected in the Play History.

If you pause a track and notice a duplication in the Track Count from any Track, Album, or Playlist page, do you also see that track listed twice in your play history when you click on the Queue and scroll up?

Sometimes these tracks may be nested under “X skipped items,” so be sure to unfold that menu.

I understand some of you are quite frustrated and have waited some time for a resolution here. We’re working with QA to reproduce, and we’re investigating the scrobbling in ARC as a separate, but potentially related issue. The tech support team will provide an update as soon as we have one, but any clarify you can provide around the above question will be immensely helpful in supporting our efforts.

1 Like

Hi Connor,

Looks like I prematurely reported this being resolved in my other thread on this issue here. The good news is, I think I’ve been able to narrow down a specific sequence of event that causes it reliably.

In this screenshot, you’ll notice two tracks that have a play count of 2. I didn’t listen to these tracks twice. However, I did pause them at somewhere around 50% to 70% progress for an extended period of time. In the case of “Nothing at All”, I paused playback for roughly 2-3 hours. When I resumed listening after that 2-3 hour period I noticed two things. First, the playback progress was right where I left it. Also, the play counter had incremented to 1 even though it was at 0 when I paused playback. After resuming playback and completing the track, the play count incremented to 2. Again, despite the pause I only played the track from start to finish one time.

I found something else very interesting when I went to check my play history. I wanted to check if there were duplicate plays listed there per your request, @connor. What I found is that the two tracks with duplicate play counts were only listed once BUT they were showing completion percentages equal only to the track duration after the pause. Despite the pause, these tracks were played through to 100%. See screenshot below.

One other thing that I’ll note, although I’m not sure if it is relevant, is that my Mac (where I did this testing) went to sleep during the extended playback pauses. My Roon core is on an Ubuntu Server elsewhere on the network. Again, I don’t know if this is an important detail but there would have been an interruption between the Roon app on my Mac and the Roon core during this time. Anyway, hope this helps the team make some progress! Please keep us posted.

Rob

1 Like

Here’s another example. This afternoon I was listening w/ my Astell & Kern SP3000 DAP via Roon Ready and paused playback about 15% into the first track of the Earthling album by Eddie Vedder. I powered off the DAP and turned it back on about 4 hours later to continue listening. Sure enough, the track that I was only 15% into showed a play count of 1 and upon completion (after unpausing) it incremented to 2. Just as before, the track’s completion percentage displayed in play history is equal to the remaining portion after unpausing. This behavior seems to be pretty consistent from what I can tell.

1 Like

Hey guys, we’ve discussed this and have some ideas about how to address it, but the fix is not simple. We do plan to fix this.

3 Likes

Thanks, @brian. Does this mean you’ve found the cause and can reproduce the issue?

1 Like

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.

My original thread has been closed so I am posting this again.

If I pause and resume a song it often counts as 2+ plays and also double scrobbling in Last.fm. This happens in Roon and Roon Arc.

Even after multiple updates, this issue has NOT been fixed.

2 Likes

This was posted on December 22:

Personally, I could understand that it’s not entirely easy to solve. E.g., if I pause and continue immediately, that should count as one play. But if I pause it in a different zone, leave it for two days, and then continue, I might consider this two plays. The track played once all through, but I cared to listed to it twice, in a way. Others may see it differently.

From my POV. If I start a song, pause it midway. Go to the moon and return. If I then hit play and hear the song end. I’ve played it through 1x. I start and stop it 15 times to explain lyrics, still made it through 1 time.

There is a tunable option to set how much of a song needs to play to count as having played. Somewhere this is being tracked. I am unsure how it is being counted. I tried to screenshot it but can no longer find te setting.

Another whatever they do will end up irritating X% of userbase I think.

Yeah, and to me, I played it two times. While …

That’s once for me, too.

I believe that this is precisely why it’s not entirely easy, and like you say inevitable that it will not fit everyone. I’m ok with that :slight_smile:

I never saw that. However, it would be nice if the play history was more editable, then everyone could solve it. Currently, it’s only possible to delete plays, which is fair enough. However, the ability to add virtual plays would help with the play count in Roon for different needs, but even beyond - if I play the vinyl, clicking an “add play to history” would be cool

1 Like

I’ve reopened it and merged topics.

Any updates on the fix? cc @Carl

@connor @brian ^^^

I’ve recently noticed that this seems to happen when transferring the queue between zones as well. While I don’t mind so much seeing a track split up in the playback history according to events such as lengthy pauses or zone transfers, the fact that these events are represented as unique play counts is very frustrating.

I’m not big on manually favoriting or ranking/rating media, be it movies, tv shows or music. Because of this, I really appreciate tools and software that track and present my watching/listening behavior. I can use this data to remind me of things that I really enjoyed, kept going back to and when (over time). This is one of the things that drew me to Roon. The ability to see my listening habits and trends both in the Roon UI and in Last.FM is very useful to me.

As a lifetime Roon subscriber, it’s frustrating to me that this core feature/functionality (track play counter) flaw has gone this long without a fix, or even a solid timeline expectation. Can we please get some sort of commitment on this fix? Thank you!