Sweet! Thank you!
1 Like
What exactly is going on at the end there, it looks like New Junk City - Cavities is playing multiple times, and wondering what was going on, were you just skipping around?
(This is a different instance of the issue)
Ha, yes. I had walked away and missed that song in particular, so I went to the BACK TO tab and tried to listen to it again while I was at my computer, only got about 30 seconds before it autoskipped to the next song.
If you can reproduce that issue Iām interested, there was nothing particularly suspicious about the log besides the fact that the stream ended (naturally) prematurely.
Yeah, thereās really nothing obvious in the logs. I might check that the file at:
C:\Users\radu\AppData\Local\Temp/Plexamp/Caches/Media/a9ae47e302387aa97f746e489c4626bb15e68a0e051be82389d1b14180625905
is 130,719,749 bytes long. Premature cache truncation is the only thing I can imagine might cause what youāre seeing.
Thank you, but I could not find that file; probably it got deleted in the meantime, as it is a cache. However, that is one exemple from the logs; there must be other ones as well. The problem keeps on happening.
Next time it happens, post the logs immediately and during regular business hours Iāll see it right away and tell you the cache file to look for.
Is this happened across all your Plexamp devices, or are you only running into it on Windows?
Hmmm, okay. Just had another instance of the issue (logs attached). Was listening to the song Mexican Stand Off, which ended prematurely and advanced to the next song (Insomnia Dipsomania).
Plexamp-skip2.log (517.5 KB)
Personally, Iām only noticing this issue using Plexamp on Windows. I havenāt had this issue on my Android devices as far as Iāve noticed. I also have sweet fades enabled, could that be related?
This is the cache file in question:
Apr 23, 2025 16:46:14.401 [0x0000a054] INFO - Cache: Opened cache file with 17135690 bytes (of 17135690 total) at 'C:\Users\BBDC-B~1\AppData\Local\Temp/Plexamp/Caches/Media/690ee453ec2f89edd628ef8e6e064e365063ec03e2946f19520bc69a2823e733'.
It might be worth comparing this file to the source FLAC for the track.
Iāve only seen the issue in logs with FLAC files, not sure if thatās a coincidence. And itās funny you mention sweet fades, because it appears they are disabled here, unless you mean Android has them enabled.
At this point all clues are valid!
Huh, I def have sweet fades enabled in the Windows app UI on the device having this issue (def Windows, not Android).
RE: cache file - I found and copied that cache file and changed the extension to .FLAC and played it back (using foobar2000). It appears to be the next song in the queue (Insomnia Dipsomania), not the song that ended prematurely, and the renamed file played all the way through with no issues. Not sure if that helps.
Yes, i will post the logs again when it happens.
I have plexamp on iphone too, but i have no problem with it. Only for windows platform i experience these issues.
Do you guys have a sense of it being a new issue?
If itās āeasyā to reproduce I can get you into a support Slack and feed you betas in a binary search to try to determine when the issue arose.
Plexamp.log (4.3 MB)
ok, just added one log. it happened at 13:37 timestamp.
Personally, I hadnāt noticed this issue until this week. Happy to help however I can!
Same issue, premature death with nothing else suspicious. Very confusing.
it is indeed. if it helps, i can monitor it and provide a log for a longer period with more occurrences. donāt know what else i can do.
If it reproduces for you fairly often, Iād like to give you a link to a previous release so we can see if it happens there, as identifying when it was introduced (if it is new) would be super valuable.
sure, i will try it. please share it.
https://plexamp.plex.tv/plexamp.plex.tv/desktop/Plexamp%20Setup%204.12.0.exe
Mind that it will autoupdate to latest when you restart, so keep it running after install while testing 
The update fixed this issue for me. Thank you!
