Rockbox mail archiveSubject: Re: Opus codec developments
Re: Opus codec developments
From: Jonas Wielicki <j.wielicki_at_sotecware.net>
Date: Mon, 31 Dec 2012 13:54:06 +0100
This goes to the kind people who integrated opus into rockbox. Please
see my questions below, this isn't a rant.
On 16.08.2012 17:00, Dave Hooper wrote:
> What's the performance of the current implementation like (compared to
> other codecs on rockbox today)?
I tested opus on my iriver H320 yesterday. To my disappointment, the
performance was horrible. The UI was lagging (didn't even know that this
was possible in rockbox -- thats what I call true multitasking :) ),
despite the CPU being overclocked all the time to ensure fluent playback.
Well yeah. I just started to dig into the opus code, as I really feel it
should be possible to make this perform better. With vorbis, I get
fluent playback without any hassles in the UI and no CPU overclocking at
all (except while reading from the non-DMA HDD).
I am totally unfamiliar on how opus works (reading the RFC right now),
also I have no knowledge about the rockbox codec framework. Can you give
me some pointers on where to start if I were to optimize this? Are there
any known bottlenecks inside or at the interface from rockbox to opus?
Or do I have to look for opportunities in the libopus code? Is there any
hope at all for such an ancient target as the H320? Is there any
extensive documentation on how to integrate new codecs into rockbox
(which would give me some pointers on how codecs and rockbox interact,
which will be valuable)? If I have to modify the libopus code, how
would I make sure that this (a) won't break on an upstream update and
(b) might go back to upstream in case it's valuable for them too?
cheers and happy new year,
Received on 2012-12-31