Okay, to follow-up; I’ve been using Plex Amp for 2 - 3 hours a day since its release and haven’t noticed any missed plays. None, zero.
@anon18523487 - does this help with narrowing down the issue with the full Plex client?
Okay, to follow-up; I’ve been using Plex Amp for 2 - 3 hours a day since its release and haven’t noticed any missed plays. None, zero.
@anon18523487 - does this help with narrowing down the issue with the full Plex client?
@anon18523487 is this still on your radar? I’ve tested again today with PMS 1.19.4.2935 and the problem is still apparent. After starting to play an album only the play history for the first 3 tracks is recorded. Again, from testing today this isn’t an issue when using Plex Amp.
Yes, still being investigated. It appears to be a race condition so it’s a little hard to track down.
Yes, still being investigated. It appears to be a race condition so it’s a little hard to track down.
Thanks very much for the update. If I can provide any help in terms of testing / providing logs / anything else just let me know. ![]()
If it’s related, Sonos playback is no longer updating playcounts again.
In my particular case, it seems if I use a device that has sweet fades enabled, depending on when the next song starts while the previous song is finishing, it will not update the play count. Try playing songs that have quick endings vs. songs the have slow drawn out fades. Or try using the Plex or Plex Media Player desktop apps as neither of those support sweet fades at all. What are the results?
Just wanted to bump this and add my experience to the thread. Recently made a playlist containing unplayed tracks and noticed the Android app seems to still exhibit this behavior. I’ll often get a few tracks recorded in the Play History before it completely stops updating play counts. This does not seem to be an issue with the Plex for Windows application.
Server on Mac 1.21.0.3616
Plexamp on Mac 3.3.1
I continue to exhibit this behavior and I continue to think it may have something to do, at least in my multiple instances, that it is a time length issue.
Looking at the attachments, you can see that PlexAmp did play data located in the file “The First Noel” by TSO. That song has a 54 second length. The Plex server made no reference that it was played at all. Whereas you can see other songs did play, but for whatever reason the play count did not increment. I did not interrupt the playing at all, just simply refreshing the filter to update the play count row.
Initially I thought it might be just the old Plex app on my old iPhone 4s, but this latest set come from the most recent PlexAmp for Mac.
Chiming in on the short songs part of this, which I am repro’ing very consistently on my end. I am able to repro this playing short songs from the web client, from Plex for Mac, and from Plexamp for iOS. In all of those cases, the server does not bump the play count for short songs nor add a play history. The shorter the song, the more likely this is to be a very consistent repro.
I also suspect a race condition. I had a song that was ~15 seconds long that would not update the play count if I let it play through continuously. From the web client I started playing it, paused it, counted to 20, then resumed it and let it finished, and the server did update the play count. I tried this method on shorter songs of around 5s (such as quick intros from rap albums), and was not able to get it to update the play count no matter how long I paused.
My setup.
At the moment, the Sonos client is again no longer updating play counts, not appearing as a “session” in the dashboard, and therefore not updating automatic play lists. Every time I’ve reported this it has been fixed without any action or updates on my part so I’m assuming this is an issue with the external service? If so can someone give it a kick? Thanks.
I am now finding that many of my “podcasts” (I do not use Plex’s podcast feature, these are downloaded MP3s treated by Plex as “tracks”) are being entered into the database with high play counts despite never having been played before. For example early this morning my podcast download run happened but when I list the play counts, I see that some of them are registered as having been played up to 80 times.
Any suggestions on where to even start with this? Note that these podcasts were downloaded but never played, as my podcast playlist only lists those with a playcount of zero so these ones never got played via any means at all.
Do your tracks have track numbers? I’ve run into an issue where the way Plex counts the plays is based on the guid given by your PMS and ones without a track number are getting confused. Add track numbers and that should fix the issue.
Edit - I get that for podcasts you manually add, having track numbers don’t make sense, but that’s the way it is for now.
I was thinking along these lines and started doing some investigation with a copy of the database and sqlite3, based on the assumption that the new podcasts are being seen as previous ones so are picking up earlier plays from previous tracks. So far I haven’t finished looking as I was just decoding the database schemas. How I’ll fix this I don’t know yet, it depends on what I can do. I may resort to creating a playlist with a Python script like I do for new video files.
@anon18523487 - I know it’s been a while but I thought I’d check if you know whether there’s been any progress with this? The behaviour with the standard Android client looks to be the same from tests I ran this morning.
All advice very gratefully received. 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.