Hello,
I'm the author and (sort of) maintainer of rawrec
(http://rawrec.sourceforge.net).
I'm working on a maintenance release. There are other programs now that
do what
rawrec does probably better, but it does have some users including some
fairly
complicated scripts (http://soundgrab.sourceforge.net) so I thought that
for
continuity sake I should do this. I'm trying to avoid spending too much
time on
it though.
My question is, given that rawrec implements its own ring buffer using
pthreads,
what is likely the best way to proceed?
What I would like is to simply replace the read/write io calls on the
old /dev/dsp
with analogous calls into ALSA lib, but since it implements its own ring
buffer,
I'm not sure this is a good idea. In truth a slight efficiency loss of
an
extra copy in this little app is not going to be the end of the world,
and it
would be the easiest way to continue (admitedly quite old now) oss
support and
support the rawrec interface.
Is it a problem to have a high priority pair of userspace threads
handling a
ring buffer which then gets filled or drained using snd_pcm_writei with
a pcm
opened in blocking mode, or will the competing userspace threads cause
problems?
Thanks,
Britton
--
Britton Kerin
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
