search for: effoft

...at is the motivation to specify "SHOULD support 8 > kbps bitrate". The main idea is that Speex supports many bit-rates, but for one reason or another, some modes may be left out in implementations (e.g. for RAM or network reasons). What we're saying here is that you should make an effoft to at least support (and offer) the 8 kbps mode to maximise compatibility. > Page 8: > > Optional parameters: > > ptime: see RFC 4566. SHOULD be a multiple of 20 msec. > > maxptime: see RFC 4566. SHOULD be a multiple of 20 msec. > > In real world, ma...

>> The main idea is that Speex supports many bit-rates, but for one reason >> or another, some modes may be left out in implementations (e.g. for RAM >> or network reasons). What we're saying here is that you should make an >> effoft to at least support (and offer) the 8 kbps mode to maximise >> compatibility. > > I understood this. But as you may know: the SDP parameters are PROPOSAL > only and a remote application might use another "mode": this typically > lead to interoperability issue and you sh...

...007, Jean-Marc Valin wrote: >>> The main idea is that Speex supports many bit-rates, but for one reason >>> or another, some modes may be left out in implementations (e.g. for RAM >>> or network reasons). What we're saying here is that you should make an >>> effoft to at least support (and offer) the 8 kbps mode to maximise >>> compatibility. >> >> I understood this. But as you may know: the SDP parameters are PROPOSAL >> only and a remote application might use another "mode": this typically >> lead to interoperabili...

...ify "SHOULD support 8 >> kbps bitrate". > > The main idea is that Speex supports many bit-rates, but for one reason > or another, some modes may be left out in implementations (e.g. for RAM > or network reasons). What we're saying here is that you should make an > effoft to at least support (and offer) the 8 kbps mode to maximise > compatibility. I understood this. But as you may know: the SDP parameters are PROPOSAL only and a remote application might use another "mode": this typically lead to interoperability issue and you should advise in the speci...

Hi all We are about to send an updated version of the internet draft "RTP Payload Format for the Speex Codec" to the IETF AVT working group. Before submitting we would like your input, if you have any comments or input please send them to the mailing list. If we don't get any comments in 1 week (by 22. May 2007) we will go ahead and submit it to the IETF. Of course you can comment