> Just set silence_size to boundary. The driver will silence the played
> (unused) portion of the ring buffer.
Brilliant - that'll do nicely until I can bug "them" to fix the
drivers. Thanks very much!
John G
--
Download
On Tue, Mar 16, 2010 at 2:53 PM, Robert Krakora
wrote:
> On Tue, Mar 16, 2010 at 11:39 AM, Robert Krakora
> wrote:
>> On Tue, Mar 16, 2010 at 9:49 AM, Takashi Iwai wrote:
>>> At Tue, 16 Mar 2010 15:21:52 +0100,
>>> Paul Menzel wrote:
Dear Robert,
please always just reply
On Wed, 17 Mar 2010, John Graham wrote:
Thanks for the quick reply.
Application can choose between two methods:
1) enable xrun (set stop_threshold to buffer_size or less) - you are
using this method now
2) disable xrun (set stop_threshold to boundary)
If you disable xrun checking in the dr
Thanks for the quick reply.
> Application can choose between two methods:
>
> 1) enable xrun (set stop_threshold to buffer_size or less) - you are
> using this method now
> 2) disable xrun (set stop_threshold to boundary)
>
> If you disable xrun checking in the driver and if application does not
On Wed, 17 Mar 2010, John Graham wrote:
> Hi there,
>
> Can anyone suggest a good, clean way of handling xruns? I'm using ALSA
> for an embedded platform (TX25 (ARM i.MX25 processor) using an
> SGTL5000 - I2S audio) and sometimes my duplex audio stream goes
> completely silent after an xrun. Then,
Hi there,
Can anyone suggest a good, clean way of handling xruns? I'm using ALSA
for an embedded platform (TX25 (ARM i.MX25 processor) using an
SGTL5000 - I2S audio) and sometimes my duplex audio stream goes
completely silent after an xrun. Then, after another xrun (or a
couple, or a few, or a lot
