Plexamp skips through tracks at random, but only on Plexamp on one device

Plex Labs
,
1

Server Version#: 1.26.1.5798
Player Version#: 4.2.1

Plexamp has started skipping through tracks, playing at most a seemingly random snippet of each track before moving on to the next and sometimes pausing as if it were buffering, until it lands on a track it is able to play and it plays it completely. There doesn’t seem to be anything in common between the tracks that do and don’t play.

This only seems to happen on Plexamp, not the main Plex app, and only on one particular device (a Pixel 3A). Plexamp on other devices works like a charm.

The issue seemingly started when I migrated Plex onto Docker from an installation on a Linux server. The database was moved on a glusterfs volume, with Cache, Logs, Media, and Metadata directories on an NFS share, which is the same as the previous installation.

We’ve cleared the app’s cache, reset it, reinstalled it, and the problem persists. The Plexamp logs don’t reveal much, although I do see the warning [Javascript] WARNING - Error loading loudness data for track <Track name> for each track that fails to play. This does not appear on the working device.

2

Please post the logs.

3

Any chance you have store track progress on?

4

Plexamp.log (1.4 MB)
Here are the logs from Plexamp.

We’ve also found that the issue affects another device, albeit far less. There also seems to be a correlation between how much the song has been played in the past and how likely it is to not play now. This may be coincidence, though. The songs that won’t play at all also change. One day a song will not play on the affected device, the next day it will and a different song won’t.

Store track progress is not turned on.

5

Seems like it might be related to issues with network connectivity. Looks like only “indirect” connections work, and there’s at least one instance where it fails to connect:

May 23, 2022 10:50:11.582 [0x42d20cb0] INFO - Cache: Network error (-7) occurred, we might want to kick off recovery (still 0 bytes in network buffer).

That being said, I don’t see any direct evidence of tracks being skipped, the log only covers from 10:50 - 11:13. It’s always best to just upload the full zip of logs.

6

131599949418182.zip (363.9 KB)

Here’s the full zip. The previous log was from a period when I observed the tracks being skipped.

Interestingly, when a tiny snippet of a given track does get played, it’s always the same snippet. It could be a half second from the middle of a track, but every time that track is played (and skipped) we hear the same snippet.

Why would a direct connection not work for music only? The server reports remote connectivity is green, and I’m able to direct stream/direct play movies.

7

I see a few errors to decode a file:

/Users/elan/Downloads/131599949418182/Plexamp.2.log:May 21, 2022 23:06:51.705 [0xd5257cb0] ERROR - BASS: Error [ret = BASS_StreamCreate((DWORD)48000, (DWORD)m_channels, BASS_SAMPLE_FLOAT | BASS_STREAM_DECODE, StreamProc, this)] - 6
/Users/elan/Downloads/131599949418182/Plexamp.4.log:May 21, 2022 22:00:38.738 [0xd60e8cb0] ERROR - BASS: Error [ret = BASS_StreamCreate((DWORD)48000, (DWORD)m_channels, BASS_SAMPLE_FLOAT | BASS_STREAM_DECODE, StreamProc, this)] - 6
/Users/elan/Downloads/131599949418182/Plexamp.4.log:May 21, 2022 22:34:34.845 [0xd61cfcb0] ERROR - BASS: Error [ret = BASS_StreamCreate((DWORD)48000, (DWORD)m_channels, BASS_SAMPLE_FLOAT | BASS_STREAM_DECODE, StreamProc, this)] - 6

It looks like these tracks are requesting a transcode from the server. There might be some corresponding logs on the server side.

It’s honestly really hard to decipher what’s going without precise logs, IOW immediately when the issue occurs, grab logs so there’s temporal context.

8

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