[xine-devel] alsa expert needed for strange problem

[Michael R. <mr...@us...>]

Hi alsa experts,

I have been investigating some lockups xine was suffering from on my 
system. I tracked things down to the alsa driver, line 427, where xine 
will ask the driver delay with snd_pcm_status_get_delay.
When I uncomment the debugging printf in the next line, I get output 
like this:

audio_alsa_out:delay:delay=8944
audio_alsa_out:delay:delay=8190
audio_alsa_out:delay:delay=7423
audio_alsa_out:delay:delay=9199
audio_alsa_out:delay:delay=9387
audio_alsa_out:delay:delay=8950
audio_alsa_out:delay:delay=-1258281603

At this place, xine is stuck.
The last returned delay is interesting, because adding the value alsa 
reports during init as "boundary", which is 1258291200 here, gives a 
more sensible delay value.
Does anyone have any idea what's happening here and how to fix this?

Michael

-- 
"The use of COBOL cripples the mind; its teaching should therefore be
 regarded as a criminal offense."
	-E.W. Dijkstra