Samuel Bronson wrote: > Yeah, after the audio starts, timestuff() seems never to return again.
I get the impression that the problem is that it's making the incorrect assumption that running a timer handler is more or less instantaneous. Because if it notices that a timer is lagging behind, it will call the timer handler again and again until it has caught up. See tl_process_group() in timers.c.
However, it looks like the timer it creates to call update_sound() will on average take longer than one timer interval to run, when using the PulseAudio driver. In that case, that timer will never ever catch up, and while it's trying to it won't be able to process any other timers in that group.
I'm not sure what the proper fix for this is, though. Torbjörn Andersson -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
