1
Bug Reports / Re: MusicBee skipping to next track on resuming playback after sleep/inactivity
« on: May 13, 2018, 03:21:20 AM »
Does anyone know of a fix/workaround for this issue?
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: 1
2
Bug Reports / Re: MusicBee skipping to next track on resuming playback after sleep/inactivity
« on: May 02, 2018, 11:06:07 PM »
Just verified that this also happens with 3.2.6693 after resuming from sleep - around 5-10 seconds of playback, then it jumps to the next track.
3
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?
4
Bug Reports / Re: Replaygain being ignored for certain MP3 files
« on: January 29, 2017, 12:03:39 PM »
That did the trick for some of the files. The Tag Inspector wasn't showing any APEv2 tags, and only the IDE3v1 Artist, Album, Comment, Genre, Title and Year tags, so I wasn't expecting removing the tags to work. Tried it anyway - removed all Replaygain tags, recalculated them using dbPowerAmp, and now they are recognised by MusicBee!
Still had a stubborn album that refused to play along with this process - in the end I got MusicBee to do the Replaygain analysis, which worked fine. Subsequently redid it with dbPowerAmp (for consistency with the rest of my library), and the tags are still recognised - so no clue as to what the issue was there.
Hadn't seen the Tagging Tools before, so thanks for pointing it out!
Still had a stubborn album that refused to play along with this process - in the end I got MusicBee to do the Replaygain analysis, which worked fine. Subsequently redid it with dbPowerAmp (for consistency with the rest of my library), and the tags are still recognised - so no clue as to what the issue was there.
Hadn't seen the Tagging Tools before, so thanks for pointing it out!
5
Bug Reports / Replaygain being ignored for certain MP3 files
« on: January 28, 2017, 07:13:45 PM »
Hi,
I'm having an issue with Replaygain values being ignored/not recognised on certain MP3 files in my collection - these files have Replaygain tags (applied by dbPowerAmp in common with the rest of my music) which show in the Tag Inspector, but not under volume levelling, and the volume adjustments aren't applied during playback.
For example:
I've tried removing the files from MusicBee and rescanning, but this has no effect. Nor does the latest patched version.
I'm having an issue with Replaygain values being ignored/not recognised on certain MP3 files in my collection - these files have Replaygain tags (applied by dbPowerAmp in common with the rest of my music) which show in the Tag Inspector, but not under volume levelling, and the volume adjustments aren't applied during playback.
For example:
I've tried removing the files from MusicBee and rescanning, but this has no effect. Nor does the latest patched version.
Pages: 1