1
Questions / Popping/crackling when playing (not scrubbing) a file only happens in MusicBee
« on: June 26, 2024, 03:43:06 AM »
So, first things first, I have a song that's a bit faulty. There are certain portions of the song that just get skipped. That's not MusicBee's fault.
However, MusicBee appears to play back those skipped portions differently compared to other music players. There is a noticeable popping/crackling noise whenever those skips occur. I've tested it in Audacity and mpv and that noise doesn't play. So what's different?
I've tried both WASAPI and DirectSound to no avail. Those normalization options didn't change anything either.
I've uploaded a recording of it here: https://youtu.be/M7gS84o0otc
EDIT: I used the FLAC frontend tool to check if it was corrupted and it is. It gave me this error, which confirms it is in fact corrupted:
EDIT 2: Nvm, it appears my hard drive is the one that's faulty. I tried a second check and it returned OK this time. It's an external hard drive connected to an xHCI, and it has shown signs of incorrectly reading files in the past. I overlooked this. My bad.
However, MusicBee appears to play back those skipped portions differently compared to other music players. There is a noticeable popping/crackling noise whenever those skips occur. I've tested it in Audacity and mpv and that noise doesn't play. So what's different?
I've tried both WASAPI and DirectSound to no avail. Those normalization options didn't change anything either.
I've uploaded a recording of it here: https://youtu.be/M7gS84o0otc
EDIT: I used the FLAC frontend tool to check if it was corrupted and it is. It gave me this error, which confirms it is in fact corrupted:
Code
01. ABOVE BELOW.flac: *** Got error code 0:FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
*** Got error code 0:FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
01. ABOVE BELOW.flac: ERROR while decoding data
state = FLAC__STREAM_DECODER_READ_FRAME
EDIT 2: Nvm, it appears my hard drive is the one that's faulty. I tried a second check and it returned OK this time. It's an external hard drive connected to an xHCI, and it has shown signs of incorrectly reading files in the past. I overlooked this. My bad.