All of lore.kernel.org
 help / color / mirror / Atom feed
From: "random.bits" <random.bits@rogers.com>
To: alsa-devel@lists.sourceforge.net
Subject: alsa driver, repeat playback of buffer contents
Date: Mon, 14 Mar 2005 15:30:20 -0500	[thread overview]
Message-ID: <200503141530.20339.random.bits@rogers.com> (raw)


I have been reading up on the alsa driver. I would like 
to have the alsa driver play a small pcm sound bite 
over and over without have to re-write it to the 
device.

By small, I mean 1.9K in length. I have followed the 
examples enough to get it to play the sound bite once, 
but I cannot figure out how to get it to play it 
multiple times without having to make another call to 
snd_pcm_writei() again.

This sound will play on in the background, while other 
cpu, data bus, and disk intensive work is being 
performed. 

Thank you for any pointers, tips or help.

Mark



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-03-14 20:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 20:30 random.bits [this message]
2005-03-14 21:45 ` alsa driver, repeat playback of buffer contents Lee Revell
2005-03-14 22:20   ` Måns Rullgård
2005-03-15  0:20     ` Lee Revell
2005-03-15  1:14       ` Mark Cannon
2005-03-15  1:19         ` Lee Revell
2005-03-15  7:49         ` Jaroslav Kysela
2005-03-15 18:49           ` random.bits
2005-03-15 18:49             ` Jaroslav Kysela
2005-03-15 21:34               ` random.bits
2005-03-15  8:14       ` Clemens Ladisch

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=200503141530.20339.random.bits@rogers.com \
    --to=random.bits@rogers.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.