On Wed, 09.09.09 14:35, Takashi Iwai (tiwai@suse.de) wrote:
I can confirm now that Audacious does indeed play correctly where it didn't before. However, using mplayer with the "-ao openal" switch still doesn't play correctly - in fact, it sounds the same as before - so it looks like OpenAL is actually doing things slightly differently than I thought. :/
Yes, likely. The app like openal is usually more sensible regarding latency, so "safe API" described there wasn't appropriate at all.
Hmm, so are you suggesting I should change that little text about the safe API subset I wrote?
So, users should always set first the buffer size, followed by the period size, is that correct? And if that fails, try the other way round, and if that fails set buffer size only? And if that fails set nothing?
Lennart