Michael Broughton wrote: > Update: > > I turned off VAD and the echo canceler and the problem seems to be gone. > Still, this could be a bug. I would be happy to provide more information > if requested. Thanks for the useful report! Could you try again with the very latest pjsua (r1513 as we speak)? I've decreased default EC tail length from 800 to 200 ms since latency is much better now, and I've also increased default WMME buffer size from 60 ms to 100 ms for added stability. This solved the choppy audio problem in my test machine where I had the problem before. cheers, -benny > MIke > > > Michael Broughton wrote: >> Hello, >> >> I am running into another audio quality issue. Let me describe what I am >> doing: >> >> 1. Make outbound call >> 2. Connect NULL sound port >> 3. Create mem player, start playback >> 4. Wait until player is finished, then disconnect and destroy it >> 5. Repeat steps 3-5 >> >> So it's really straightforward, and it works fine for a few minutes. >> After a few minutes I started noticing a slight popping noise in the >> middle of the audio playback. It happens in the same place every time >> the playback loops. >> >> In my log file I noticed that I was getting the following line printed >> regularly before the problem starts: >> >> 10:11:14.874 silencedet.c Vad cur_threshold updated 38-->39. Signal lo=39 >> >> After the popping starts, I get a different regular output: >> >> 10:11:24.215 strm0x3c53848 Starting silence >> 10:11:24.254 strm0x3c53848 Start talksprut.. >> >> I have noticed that these two lines seem to get printed at the same time >> as the popping sound. There is no other useful information in the log >> when the problem starts. >> >> Any idea's? It seems like the VAD is getting disabled or breaking >> somehow, but I can't figure out why. I'm not sure I even need this >> feature enabled since my application end never 'says' anything. >> >> Thanks,
