Comment 15 for bug 1815305

I got a new drive and transfered everything over, so far so good.

Another thing that I noticed during this failure. While only a single frame of the FLAC file was broken, the cachingreader gives up and truncates the file at that point. In actuality, the rest of the file is indeed playable (I can seek past the breakage just fine). From a performance standpoint, what I see is that the track hits the breakage and then just goes dead silent.

What would be better would be for the caching reader to mark the frame as bad, but recover if possible and cache the rest of the data. That way there would maybe be a brief dropout, but the rest of the track could keep going. It wouldn't be quite as much of a party stopper.