I discovered that starting from svn commit 13186, liibspeex does not work anymore. Version 13178 and earlier works ok. Revision: 13186 Author: jm Date: 0:16:56, 25 June 2007 Message: Tuned the vocoder gains and prevented the ol_gain from being reduced by the encoder for voiced segments. ---- Modified : /trunk/speex/libspeex/nb_celp.c I tested it on Windows Mobile 5.0 PocketPC platform with several different applications (duplex voice capturing/encoding/decoding/playback). If I use any recent libspeex version >=13186, application exits in 2-3 seconds after I stop to talk :(. But if I talk continuously (without long pauses), application works and I hear my own voice passed through speex. Perhaps this info will help you to find out the bug.
Hi Oleg, Thanks for the bug report and the fact you spent the time to track down where it broke.> I tested it on Windows Mobile 5.0 PocketPC platform with several > different applications (duplex voice capturing/encoding/decoding/playback). > If I use any recent libspeex version >=13186, application exits in 2-3 > seconds after I stop to talk :(.by exit, you mean segfault (or whatever the Windows equivalent is), a division by zero, or something else? Do you have the line number by any chance? Also, if you have a file that can reproduce the problem with speexdec (I assumer it's the decoder that crashes), that would help a lot.> But if I talk continuously (without long pauses), application works and > I hear my own voice passed through speex. > Perhaps this info will help you to find out the bug.Sounds like you have VAD/VBR enabled, is that correct? I'll have a closer look at that change in the mean time. Cheers, Jean-Marc
Hi Jean-Marc>> I tested it on Windows Mobile 5.0 PocketPC platform with several >> different applications (duplex voice capturing/encoding/decoding/playback). >> If I use any recent libspeex version >=13186, application exits in 2-3 >> seconds after I stop to talk :(. >> > by exit, you mean segfault (or whatever the Windows equivalent is), a > division by zero, or something else? Do you have the line number by any > chance? Also, if you have a file that can reproduce the problem with > speexdec (I assumer it's the decoder that crashes), that would help a lot. > >It accessed wrong memory location, I think. I can send you complete VS2005 project that I use to test, if it can help.>> But if I talk continuously (without long pauses), application works and >> I hear my own voice passed through speex. >> Perhaps this info will help you to find out the bug. >> > Sounds like you have VAD/VBR enabled, is that correct?Yes, I use both VAD and VBR See you, Oleg