All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Carlo Wood <carlo@alinoe.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Bug in OSS simulation (ALSA 0.9.4)
Date: Thu, 10 Jul 2003 14:15:25 +0100	[thread overview]
Message-ID: <3F0D66ED.3090509@superbug.demon.co.uk> (raw)
In-Reply-To: <20030710013326.GA12086@alinoe.com>

Carlo Wood wrote:
> I pinpointed the problem and wrote a small program
> to illustrate the problem.
> 
> When compiling the program given below with:
> 
>   gcc -DUSE_DSP_SETFMT=0 troep.c
> 
> it runs fine.
> 
> But, when compiling it with:
> 
>   gcc -DUSE_DSP_SETFMT=1 troep.c
> 
> It stops rather quickly with reading data.
> 
> Example output of the latter:
> 
> ~>a.out
> Fragment size: 1024
> Number of fragments: 32767
> Number of channels: 1
> Sample rate: 22050
> Read 1024 bytes.
> Number of full fragments that can be read or written without blocking: 0
> Total number of fragments allocated for buffering: 2
> Size of a fragment in bytes: 1024
> Number of bytes that can be read or written immediately without blocking: 0
> #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
> 
Why don't you just use /proc/asound to gather all the info you need, 
like buffer and period sizes.
E.g.
While playing a sound file: -
cat /proc/asound/oss/sndstat
cat /proc/asound/card0/pcm0p/info

cat /proc/asound/card0/pcm0p/sub0/hw_params
cat /proc/asound/card0/pcm0p/sub0/info
cat /proc/asound/card0/pcm0p/sub0/status
cat /proc/asound/card0/pcm0p/sub0/sw_params

If recording a sound, use pcm0c instead of pcm0p

Cheers
James



-------------------------------------------------------
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

  parent reply	other threads:[~2003-07-10 13:15 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
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 [this message]
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=3F0D66ED.3090509@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=carlo@alinoe.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.