aplay: add support for G.711 A_LAW enconding in AU file format #297
Conversation
This file contains hidden or 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
At the time being, aplay only supports G.711 µ-law, 8-bits PCM and 16-bits PCM encodings for the AU format while the AU format supports many more. In Europe the most G.711 used encoding is the A-law, which is also part of the encodings supported by the AU file format. Add support for that encoding in aplay. Signed-off-by: Christophe Leroy <[email protected]>
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.
At the time being, aplay only supports G.711 µ-law, 8-bits PCM and 16-bits PCM encodings for the AU format while the AU format supports many more.
In Europe the most G.711 used encoding is the A-law, which is also part of the encodings supported by the AU file format.
Add support for that encoding in aplay.