[Alsa-user] Reducing overruns from arecord

[Ralph at Alsa-U. <als...@sp...>]

I'm seeing "overrun!!! (at least XXX.XXX ms long)" messages from my
arecord cron jobs.  (Well, I'm pretty sure they're from arecord, they
might alternatively be from notlame it pipes to).

I'm wondering if playing with any arecord options (--buffer-time or
--buffer-size perhaps?) might reduce these occurences.

Can anyone here offer some advice?

Best regards, Ralph.