Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed error in Vorbis I specification for limiting residue vector size #35

Closed
wants to merge 1 commit into from

Conversation

penguin359
Copy link
Contributor

The minimum between the encoded residue boundaries and actual block size
needs to be used, otherwise it pushes the boundaries to the edge of the
actual blocksize or beyond.

The minimum between the encoded residue boundaries and actual block size
needs to be used, otherwise it pushes the boundaries to the edge of the
actual blocksize or beyond.
@est31
Copy link

est31 commented Nov 14, 2017

This is definitely something I (and others) have stumbled into as well. I've ended up to just takeresidue_begin and residue_end. I've just tried out taking the minimum like this PR suggests and decoding on my test files gave successful results as well. So 👍 to this PR!

@tdaede
Copy link
Contributor

tdaede commented Nov 29, 2017

Pushed, thanks!

@tdaede tdaede closed this Nov 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants