I'm sorry if I direct this message to a wrong address but this is the first
time I'm using a mailing list and don't know how to reply directly to the
topic in the list.
It appears that you're using Thunderbird so, as far as my experience
with Thunderbird goes, "Reply to all" should automatically add
email@example.com to the list of recipients of your reply. Anyway,
manually setting firstname.lastname@example.org in To: or CC: should do the trick.
I installed the latest nightly and it seems is better.
If I use WASAPI the audio call is not stuttering now (the latest stable
version is 5 months old and I suppose you did many improvements).
Indeed, we improved the audio quality and stability in major ways by
replacing PortAudio with WASAPI as the default audio system.
But the noise suppression function is doing poor job on noise reduction.
Well, Windows is doing the synchronization between the capture and the
playback for the purposes of the acoustic echo cancellation (AEC).
Anyway, (1) it's working perfectly for us and (2) it's unquestionably
far better than what we had with PortAudio and Speex.
Anyway, still more usable than before.
If I activate PortAudio the stuttering is here again. My experiments and
observations lead me to believe I was right - maybe the sound buffers are
too small, and Jitsi fails to set the system timer resolution. By default it
is 15.6ms in one of the systems in the conversation and it stutters bad.
However if I use TimerResolution.exe tool and set to 0.5ms then the call is
Ok with occasional stuttering but Much less frequent.
Still I think there is a problem with the audio buffers and/or failing to
work on the timer resolution on Windows - any music player lowers the
resolution from 15 to at least 1ms when playing sounds.
By the way, is there any side effects of using WASAPI rather than the
PortAudio choice? PortAudio was the default in the stable, now I see the
default is WASAPI after I installed the nightly.
We are moving away from PortAudio because it has multiple performance
and stability issues. Windows Audio Session API (WASAPI) is what we
expect our users on Windows Vista+ to use. So in the terms of your
question, the side effects should be that the audio should exhibit
better quality and stability.
2013/8/24 Teodor Hadjiev <email@example.com>: