NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/54243 (beeping woes with -current)



The following reply was made to PR kern/54243; it has been noted by GNATS.

From: Tetsuya Isaki <isaki%pastel-flower.jp@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: netbsd-bugs%netbsd.org@localhost,
	gnats-admin%netbsd.org@localhost,
	dholland%NetBSD.org@localhost
Subject: Re: kern/54243 (beeping woes with -current)
Date: Sun, 24 Nov 2019 18:07:54 +0900

 At Sat, 16 Nov 2019 11:40:14 +0000 (UTC),
 dholland%NetBSD.org@localhost wrote:
 > Yes. As of yesterday's tree the default beeps are still very loud and grating.
 > The beep I get after my countermeasures is somewhat different so maybe
 > something changed, but it wasn't enough.
 
 I improved waveforms and volume(amplitude) by your comment.
 The audio beep which I imported first was full-range rectangular wave
 (the code was small but was uncomfortable as you say), and it is now
 pseudo sine wave with 60% amplitude.
 
 For audio beep volume, I chose the default not too small intentionally.
 If you feel the beep is too loud, you can turn it down by setting, but
 if the default beep is too silent, you may not be noticed or you may
 not be able to turn it up by setting.
 The best default value for every person is difficult, but I also think
 a reasonable default is worth.
 
 1. Please let me confirm the problem again.
  Which is(are) your problem(s)?
  A) pitch (frequency) of audio beep.
  B) length of audio beep.
  C) volume (amplitude) of audio beep.
  D) timbre(depending on waveforms) of audio beep.
  E) two or more beep devices sound simultaneously (like spkr@pcppi and
    spkr@audio).
 
 2. Please show me
  - xset q | grep bell
  - wsconsctl -a | grep bell
  - mixerctl -a
 
 3. Is your machine a real hardware? or some emulators?
 4. Does your machine have separate speakers for sysbeep and audio?
 
  (I mean, in some hardware (or environment), it shares one speaker with
  sysbeep and audio.  And these two were not synthesized, seemed to be
  toggled each other.  In result, two beeps that sounded simultaneously
  made unclear.  Although it's my experience.)
 
 5. Do you feel the same problem on console too?
  (In other words, Is the probelm specific to X?)
 
 6. If you feel the same problem on console and if your problem includes
  any of above A, B, or C.  What parameters do you think comfortable
  default (when measuring using wsconsctl)?
  - wsconsctl -w bell.pitch
  - wsconsctl -w bell.period
  - wsconsctl -w bell.volume
 
  Beeps on X applies xset's parameters, and in addition applies
  wsconsctl's parameters.  It's too complicated to use to verify.
 
 Thanks,
 ---
 Tetsuya Isaki <isaki%pastel-flower.jp@localhost / isaki%NetBSD.org@localhost>
 


Home | Main Index | Thread Index | Old Index