Displaying 4 results from an estimated 4 matches for "decocd".
Did you mean:
  decod
  
2015 Dec 31
0
Benchmarking Data for Opus Encoder and Decocder on Cortex M4
Hello All,
I recently completed the porting of Opus Encoder on a Cortex M4 embedded
controller. The decoder is yet to be done. Based on the chat discussion I
would be putting CPU performance numbers for
Encoder: Speech, 16KHz, 16-bit mono channel for the following combinations
Complexity: 0,1,3,5,9 and Frame Size of 20 and 40ms for Output bit rate of
4Kbps and 8Kbps
Any suggestions/critical
2007 May 16
2
draft-ietf-avt-rtp-speex-01.txt
> Page 3:
> 
>    To be compliant with this specification, implementations MUST support
>    8 kHz sampling rate (narrowband)" and SHOULD support 8 kbps bitrate.
>    The sampling rate MUST be 8, 16 or 32 kHz.
> 
> There is a type above after (narrowband), there is a " extra character.
> 
> I don't understand what is the motivation to specify "SHOULD
2007 May 16
0
draft-ietf-avt-rtp-speex-01.txt
...e. Again suggestions welcome.
I mean always the same: be prepared to decode all modes, no matter what
you sent in the SDP as preference.
For example, xlite used to have a speex "quality" parameter and no
negotiation was done: if you were sending data with another mode,
the audio was not decocded. This was exactly the same issue than
the one described above for iLBC decoder in asterisk.
Aymeric
> 	Jean-Marc
2007 May 16
2
draft-ietf-avt-rtp-speex-01.txt
...> I mean always the same: be prepared to decode all modes, no matter what
> you sent in the SDP as preference.
> 
> For example, xlite used to have a speex "quality" parameter and no
> negotiation was done: if you were sending data with another mode,
> the audio was not decocded. This was exactly the same issue than
> the one described above for iLBC decoder in asterisk.
If all you mean is "do your best to decode anything you get no matter
how different it is from what you asked for", then I agree.
	Jean-Marc