Ability to detect MPEG when prefixed with some noise #646
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Borewit
requested review from
sindresorhus
and removed request for
sindresorhus
sindresorhus
force-pushed
the
main
branch
2 times, most recently
from
5b9fdd9 to
0e91f7b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow 4 bytes of prefixing MPEG noise.
Via
options.mpegOffsetTollerancethis number can be increased, which will result it a bit slow scanning times.Resolves #628
ToDo
options.mpegOffsetTolleranceoptions.mpegOffsetTolleranceexceed 256 (peeked buffer size) - 2 (MPEG preamble) [bytes]