(First, apologies for adding to an old thread - I am seeing this issue too
, but I'm not sure what the etiquette is around here. I'm happy to start a new thread if that's preferred.)
I have Musicbee 3.5.8698 on two PCs. One is Windows 10 22H2, and plays all my tracks. I've never found anything in my collection that it won't play.
The other PC is Windows 11 (also 22H2, albeit of that OS), and plays most
of my tracks - there's some that it barfs at with this "BASS_ERROR_UNKNOWN", and this page is the most "relevant" that came up when I searched for help on the error.
. Don't laugh at my eclectic taste in music
To forestall the obvious questions: yes, I've done a clean install of the application, and I've whitelisted the various files in Windows Defender (and have actually turned off realtime scanning anyway). I've also tried changing the output device - whether WASAPI/Exclusive, or DirectSound, makes no difference.
What's weird is that there's no pattern to the tracks that won't play. The ones that won't play all seem to be .m4a AAC tracks (44100Hz, 32bits per sample, according to VLC, which by the way plays them perfectly)... but I have plenty of other tracks of the same type that play perfectly in Musicbee.
My collection is on my Linux NAS; thinking that it might be a file permissions/access issue, I've tried copying the problem files to the Desktop, and Musicbee still won't play them from there either.
The Musicbee error log shows nothing... literally, it remains empty after failing to play a file.
One oddity, that might be significant, is that when I've removed the tracks from my MB library and re-added them, all their embedded metadata shows up in the library - ID3 tags, album cover art, etc - except
for the track duration, which remains blank. If I re-add a "working" track in the same fashion, the duration is immediately displayed, as expected. Could MB be having trouble reading the headers on these tracks? As I said, VLC plays them perfectly, and they've been created using exactly the same encoder as the working tracks, so I don't think
they're corrupted in any way.
This is a little frustrating, to put it mildly. What can I do to help diagnose and debug this issue? I'm happy to provide more detailed information about my computer configurations if needed.