Borewit

Part of [v8.3.0](https://github.com/Borewit/music-metadata/releases/tag/v8.3.0)

> @Borewit Thanks a ton! Will keep an eye out for when this is published to npm. Sorry, busy, forgot about it

Part of [v8.3.0](https://github.com/Borewit/music-metadata/releases/tag/v8.3.0)

Do you have the same issue [here](https://audio-tag-analyzer.netlify.app/) using Safari? A workaround is: ```js import {parseBuffer} from 'music-metadata'; let blob; // Assume this Blob is assigned const metadata = await parseBuffer(await...

Is there is any news, feel free to re-open

I will try to switch from BYOB (bring your own buffer)/byte stream to the default stream. Ref: https://developer.mozilla.org/docs/Web/API/ReadableStream/ReadableStream

@jonluca can please retry here: https://fallback-on-default-reader--audio-tag-analyzer.netlify.app/

Do you mind to try one more time @jonluca ? GUI should show v10.8.0-beta.**3**", otherwise please reload your browser.

Any improvement in music-metadata 10.8.1 deployed on https://github.com/Borewit/audio-tag-analyzer @jonluca ? If you experience the same error, can you pinpoint where the out-of-bounds exception occurs?

That was a pretty dumb attempt, as this is the the same `TypeError` error we had in the beginning. This `TypeError` should be caught to fallback on [StreamDefaultReader](https://developer.mozilla.org/docs/Web/API/ReadableStreamDefaultReader). You mind...