On Sun, 07 Mar 2021 17:26:23 -0800
Chime Hart wrote:
> Package: beep
> Version: 1.4.9-1+b1
> Severity: wishlist
>
> Dear Maintainer,
I am the upstream maintainer of "beep", and I neither maintain any
Debian packages nor am I a Debian user unless you count my Rasberry
Pi's Raspbian.
> Whether I use "beep" or "setterm" neither have a way
> of increasing the volume of the PC-Speaker.
> Supposedly xset has such an option, but that may not work in a
> console only setup.
The PC speaker hardware as such has no notion of sound volume. It just
produces a rectangular pulse with a given frequency, or no pulse at all.
Therefore I doubt very much that xset
In traditional PCs, that signal went to a small dynamic speaker, and
since circa the years 2000..2010 to a piezo buzzer which takes less
space and is less expensive.
If you have a traditional PC with a dynamic speaker, you probably
cannot do much about the audio volume "beep" produces.
If you have a traditional PC with a piezo buzzer, you can indirectly
change the audio volume "beep" produces by changing the beep
*frequency* to a frequency close to the resonant frequency of the piezo
buzzer. My PC's buzzer is loudest around 2100Hz.
However, non-traditional PCs (such as the IBM Thinkpads family where I
have had models from the mid-1990s to the mid-2000s) do not have
that separate speaker and route the audio signal from the PC speaker
hardware to a mixer circuit where the PC speaker audio is mixed
together with the PCM audio, CD player audio, and whatever else there is
and the sum is finally routed to the laptop speakers to produce audible
sound.
On such systems, you can change the volume settings of that mixer
circuit using alsamixer, and then save the mixer setting to have that
setting loaded on the next system boot.
See https://github.com/spkr-beep/beep/issues/13 for another Debian
user's bug report, where the Debian 10 user on a ThinkPad T440p
describes how they solved their audio problem in the comment
https://github.com/spkr-beep/beep/issues/13#issuecomment-637058344
I do not know how well alsamixer works with a screenreader.
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.10.0-2-amd64 (SMP w/2 CPU threads)
> Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
> (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to
> /usr/bin/dash I run in tcsh with a screen-reader
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages beep depends on:
> ii libc6 2.31-9
>
> beep recommends no packages.
>
> beep suggests no packages.
>
> -- no debconf information
> Thanks so much in advance for considering an addition.
