Interesting Lucid regression

[Jacob Schmude]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi
I can't speak for others, but portaudio isn't the issue on my particular
system as speech dispatcher uses Pulseaudio directly regardless of
whether Espeak is compiled for portaudio. Speech dispatcher obtains the
audio data and sends it over the backend you specify. On top of that,
I'm using ibmtts not espeak as my primary engine which doesn't touch
Portaudio at all. As I said, on my system it appeared to be a resampling
issue and changing Pulseaudio's resample method to one of slightly
higher quality dealt with the problem, though why this only started
happening with the new Pulseaudio in Lucid I've not been able to determine.

On 04/13/2010 07:51 PM, Tim Cross wrote:
> 
> Your description of poor quality sound for a short time after you first login
> sounds very similar to the issues I had with portAudio initially. 
> 
> In my case it was because portAudio wasn't able to obtain high priority for
> its processes or use realtime scheduling. Given that in the first little time
> after logging in, your system is often doing a bit of work still setting
> things up and the load can be higher than average, this could be affecting
> sound quality if portaudio doesn't have the right scheduling privileges. 
> 
> Grepping for pulsaudio in /var/log/messages should tell you if this is the
> case or not. On my system, pulseaudio reports whether it has been able to
> obtain the necessary priority and scheduling privileges. 
> 
> HTH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvFCIsACgkQybLrVJs+Wi5YHwCfaCY+raU25cWU/7NqVNTZRJ4R
UgYAn23xxcjOl9tPskEVlGemeuqAttIU
=ATuf
-----END PGP SIGNATURE-----