New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"pause after this song" does not work. #2604
Comments
Used to work for me, but this also just started happening to me (Windows 10). |
When will this update be available? I'm having this issue in 4.3.0 which is currently the latest from the site. |
Planning on an update this week, it's a complicated process with lots of manual steps though so no promises. |
I started having this issue several weeks ago. Just installed the 4.4.0 update but it didn't fix any of my problems. Even though it was glitchy (presumably because of GPM sticking the front of the 'next' song on the end of the current song, leaving a second or three of interrupted music from that next track), I nonetheless used it all the time. TBH, I consider pause and the remote two of the best features. (Although the ability to choose output device is really killer -- but I haven't had to use it [and don't actually know it works!] since I finally broke down and switched around my rig to use my good converters as Win default.) |
@KS2Problema, you bring up another good point - how the feature, when it worked, played the beginning of the next song before pausing. I don't think it is the fault of GPM, however, but rather a separate bug with GPMDP. Case in point, if a user plays a single song from an album, the beginning of the next track does not play. I suppose we must wait until the bugfix for #2604 is released, then see if the glitch still affects the "Pause after this song" feature, at which point, if it does, we can open a new issue. |
I just downloaded and tested this issue with 4.4.0. #2604 is not resolved. |
The bit of the next song glued to the currently ending song is, indeed, a problem in Google's Chrome-browser based application, as well. It started when they introduced gapless play. (Which really is a nice feature; tradeoffs, eh?) In my experience, on my system, the next-song-glitch seems to occur if the next song is changed (or, in GPMDP, paused) in the last half-minute to minute. |
Still not working in v. 4.4.1 on OSX 10.12.6. |
Windows 10, v4.4.1: does not work as well |
Ubuntu 17.10 here. Player version 4.4.1. Issue is still present. |
Windows 10, v4.5.0. Been seeing this issue since I first installed GPMDP (v4.4.0), still occurring. |
I just discovered GPMDP and like it a lot. I was excited to see this feature because I would often wait until a song finished and pause before stepping away. Unfortunately, it doesn't work, as described in the issue description. I'm on Linux Mint 18.3. |
This feature is still non-functional on MacOS 10.13.4 using GPMDP 4.5.0 |
not working in windows 7 64-bit, 4.6.1 |
Doesn't work in Windows 10, GPMDP 4.6.1 |
OS
Arch Linux (Manjaro 17.0.1 KDE Plasma 5.35.0)
Issue Descriptions:
When you have a queue of songs, the pause after this song option does nothing. At the end of the song, the next one plays (if there is another song in the queue.)
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: