From: Raymond <rayau@netvigator.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: [ALSA - utils 0001174]: Speaker Test fails with error message(s) from alsa lib. "problem for start_threshold"
Date: Wed, 22 Jun 2005 18:22:17 +0800 [thread overview]
Message-ID: <42B93BD9.4060806@netvigator.com> (raw)
In-Reply-To: <315013d76908703237d6b3c53ef285d4@bugtrack.alsa-project.org>
I notice that there are female voice wav files in samples subdirectory.
ls speaker-test/samples
Front_Center.wav Makefile Noise.wav Rear_Right.wav
Side_Right.wav
Front_Left.wav Makefile.am Rear_Center.wav sample_map.csv
Front_Right.wav Makefile.in Rear_Left.wav Side_Left.wav
Is there an option to use female voice instead of pink noise, sine wave ?
speaker-test --help
speaker-test 0.0.8
Usage: speaker-test [OPTION]...
-t,--test 1=use pink noise, 2=use sine wave
bugtrack@alsa-project.org wrote:
> A NOTE has been added to this issue.
> ======================================================================
> <https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1174>
> ======================================================================
> Reported By: herby
> Assigned To:
> ======================================================================
> Project: ALSA - utils
> Issue ID: 1174
> Category: speakertest
> Reproducibility: always
> Severity: major
> Priority: normal
> Status: new
> ======================================================================
> Date Submitted: 06-09-2005 00:42 CEST
> Last Modified: 06-22-2005 11:39 CEST
> ======================================================================
> Summary: Speaker Test fails with error message(s) from alsa
> lib. "problem for start_threshold"
> Description:
> Running speaker test gets me:
>
> speaker-test 0.0.8
>
> Playback device is plughw:0,0
> Stream parameters are 48000Hz, S16_LE, 1 channels
> Using 16 octaves of pink noise
> Rate set to 48000Hz (requested 48000Hz)
> Buffer size range from 16 to 32768
> Period size range from 8 to 16384
> Periods = 4
> Buffer time size 2525
> To choose buffer_size = 15052
> To choose period_size = 3763
> was set period_size = 3764
> was set buffer_size = 15052
> ALSA lib pcm.c:824:(snd_pcm_sw_params) snd_pcm_sw_params:
> params->avail_min problem for start_threshold
> Unable to set sw params for playback: Invalid argument
> Setting of swparams failed: Invalid argument
> <<<
> ======================================================================
>
> ----------------------------------------------------------------------
> herby - 06-22-05 10:19
> ----------------------------------------------------------------------
> I've seen recent notes on the frequency range for speaker test (nice to
> have a wide range of things). Has anyone tried the latest version(s) to
> see if this bug pops its head up. I've got other programs that appear to
> exhibit this (or a similar) error, but I feel that a standard program is a
> better example. If you need more information, PLEASE let me know!
>
> ----------------------------------------------------------------------
> tiwai - 06-22-05 11:39
> ----------------------------------------------------------------------
> The bug acked. Will check what's going on there...
>
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-06-22 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 9:39 [ALSA - utils 0001174]: Speaker Test fails with error message(s) from alsa lib. "problem for start_threshold" bugtrack
2005-06-22 10:22 ` Raymond [this message]
2005-06-22 10:34 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2005-06-23 10:06 bugtrack
2005-06-22 8:19 bugtrack
2005-06-15 12:27 bugtrack
2005-06-13 17:55 bugtrack
2005-06-08 22:42 bugtrack
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=42B93BD9.4060806@netvigator.com \
--to=rayau@netvigator.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox