Displaying 4 results from an estimated 4 matches for "decocder".
Did you mean:
  decocded
  
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
comment inline.
On Wed, 16 May 2007, Jean-Marc Valin wrote:
>> 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
2007 May 16
2
draft-ietf-avt-rtp-speex-01.txt
>> 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