Displaying 4 results from an estimated 4 matches for "003410".
Did you mean:
003110
2005 Sep 21
0
Speex and Builder
...t; 1) May I know how Speex compared with GIPS codec? It seems that Google,
> Yahoo, and Skype are licensing from GIPS. Are there any good benchmarking
> or fair comparisons?
I think these two emails sum up my opinion about Speex vs. iLBC:
http://lists.xiph.org/pipermail/speex-dev/2005-June/003410.html
http://lists.xiph.org/pipermail/speex-dev/2005-September/003652.html
> 2) In particular, how is the jitter buffer control for Speex in response to
> intermitent poor connection hiccups? Is it robust enough to smooth out lost
> packets (error concealment) and quick enough to recover...
2005 Sep 21
1
Speex and Builder
Hi,
We are planning to use Speex as the speech codec for a VoIP application.
1) May I know how Speex compared with GIPS codec? It seems that Google,
Yahoo, and Skype are licensing from GIPS. Are there any good benchmarking
or fair comparisons?
2) In particular, how is the jitter buffer control for Speex in response to
intermitent poor connection hiccups? Is it robust enough to smooth out
2005 Sep 20
2
Speex and Builder
> Obviously this is Jean-Marc's decision and I'm not telling
> him not to support this compiler. I am however pointing
> out that this compiler is yet more work for very little
> payoff. In the case of my project, the proponent of C++
> Builder sent me a huge, monsterously ugly and totally
> unmaintainable patch to add C++ Builder support. Needless
> to say, that
2005 Sep 21
2
Speex and Builder
...x compared with GIPS codec? It seems that Google,
> > Yahoo, and Skype are licensing from GIPS. Are there any good benchmarking
> > or fair comparisons?
>
> I think these two emails sum up my opinion about Speex vs. iLBC:
> http://lists.xiph.org/pipermail/speex-dev/2005-June/003410.html
> http://lists.xiph.org/pipermail/speex-dev/2005-September/003652.html
>
> > 2) In particular, how is the jitter buffer control for Speex in response
> to
> > intermitent poor connection hiccups? Is it robust enough to smooth out
> lost
> > packets (error concea...