Server Version#: 1.24.0.4897
Player Version#: 3.5.0
Hello! I’ve been using Plex for around 2 years now, and plexamp for ~1, and I love them both. By far the best media experience I’ve ever had.
One small annoyance I’ve found is that when skipping a song in plexamp using my headphones (Shure SE-215s), the song does skip and appeara to play (the song progress increases), but makes no sound until I pause and then resume playing.
Skipping in the app works fine, and I’ve tried it with one other headset (Xiaomi Freebuds Pro) and experienced the same. Both headsets skip songs normally in Spotify.
For reference, the “skip song” command on both is a double press of the same button that controls pause/play, and my phone is an Asus ROG phone 2.
Has anyone else experienced this issue, or know of any solution?
Just wanted to say, I’m having the same issue with my Pixel 4a when using a wired headset. Works fine with a bluetooth one, but I’m too lazy to charge them all the time.
Server Version 1.33.0.2444-a220eae4
Player Version 3.5.0
Edit: Also wanted to mention, I have not used Plexamp before. 3.5.0 is the first version I’m using, therefore I cannot say, if that’s a “new bug” or if this behaviour was present before this version already.
What I do now to somewhat make it work is, I first pause the current song and then skip to the next track while it’s paused. That way the current song will fade out and the next one fade in correctly.
Here a log of the problem, as I was asked to submit on the Play Store.
First skip was done by pressing the button on the app screen, second skipping done with the headset. Again, silent start of the track.
Then a pause and a resume which did then fade the track in correctly.
Assuming these two button sequences were generated by your headset, it seems like with the second one, you didn’t press the buttons twice fast enough so it was just interpreted as two toggle operations, which should have left the app playing the same track again after pausing (which is what I see over here if I synthesize those events).
If I’m reading Miingno’s comment correctly, there were 4 total presses, one on the phone and 3 on the headset.
Song skip via phone (Control)
Song skip via headset (which did skip the song and time moved forward in the track but no audio played)
Play/Pause via headset (paused the silent song)
Play/Pause via headset (resume the paused song, audio now plays)
This is exactly what I experience, so I’ll make a log just of the headset presses so it’s clear what is going on. I’ll press the buttons very quickly as well to ensure it is read as a skip.
Edit: Attached the log,
I opened the app at 8:28,
pressed the headset button once to resume the most recently played song,
waited a few seconds,
then pressed the headset button twice quickly to skip to the next song(which worked, it did skip to the next song),
but no audio was played and the song paused without me pressing anything after ~4 seconds.
The first step is correct. And the second one kinda too?
I did press the Play/Pause button twice fast in a row, which skipped song as it was supposed to, however resumed the playback silently. The second (actually third) Play/Pause a few seconds later was when I stopped the silent playback to exit and export the log.
Meaning, the actual function of the skipping part works. It’s really only the silent playback that’s the issue.
Edit: This morning I regardless tried the suggested even faster double press. That however only resulted in a pause. No skip happened.
For the previous log, I had not yet configured the “Analyze audio tracks for loudness”, as I didn’t know that was actually a thing. Now I have activated this setting and have the whole library analyzed, resulting in the same behaviour doctorzeromd has.
Also, Sweet Fades is now working and turned off as I don’t quite like this setting very much.
Here a new log (and in the zip a screen recording too) on how it behaves now:
First press of the headset button to start the track.
Double press to skip to the next track > Track skips but start playing silently for about 3 seconds and then stops on it’s own.
Another press of the headset to start playing the track, this time with sound.
And finally the pause on the app to exit and take the logs.
All fine!
Just wasn’t sure if this was still on the list. After the last update a month ago it seemed like it was treated as a user error and ignored.
Let me know if more logs are needed.
followed by a play.
followed by 