From: Stewart E. <st...@lu...> - 2005-04-13 09:27:30
|
Thanks for the reply, Jeff. I put in debugging to look at the value returned by audio_device_processed_bytes() when called from set_playback_cursor_position(). I get output like this: audio_device_processed_bytes: 16432 play_a_block: bytes_left 1454776 leaving start with audio_playback=1 audio_device_processed_bytes: 22528 audio_device_processed_bytes: 29552 play_a_block: bytes_left 1441656 audio_device_processed_bytes: 31520 audio_device_processed_bytes: 40512 audio_device_processed_bytes: 28864 play_a_block: bytes_left 1442344 audio_device_processed_bytes: 33136 audio_device_processed_bytes: 40960 audio_device_processed_bytes: 40960 play_a_block: bytes_left 1430248 audio_device_processed_bytes: 40960 audio_device_processed_bytes: 40960 audio_device_processed_bytes: 40960 play_a_block: bytes_left 1430248 Curiously, the number that it freezes at is always 40960. What's the magic in 40960, I wonder? It's not even divisible by 42. ;-) Jeff Welty wrote: > Hi all, > > Sorry to be late answering, I was on the road all last week. I have > to get my taxes filed in 2 days so I > can't spend any time digging into this right now. As I recall, in the > audio util section, it queries the sound > driver to find out how many bytes it can throw at the playback > device. My first guess is that the playback > device is reporting there is no room in it's buffers, and that's why > gwc is showing the bytes_left staying > constant. > > jw |