Displaying 3 results from an estimated 3 matches for "xin1".
Did you mean:
pin1
2007 Mar 14
2
re: decoder issue in sb_celp
Jean 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....
2007 Mar 14
0
re: decoder issue in sb_celp
> 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.
Well, the question is where does the problem come from. To give INF on
the output, there would need to...
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