Corruption bug: Argument out of range sizeChange must be a safe, positive JS integer #124
Description
Sometimes audio tracks have a frame with a negative first timestamp. I'm unclear on what causes this, but it happens with [nearly?] every audio file exported from Audible, for example. MediaBunny, when encountering this, resamples to fix the negative timestamp (just as an example), I assume ffmpeg does something similar.
node-taglib-sharp both throws and error and produces a corrupt file when encountering this input (apologies for the screenshot of logs, was from a user report):
