Show Posts
1
Bug Reports / MusicBee skipping to next track on resuming playback after sleep/inactivity
« on: May 02, 2018, 03:28:26 PM »
Having a weird (and irritating) issue with MusicBee (3.1.6590 on Windows 10). After pausing my music and leaving MusicBee alone for an extended period, or letting/telling the computer to sleep/hibernate, when I next resume playback I'll get about 5-10 seconds of playback of the current track before it automatically jumps to the next track. This happens regardless of what playlist/album I'm playing.
Virtually all my music is encoded as FLACs (apart from some stuff downloaded from Google/Amazon etc - none of which I've listened to in a while) stored on a Windows 10 "server" and accessed over the (wired gigabit) network. Crossfading is not enabled.
Typing that out just now makes me think that MusicBee is playing what remains in its buffer, trying to read the remainder from the now expired/timed-out network handle for that file and failing, so then jumping to the next file which creates a new network connection - this is just a guess, but it seems logical.
I'm about to try 3.2.6693 to see if this issue is still there, but as I'll need to leave it alone for a while to replicate the conditions I thought I'd post this first to see if anyone else has experienced this, or knows of any fix?
Virtually all my music is encoded as FLACs (apart from some stuff downloaded from Google/Amazon etc - none of which I've listened to in a while) stored on a Windows 10 "server" and accessed over the (wired gigabit) network. Crossfading is not enabled.
Typing that out just now makes me think that MusicBee is playing what remains in its buffer, trying to read the remainder from the now expired/timed-out network handle for that file and failing, so then jumping to the next file which creates a new network connection - this is just a guess, but it seems logical.
I'm about to try 3.2.6693 to see if this issue is still there, but as I'll need to leave it alone for a while to replicate the conditions I thought I'd post this first to see if anyone else has experienced this, or knows of any fix?
