RE: Opus codec developments

2012-12-31 Thread Mike Giacomelli
> Okay. A quick grep for iram_ showed that this is not used at all yet. The actual defines are ICODE, ICONST, IBSS, and IDATA. Maybe someone else can help you with your ASM problems (I don't know coldfire).

Re: Opus codec developments

2012-12-31 Thread Jonas Wielicki
On 31.12.2012 14:37, Magnus Holmgren wrote: > Based on my experience with the H140, I'd say start looking at what data > is put in IRAM. The external memory bus is pretty slow in comparison to > IRAM, so putting "hot" buffers and tables in IRAM can make a big > difference. The next step would proba

Re: Opus codec developments

2012-12-31 Thread Magnus Holmgren
On 2012-12-31 13:54, Jonas Wielicki wrote: 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-D

Re: Opus codec developments

2012-12-31 Thread Jonas Wielicki
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 yeste