From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: speaker-test: allow controlling how long the noise is heard by the user
Date: Tue, 30 May 2023 20:42:32 +0200 (CEST) [thread overview]
Message-ID: <20230530184232.921E5F8026A@alsa1.perex.cz> (raw)
In-Reply-To: <1685472145595734358-webhooks-bot@alsa-project.org>
alsa-project/alsa-utils issue #219 was opened from jidanni:
$ speaker-test --nloops 1
makes a pink noise for about one second.
On the man page mention how to make this into say a half second,
as some users would like to listen to shorter test sounds,
and no matter if the user does
```
$ speaker-test --device hdmi:HDMI -c 2 --nloops 1 --period 5
$ speaker-test --device hdmi:HDMI -c 2 --nloops 1 --period 50
$ speaker-test --device hdmi:HDMI -c 2 --nloops 1 --period 500
$ speaker-test --device hdmi:HDMI -c 2 --nloops 1 --period 5000
```
what the user hears is exactly the same, therefore --period is not what
controls this item.
I am saying that some users can confirm their speakers work without
listing to a full second of pink noise, and thus would like a way to
listen to a shorter length.
As far as
```
-b | --buffer TIME
Use buffer size of TIME microseconds. When 0 is given, use the
maximal buffer size. The default value is 0.
-p | --period TIME
Use period size of TIME microseconds. When 0 is given, the pe‐
riods given by -P option is used. The default value is 0.
```
are concerned, they must be documenting something completely different.
Debian
Package: alsa-utils
Version: 1.2.8-1
Issue URL : https://github.com/alsa-project/alsa-utils/issues/219
Repository URL: https://github.com/alsa-project/alsa-utils
parent reply other threads:[~2023-05-30 18:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1685472145595734358-webhooks-bot@alsa-project.org>]
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=20230530184232.921E5F8026A@alsa1.perex.cz \
--to=github@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 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.