[Bug]: Next Song Does Not Play Automatically (From the album page or the song list)
I have already checked through the existing bug reports and found no duplicates
- [x] Yes
App Version
0.19.0
Music Server and Version
Navidrome 0.58
What local environments are you seeing the problem on?
Desktop Windows
What happened?
Hello,
I’m experiencing the exact same problem reported in Issue #550 and it’s quite frustrating. When I play music (whether from an album, playlist, or smart playlist), the player just stops at the end of the current track and does not automatically move on to the next song. I have to manually click the next song every time, which totally breaks the flow.
This happens in both the web player and mpv mode on my system. I have tried Feishin on Windows 11 as well as on the latest macOS, version 15 Sequoia, and the issue persists on both platforms. The only way I can get songs to queue properly is by clicking the big play button of an album or playlist, but even then, sometimes it still stops. It’s pretty silly behavior for a music player because automatic playback of the next track is such a basic feature. Without this, it’s hard to keep using Feishin as my main music player.
Others in the GitHub thread have noted similar symptoms — stuck progress bar when skipping backward is disabled, no error messages, and it seems to only affect the web player mostly. Some workarounds mentioned are switching to mpv (which works better for some users) or using the Vercel app, where the issue might not happen.
Still, it’s disappointing that this problem persists with no clear fix, making Feishin hard to use for continuous playback.
Is there any hope for a fix soon? Or any unofficial solutions or configuration tweaks that could help?
Thanks for any insights!
Steps to reproduce
Switch to the Feishin web player.
Start playback of any song by:
Playing an entire album (starting from the first song or any other song),
Using the artist play button, or play directly from the list
Listen until the current song finishes.
Notice that the player stops at the end of the current song and does not automatically continue to the next track when played from the list.
Observe that the progress bar may get stuck near the end, and the playback appears paused but the pause button stays visible.
Relevant log output
I found a workaround for this issue: clicking directly on the song title instead of the play button on the album cover allows auto-play to work properly and continues to the next track as expected.
This raises a question: is this different behavior between the play button and clicking the title actually a feature rather than a bug?
If so, it might be confusing for users who expect consistent playback behavior regardless of which UI element they use to start playing music. Would it be possible to add an option in the settings to disable this distinction and make both methods behave the same way?
This would help avoid confusion and provide a more consistent user experience.
Getting this issue on macOS. If I click the album play button (upper button in the image), it'll work fine; if I hit play on a song, it doesn't automatically go to the next one.
Sorry didn't parse previous comment before posting, the workaround works for me too; this bug being fixed would definitely be nice though. Thanks!
very confusing and inconsistent behavior for such a basic thing that new user interacts with in any media player
Using the preview from #1095 on browser does not fix the problem, If you click on the cover of the song/play icon, next song doesnt play automatically. Thanks for the workaround @Bluetupperware , it works flawlessly clicking the title of the song. Hope it gets resolved
EDIT: I kinda found the problem, clicking on the cover art/play icon on a track creates a playlist of only one song(check the (1/1) on the title bar):
Instead if you click on the track name/empty space on the right it creates a normal playlist (1/2161):
I dont know if this is intended or not, but is certainly confusing
Just experienced this issue, quite annoying.
Double-clicking the song works as expected, playing the next song. But clicking the play icon does not work.
I have the same problem, it's very confusing. For now, double-clicking on the title and not on the cover fixes the problem. But it would be good if this changed in the future.
Thanks for the workaround with double-click on track. Would be nice to get a fix for play button as well
Thanks for the workaround, as other said it's very confusing. I'd reckon most people expect music to keep on playing after the first track they clicked on is over. Expected behaviors would be to keep playing that album until the end and then either pause or start a random artist's tracks /artist's genre playlist or simply play the next album of that artist, or an adjacent artist album.
Either way, it's confusing and it would be nice to at least be able to toggle a "randomized playlist after end of queue" behavior by default
Is there a plan to fix this? or is this intended behavior?
That's a good question, and it seems that people wouldn't want it to be the intended behavior.
jumping on in agreement- i didn't know about the title click workaround until now, and was very frustrated to find that playing an album from a specific song would only queue that one song. it's much more intuitive to queue the whole album, with the selected track as its starting point.
my issue is more that clicking the play button and clicking the title do two different things, which isn't intuitive. both use-cases (playing only one song from an album, and playing the whole album from a specific point) are perfectly valid, but there should be a more clear-cut way to do either.
my proposal:
- clicking a song's title or play button should queue the entire context it's selected in (album, playlist, all tracks, etc.), starting from that track. (the same functionality that exists when double-clicking the title)
- to queue a single song, simply clear the existing queue, right-click the desired track, and "Add next"
this issue goes to show that the first use-case is more expected, and should be the default. playing a single track from any given context could reasonably be isolated to this admittedly higher-friction path.
This will be fixed in 1.0.0 (and is already fixed in some cases).
I've been aware of this issue for some time but did not want to address it until I properly rewrote the player handlers.
Fixed in 1.0.0-beta.3