From: Anssi Hannula <anssi.hannula@mbnet.fi>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] Change the freq limit of speaker-test
Date: Tue, 21 Jun 2005 18:14:55 +0300 [thread overview]
Message-ID: <42B82EEF.3020401@mbnet.fi> (raw)
In-Reply-To: <s5hpsufoigm.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Tue, 21 Jun 2005 17:50:36 +0300,
> Anssi Hannula wrote:
>
>>Takashi Iwai wrote:
>>
>>>At Fri, 17 Jun 2005 21:14:48 +0300,
>>>Anssi Hannula wrote:
>>>
>>>>I noticed that the speaker-test has limited sine wave frequency to
>>>>50-5000 Hz. Attached patch changes that to 0-24575Hz (that's the limit
>>>>at least here (x86-64) after which the freq would roll over to 0 Hz).
>>>
>>>Does freq=0 really work? I think this will result in zero-division.
>>
>>Well, it produces the expected output (no sound) and does not crash.
>
> Strange. Anyway, accepting freq = 0 doesn't make sense.
> I think we should keep reasonalbe minimal/maximal values to produce
> tones.
I understand that 0 doesn't make any sense.
But I think we should still change the limits, so that users can
experiment things and test their hardware (someone asked for tone
generator in VDR ml, I replied with speaker-test, but it didn't produce
high enough tones) etc, and it wouldn't hurt.
--
Anssi Hannula
-------------------------------------------------------
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-21 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 18:14 [PATCH] Change the freq limit of speaker-test Anssi Hannula
2005-06-21 11:03 ` Takashi Iwai
2005-06-21 14:50 ` Anssi Hannula
2005-06-21 15:08 ` Takashi Iwai
2005-06-21 15:14 ` Anssi Hannula [this message]
2005-06-21 15:26 ` Takashi Iwai
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=42B82EEF.3020401@mbnet.fi \
--to=anssi.hannula@mbnet.fi \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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