Jump to content

Count as played bug?!


Go to solution Solved by andrewilley,

Recommended Posts

  • Solution

The counter only increments when you move on to a new track while the progress bar is over the threshold level. It does not increment if you stop playback and the counter thus resets to zero (e.g. 'Play Single Song' or the last track of a Repeat Off session) , nor when using Repeat Song mode.

Andre

32 minutes ago, andrewilley said:

The counter only increments when you move on to a new track while the progress bar is over the threshold level. It does not increment if you stop playback and the counter thus resets to zero (e.g. 'Play Single Song' or the last track of a Repeat Off session) , nor when using Repeat Song mode.

Andre

Thank you.

19 minutes ago, ScarletNeko said:

The counter also resets on full rescans

I guess logically it should do, as that process effectively builds a whole new 'clean slate' music library from scratch, so nothing has been played at all yet.

Andre

Personally I think the player count logic needs revisiting at some point as the need to progress to the next track with the progress bar set greater than the threshold seems a bit crude, as it doesn't take account of single play modes or repeat plays. It also triggers an increment if you manually scrub to near the end and only listen to the last few seconds of a song before moving on to the next track, which I don't think it should unless you have heard more than that.

Also, don't know if you've noticed, but the instant Play Counter gets incremented if you view the Info/Tags screen as soon as you start playing a song, it does not wait until the threshold has been exceeded as you would expect (although if you stop the song straight away, the count does drop back down to its correct value again).

My suggestion would be that the database field (and thus also the Info/Tags screen, if viewed) gets immediately updated at the point where the duration of music heard exceeds the threshold value. That should apply whether playing from the beginning of a track or starting in the middle, and it should not require moving on to a new track afterwards. e.g. if the threshold is set to 50%, then you must have listened to at least a 2'30" portion of a five minute song.

Andre

4 minutes ago, 6b6561 said:

One example is "Albums", albums are not recreated so at least that's not modified.

They are rebuilt from the newly re-read tag data, which in most cases will be the same as before I guess.

Ratings are temporarily saved and then restored after the Full Rescan though, so I guess there's no reason Play Counts could not be handled in the same way.

Andre

1 hour ago, 6b6561 said:

Sorry for the topic drift, there is a a separate topic on albums not being recreated on full rescan.

Changes in case are a separate issue. Once PA has cached the first version of an Artist or Album name, it will continue to use that version for any varied case instances that it encounters later. Otherwise you might get three individual Artist entries for "ABBA", "Abba" and "abba". Same applies with Album titles. This cached master variant will (I think) survive a Full Rescan as the name will be needed to be able to restore Ratings.

If this occurs, simply remove all instances of that Artist/Album name from your scanned filesystem, then do a rescan, then  put them back to be created again as new entities.

Andre

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...