Changing zones causes the play count of the currently playing track to increment if conditions are met to mark the track as played. I've seen it happen where changing zones again causes another increment, but I can't reproduce that. Regardless, when the track completes play count is incremented yet again. This results in two or more play counts for what was in fact a single play.
This is happening in Roon for PC. Sever is Roon for Mac.
Describe your network setup
Roon server on MacOS. Controlling from Roon on PC.
Fellow user here. Support will be back on Tuesday.
I hear what your saying but, I think that you’ll find that this is expected behavior, from how I understand Roon works. Again, I could be misunderstanding things.
The Queue is different/unique for each audio device. There is not one single multi-zone queue. So when you “transfer” to a new zone, you are not just shifting the audio output playback between zones; you are in essence cloning the queue at that time point from the original audio device to the new audio zone and then starting playback on the new zone. The queue still exists on the original audio device, at the point it was stopped. If the transfer occurs after a point Roon considers that the track has been played, then it will increment it once for the original queue, and then when you finish playback on the new queue, it will increment it again. Again because the queues are actually different.
Thanks for the feedback here. Since this is not a current feature of Roon as described by @Rugby, I would recommend also posting your suggestion in the Feature Suggestions section of the site or vote for the existing one.
Our product team and developers keep a close eye on that category, so that’s definitely the best place to propose a change like this and get feedback from the Community.
What Rugby describes sounds like it could explain what’s going on behind the scene. But as a user who’s not versed or particularly interested in implementation details the behavior just seems like something is going wrong. I mean, from my perspective, I play a track once and according to the display I have played it twice. It just seems incorrect to me.
What would help, and would be a candidate for the Feature Suggestion section as Vadim suggested, is to have the ability to set what Roon counts as “played”. In this case, you would want to set the runtime value to 100%. I haven’t tested it in years to determine what the current percentage of playback time played “counts” to incrementing the play count, but it is less than 100%.
Currently, these settings do exist but only for the Listen Later queue. Those same settings could be applied to overall playback, imho.
As @Rugby has mentioned there is some logic behind the scenes which might be a bit different from what you’re expecting, but it does not mean it is not working correct.
If you want to have an option to have different plays count logic I do recommend you to submit a feature request in the relevant section -
.
Our Developers are watching it closely so that will be considered.
