general: linux audio extract now considers actual header len #57
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
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.
Dear Maintainer,
i found the toniebox reverse engineering wiki very useful today. As a side-effect, i submit to you a change to the wiki content that hopefully is noted as improvement.
When recommending on how to convert a toniebox data file, the header_len can be easily extracted from the data file itself. Just in case the header_len is not the usual value of 0x0ffc.
Personally i find it easier, if the bash commands are presented as one block that can be copy&pasted with the input file as variable.
with best regards,
qyanu / Max-Julian Pogner