Displaying 4 results from an estimated 4 matches for "xout2".
Did you mean:
out2
2005 Mar 17
1
c55x dsp
.../CNG/VBR, using
a low complexity, say 1, for a midrange bitrate, say 15kbps?
was the c55 dsp able to run real-time on speex for the above configuration?
can someone share their timings?
tia!
oh yes, just downloaded the latest revision, rev 9080
i think line 472 lsp.c
else if (xout1 + xout2 < -SHL(32766,8))
should read
else if (xout1 + xout2 < -SHL(32768,8))
rgds,
tk
2007 Mar 14
2
re: decoder issue in sb_celp
...an Marc-
Thanks for looking into this- I think I needed to give you a
bit more info! Sorry for such a vague initial report.
So most of these problems seem to be coming
from the lsp_to_lpc function. In particular the following:
xout1 = xin1 - 2.f*x_freq[i2] * *n1 + *n2;
xout2 = xin2 - 2.f*x_freq[i2+1] * *n3 + *n4;
... in the floating point version this code can produce xout1 or
xout2 that go to INF.
That is the main issue- I have also seen the IIR filter go wonky
occasionally, which is what is corrupting st->mem_sp. Usually
this is just because there are some odd...
2007 Mar 14
0
re: decoder issue in sb_celp
...into this- I think I needed to give you a
> bit more info! Sorry for such a vague initial report.
>
> So most of these problems seem to be coming
> from the lsp_to_lpc function. In particular the following:
> xout1 = xin1 - 2.f*x_freq[i2] * *n1 + *n2;
> xout2 = xin2 - 2.f*x_freq[i2+1] * *n3 + *n4;
>
> ... in the floating point version this code can produce xout1 or
> xout2 that go to INF.
Well, the question is where does the problem come from. To give INF on
the output, there would need to be a problem with the input. Checked that?
> That...
2007 Mar 13
3
re: decoder issue in sb_celp
A little more info on this:
I backtracked deeper into this and it looks like excBuf
is corrupted, which is corrupted by low_innov_alias
being invalid. However it is not entirely clear where
that gets initialized (in sb_celp it is set to out+st->frame_size)
Tom