You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a song in Plex is on repeat (the single-track repeat mode, so the button has a 1 on it) then Tautulli registers the playback as one, very long song listen rather than multiple listens as expected.
Steps to Reproduce
Find a song in Plex.
Play the song and select single-track repeat (the repeat button with the 1 on it).
Play the song a couple of times.
Look in Tautulli for the playback (in History) and it will show as 1 listen that lasts the whole time you played it.
For example, I have a playback of a single song that lasts 87 minutes (the time I had it on repeat) when the song is only 3 minutes 5 seconds.
Expected Behavior
Tautulli counts each repeat of the song as 1 playback, so that "x plays" is correctly indicated.
I just tried testing this and Plex doesn't send Tautulli a stop event when a track is repeats. Looking directly at the Plex Media Server API, the session ID doesn't change so Plex is treating it as one continuous session.
Describe the Bug
If a song in Plex is on repeat (the single-track repeat mode, so the button has a
1
on it) then Tautulli registers the playback as one, very long song listen rather than multiple listens as expected.Steps to Reproduce
1
on it).For example, I have a playback of a single song that lasts 87 minutes (the time I had it on repeat) when the song is only 3 minutes 5 seconds.
Expected Behavior
Tautulli counts each repeat of the song as 1 playback, so that "x plays" is correctly indicated.
Screenshots
No response
Relevant Settings
No response
Tautulli Version
v2.13.4
Git Branch
master
Git Commit Hash
d019efc
Platform and Version
Python Version
3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
Browser and Version
Chrome 124.0.6367.79 (Official Build) (arm64)
Link to Logs
https://gist.github.com/isaac-mcfadyen/873918d0659f82b68c4e836fca2f5725
The text was updated successfully, but these errors were encountered: