From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@alsa-project.org
Subject: driver silence callback
Date: Thu, 24 Mar 2011 13:32:13 +1300 [thread overview]
Message-ID: <4D8A910D.6030604@audioscience.com> (raw)
Greetings,
Is the driver's silence callback meant to be able to *overwrite* some
part of the audio buffer that has already been written e.g. via the
playback *copy* callback?
In the case of my (older) hardware, once audio has been written via the
copy callback, it is gone (into a fifo), there is no way to overwrite
with silence.
The asihpi silence call back will _append_ a period of silence to the
already written audio queue. I'm wondering if this is wrong?
Perhaps I should not have a silence callback at all?
I'm looking at the case in pcm_lib.c snd_pcm_playback_silence() where
"when runtime->silence_size >= runtime->boundary - fill processed area
with silence immediately"
My reference for silence callback.
http://www.alsa-project.org/~tiwai/writing-an-alsa-driver/ch11s02.html
regards
Eliot
next reply other threads:[~2011-03-24 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 0:32 Eliot Blennerhassett [this message]
2011-03-24 7:21 ` driver silence callback Clemens Ladisch
2011-03-24 21:11 ` Eliot Blennerhassett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8A910D.6030604@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).