[opus] OPUS on embedded platforms
mihooper at bellsouth.net
Tue Dec 18 09:41:46 PST 2012
Timothy, Jean-Marc, et al,
I would very much like to see an "embedded" version of Opus developed that
is optimized for small size and much higher performance (at least on the
CELT side of the codec). I am using V.8 of CELT which takes about 60MIPS
(encode) and 40MIPS (decode) of a TI C5515 100MHz DSP. I have tried to
squeeze Opus into a C55xx but the size of the code has grown to the point
where it requires external memory. Since the C55xx does not have cache, the
performance is not usable.
I would imagine that there is a large potential user base of an
embedded-specific code base.
From: opus-bounces at xiph.org [mailto:opus-bounces at xiph.org] On Behalf Of
Timothy B. Terriberry
Sent: Tuesday, December 18, 2012 11:21 AM
To: opus at xiph.org
Subject: Re: [opus] OPUS on embedded platforms
Jean-Marc Valin wrote:
> On 12/18/2012 09:35 AM, van Bijleveld Christian (ST-CO/ENG1.3) wrote:
>> * I see that there are projects which aim to implement OPUS on a ARM
>> processor. Does anyone know about or have figures regarding
>> resources (memory footprint, clock cycles) which are needed in order
>> to run OPUS on lower-profile processors, such as Cortex Mx, Blackfin
>> DSP or some TI DSP??
Just as a point of reference, a fixed-point build running complexity 10
encode+decode of 48 kHz stereo in CELT mode at 64 kbps is 3.3x realtime
on my 600 MHz Cortex A8 (which is not an Mx, but should at least give
you something to compare to). There's still substantial room for
platform-specific optimizations here.
>> * If these figures are not available, does anyone have an estimate on
>> how many resources OPUS needs compared to the AAC codec??
Which AAC? HE-AAC requires well over 3 times as much CPU as LC-AAC.
opus mailing list
opus at xiph.org
More information about the opus