Fix reading of Wave-Files with odd Chunk-Lengths #386
Merged
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.
This fixes the problem of reading Wave-Files with odd chunk lengths.
The specification says that odd chunks have to be filled with a padding byte (value zero)
which is not included in the chunk length. So the next chunk is word aligned.
This also fixes the problem in pull request #220 but IMO in a way more aligned
with the wave spec.
To allow for malformed wave-files with no padding byte I check if the byte is zero before skipping it.