Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

speaker-test: allow controlling how long the noise is heard by the user #219

Open
jidanni opened this issue May 30, 2023 · 2 comments
Open

Comments

@jidanni
Copy link
Contributor

jidanni commented May 30, 2023

$ 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

@perexg
Copy link
Member

perexg commented Aug 30, 2023

Yep, it controls the audio buffering parameters. The duration for one loop is hardcoded to 3 seconds for the "all channels" test or 5 seconds for the single channel test (-s).

@dima4p
Copy link

dima4p commented Sep 6, 2024

I support the creation of the feature too. Option -d seems to be good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants