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

Misleading/incorrect statement in Opus codec registration #853

Open
Vanilagy opened this issue Nov 30, 2024 · 1 comment
Open

Misleading/incorrect statement in Opus codec registration #853

Vanilagy opened this issue Nov 30, 2024 · 1 comment

Comments

@Vanilagy
Copy link

The Opus codec registration states the following:
image

The conclusion I draw from this is that when description is set, the bitstream is in the 'ogg' format. However, this is not necessarily the case. description may still be provided even if the format is 'opus', and the 'ogg' format may not even be supported even if description is being set.

Here's a repro link: https://jsfiddle.net/7d1fLmbz/4/
I'm on Chrome Version 131.0.6778.86 on Windows 11.

I think what the registration is meaning to say is that each user agent is free to set description if they want, it's just when they set it it needs to be an Identification Header. It's very useful that it does this and I make use of this description field myself. However, the presence of description cannot be used to conclude whether the format is 'opus' or 'ogg'.

@padenot
Copy link
Collaborator

padenot commented Jan 7, 2025

Yes this needs a bit of work, I don't think this was ever implemented by any browser, per spec, we might want to change the spec.

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

No branches or pull requests

2 participants