-
Notifications
You must be signed in to change notification settings - Fork 70
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
Wrong syntax for Opus codec line #12
Comments
Yes. The grammar for rtpmap is lacking. It's defined in RFC as:
and we are just ignoring the encoding parameters. This is one of those annoying ones where you get an extra slash when the parameters are present, otherwise it's not there. Either have to incorporate the slash in the encoding parameters, or just merge clock rate and encoding parameters in one big string. Alternatively, rewrite the grammar formating to handle such cases better. Undecided atm. |
I propose extending the resulting rtpmap Object with a new field "extraParams":
Of course those params must appear in the given order and make the String so they can hold any kind of value. |
Yeah, the problem is having to make the writer better with dealing with parameters that are only sometimes there to do that. But I have a sensible solution to deal with conditionals in the format string - will get a version up later. |
The proper way of indicating Opus codec in the SDP is:
and that is what Chrome generates. But when sdp-transform handles the SDP it converts such a line into:
(which is the old syntax for Opus codec)
The text was updated successfully, but these errors were encountered: