From: Carlo Wood <carlo@alinoe.com>
To: alsa-devel@lists.sourceforge.net
Cc: xvoice@yahoogroups.com
Subject: Re: Bug in OSS simulation (ALSA 0.9.4)
Date: Thu, 10 Jul 2003 03:51:34 +0200 [thread overview]
Message-ID: <20030710015134.GA12482@alinoe.com> (raw)
In-Reply-To: <20030710013326.GA12086@alinoe.com>
On Thu, Jul 10, 2003 at 03:33:26AM +0200, Carlo Wood wrote:
> #fragments, #bytes: 0, 0
> #fragments, #bytes: 1, 1632
> Read 1024 bytes.
> #fragments, #bytes: 2, 2048
> Read 1024 bytes.
> #fragments, #bytes: 1, 1024
> Read 1024 bytes.
> #fragments, #bytes: 0, 0
> #fragments, #bytes: 0, 0
> #fragments, #bytes: 0, 0
> ...etc
Ah... I noticed something else.
It doesn't have to do with whether or not
using SNDCTL_DSP_SETFMT, but with having
an overrun of the number of buffers.
Why is the number of allocated buffers
so low?!
And, is it normal that when the buffers
did overrun that nothing is returned anymore?
How about just skipping it? :/
The problem of ViaVoice is probably that
after it opened /dev/dsp, it first does
something that eats cpu for half a second.
With only 2 buffers of 1024 bytes, I immedeately
get an overrun.
--
Carlo Wood <carlo@alinoe.com>
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
next prev parent reply other threads:[~2003-07-10 1:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 1:33 Bug in OSS simulation (ALSA 0.9.4) Carlo Wood
2003-07-10 1:51 ` Carlo Wood [this message]
2003-07-10 22:54 ` Kai Vehmanen
2003-07-10 23:43 ` Carlo Wood
2003-07-11 0:05 ` Kai Vehmanen
2003-07-11 1:41 ` Carlo Wood
2003-07-10 13:15 ` James Courtier-Dutton
2003-07-10 22:36 ` Carlo Wood
2003-07-10 22:49 ` Kai Vehmanen
2003-07-10 23:07 ` James Courtier-Dutton
2003-07-11 0:00 ` Carlo Wood
2003-07-11 0:21 ` Kai Vehmanen
2003-07-10 23:09 ` Kai Vehmanen
2003-07-11 0:28 ` Carlo Wood
2003-07-11 0:44 ` Kai Vehmanen
2003-07-11 2:03 ` Carlo Wood
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=20030710015134.GA12482@alinoe.com \
--to=carlo@alinoe.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=xvoice@yahoogroups.com \
/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.