[alsa-devel] snd_pcm_drain and partial periods
tpiepho at gmail.com
Fri Nov 25 17:37:34 CET 2011
When the driver schedules the final period, couldn't it check if the
device is draining, and if so try to end playback at the right time.
Of course, it would need to be able to play less than a period of
audio do that.
What is the proper way the finish playing if snd_pcm_drain() will go
past the end of the audio?
On Thu, Nov 24, 2011 at 9:17 AM, Clemens Ladisch <clemens at ladisch.de> wrote:
> Trent Piepho wrote:
>> Say an application does not write a full multiple of the period size
>> with snd_pcm_writei(). It's playing a clip and the clip ends and it
>> doesn't happen to end on a multiple of 6000 frames or whatever the
>> period size is.
>> Now the application calls snd_pcm_drain() to wait for the clip to finish.
>> How does the driver know to stop when it gets to the end of the
>> supplied data?
> It doesn't.
>> It seems like the driver will keep playing until it calls
>> snd_pcm_period_elapsed() at the end of the final period. Then the
>> alsa pcm layer will call the ->trigger() method and stop the stream.
>> Hopefully before the driver has started the next DMA for the next
> Let's hope that the FIFOs are large enough so that the actual playback
> hasn't yet reached the period boundary ...
>> I don't see any documentation for snd_pcm_drain() that says it will
>> keep playing until it finishes a period, even if the data runs out
>> before hand. "For playback wait for all pending frames to be played
>> and then stop the PCM." Seems pretty clear that only the pending
>> frames are played and not the rest of a period.
> ALSA will stop the device when it realizes that it has run out of data
> (just like an underrun). This might happen before the period boundary
> if there is some call to snd_pcm_status() or _delay() that reads the
> current position (and if the hardware also supports reading the current
> It's racy and undocumented, but there's nothing a driver can do about
More information about the Alsa-devel