From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0001172]: speaker-test:option -p and -f ignored
Date: Thu, 23 Jun 2005 12:12:34 +0200 [thread overview]
Message-ID: <c12cf8a32145f33bf61df5f54dd7eabe@bugtrack.alsa-project.org> (raw)
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1172>
======================================================================
Reported By: norbert
Assigned To: tiwai
======================================================================
Project: ALSA - utils
Issue ID: 1172
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Resolution: not an issue
Fixed in Version:
======================================================================
Date Submitted: 06-08-2005 15:40 CEST
Last Modified: 06-23-2005 12:12 CEST
======================================================================
Summary: speaker-test:option -p and -f ignored
Description:
speaker-test: options -p and -f are ignored
> speaker-test -c6 -p100 -f200 -Dsurround51
speaker-test 0.0.8
Playback device is surround51
Stream parameters are 48000Hz, S16_LE, 6 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 6 to 5461
Period size range from 3 to 2730
Periods = 4
Buffer time size 2525
To choose buffer_size = 5460
To choose period_size = 1365
was set period_size = 1365
was set buffer_size = 5460
0 - Front Left
4 - Center
(sorry for choosing category aplay, but no speaker-test found)
======================================================================
----------------------------------------------------------------------
tiwai - 06-23-05 12:12
----------------------------------------------------------------------
-p option acceps the value between 1000 and 1000000. 100 is too small.
-f option specifies the frequency of sine waves. If you use pink noises,
it doesn't change anything.
Issue History
Date Modified Username Field Change
======================================================================
06-08-05 15:40 norbert New Issue
06-08-05 15:47 perex Category aplay/arecord =>
speakertest
06-23-05 12:12 tiwai Status new => resolved
06-23-05 12:12 tiwai Resolution open => not an issue
06-23-05 12:12 tiwai Assigned To => tiwai
06-23-05 12:12 tiwai Note Added: 0005178
======================================================================
-------------------------------------------------------
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 reply other threads:[~2005-06-23 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 10:12 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-02 19:29 [ALSA - utils 0001172]: speaker-test:option -p and -f ignored bugtrack
2005-06-23 11:42 bugtrack
2005-06-23 10:41 bugtrack
2005-06-08 13:47 bugtrack
2005-06-08 13:40 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=c12cf8a32145f33bf61df5f54dd7eabe@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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