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

Spec better codec strings for wav ulaw / alaw #126

Closed
chcunningham opened this issue Jan 26, 2021 · 0 comments · Fixed by #149
Closed

Spec better codec strings for wav ulaw / alaw #126

chcunningham opened this issue Jan 26, 2021 · 0 comments · Fixed by #149
Assignees

Comments

@chcunningham
Copy link
Collaborator

wav files are described with mime types like:
'audio/wav; codecs=1'

I believe codecs=1 signals 'Microsoft PCM Format', as described in this RFC: https://www.ietf.org/rfc/rfc2361.txt

Other notable digits include 6:ulaw and 7:alaw. Chrome recognizes 1 via canPlayType() and kin. Firefox recognizes more. Haven't checked the other UAs.

Such codecs strings aren't very readable, particularly if used in WebCodecs without the accompanying 'audio/wav' prefix. Strawman solution: revive the idea to have a registry of codecs strings. This will serve to document the nice familiar strings for other codecs and give us an option to set a new precedent for the wav strings (e.g. 'pcm', 'ulaw', 'alaw').

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 a pull request may close this issue.

1 participant