Re: [codec] draft-spittka-payload-rtp-opus-00: a=fmtp:101 application=audio

[Jean-Marc Valin <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/13/2012 06:52 PM, Lars Immisch wrote:
> Well, the draft talks about "audio mode" and "voice mode" [1]. I 
> should have suggested the parameter name "mode" and not
> "application" to stay within the draft's language.

Actually, the audio mode/voice mode will go away in the next revision
- -- it's just not needed considering that the sender knows better.

> But how can the receiver say: "encode at high bit-rate"? I don't
> see how that can be done.

You can do that with the b=AS: parameter

> a=fmtp: 101 maxaveragebitrate=128000 (or any x > 32000) is a bit 
> weak, because that's always true per Table 1.

First, table is just a rule of thumb for the recommended bandwidth
bandwidth in each more. It's not about defining maxaveragebitrate.
Also, we've realised that maxaveragebitrate needs to be a hard cap and
that it's not a good idea to use it for controlling the rate.

> What about maxaveragbitrate=unlimited?

Indeed, we'll make maxaveragbitrate *default* to unlimited in the next
draft. Controlling the bitrate should be done with the b= attribute.

	Jean-Marc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJP2f4tAAoJEJ6/8sItn9q9efIH/Ryhv6dY1MY787Ow4YAVK3Fj
cOaKQVcFOwEeFfto+4a0fVnBdTP0Zb5WBqAAySwFjKmk+72omAGPETsDamqMQhN+
8XGE5/Nx8eq9kGzsEtWp/XkPPUjBxF1iTr9s89MLmmKU0h/O9RdEzGbht9aNL3Go
oDbjWK8/lDi5giOUglFTPOjX3vdZJNGMfX+6qMY93CqROp0shIs+S1J7BJOFl9gs
K9XqRl/uyOV/7QtfN8HGDjsuX4qx/iKkt9+ABD0ZEmSXwNBZnrtDXP9Mx9mMpNlg
iq3s+VzxhT5YHMTLsv0f9M2j2HAHmr1EGQRSBlKqAEnnDfiaLnjmHQDlULXac9U=
=ROUc
-----END PGP SIGNATURE-----