SPKR(4)

✨ SPKR(4) β€” speaker, spkr ✨

okay bestie, gather round πŸ’– this is the manual page for the console speaker device driver β€” you know, that little beeper inside your IBM-PC-compatible machine? she's tiny, she's iconic, and she's about to make sounds you did not know a computer could make. section 4 energy, Kernel Interfaces Manual, let's GO πŸŽ€


🌸 SYNOPSIS 🌸

device speaker
#include <dev/speaker/speaker.h>

πŸ’… DESCRIPTION πŸ’…

So. The speaker device driver lets applications control the PC console speaker on an IBM-PC–compatible machine running FreeBSD. That's the whole gig. She beeps. On purpose. With style. πŸ”₯

Only one process may have this device open at any given time β€” open(2) and close(2) are how you lock it and how you give it back. If you try to open it while somebody else has it locked, you get -1 with an EBUSY error indication. so rude of them, but fair tbh. πŸ™ˆ

Writes to the device are interpreted as play strings in a simple ASCII melody notation. There's also an ioctl(2) request for tone generation at arbitrary frequencies, if you're feeling ✨fancy✨.

good news: sound-generation does not monopolize the processor. fr fr. The driver spends most of its time sleeping while the PC hardware is out there emitting tones, which means other processes can still emit beeps while the driver is running. multitasking queen πŸ‘‘

Applications may call ioctl(2) on a speaker file descriptor to control the speaker driver directly; the definitions for the ioctl(2) interface live in <dev/speaker/speaker.h>. The tone_t structure used in these calls has two fields, specifying a frequency (in Hz) and a duration (in 1/100ths of a second). A frequency of zero is interpreted as a rest. silence, but make it intentional 🫢

At present there are two such ioctl(2) calls:

  • SPKRTONE β€” accepts a pointer to a single tone structure as third argument and plays it. one note. one moment. slay.
  • SPKRTUNE β€” accepts a pointer to the first of an array of tone structures and plays them in continuous sequence; this array must be terminated by a final member with a zero duration. do not forget the zero-duration terminator bestie, she will simply keep reading 😭

The play-string language is modeled on the PLAY statement conventions of IBM Advanced BASIC 2.0. The MB, MF, and X primitives of PLAY are not useful in a timesharing environment and are omitted. The octave-tracking feature and the slur mark are new. ✨ upgrade era ✨

There are 84 accessible notes numbered 1-84 in 7 octaves, each running from C to B, numbered 0-6; the scale is equal-tempered A440 and octave 3 starts with middle C. By default, the play function emits half-second notes with the last 1/16th second being rest time. lil breather. self care. 🌸

Play strings are interpreted left to right as a series of play command groups; letter case is ignored. The play command groups are as follows:

  • CDEFGAB β€” Letters A through G cause the corresponding note to be played in the current octave. A note letter may optionally be followed by an "accidental sign", one of # + or -; the first two of these cause it to be sharped one half-tone, the last causes it to be flatted one half-tone. It may also be followed by a time value number and by sustain dots (see below). Time values are interpreted as for the L command below.
  • O n β€” If n is numeric, this sets the current octave. n may also be one of L or N to enable or disable octave-tracking (it is disabled by default). When octave-tracking is on, interpretation of a pair of letter notes will change octaves if necessary in order to make the smallest possible jump between notes. Thus olbc'' will be played as olb>c'', and olcb'' as olc<b''. Octave locking is disabled for one letter note following >, < and O[0123456]. (The octave-locking feature is not supported in IBM BASIC.)
  • > β€” Bump the current octave up one. ⬆️
  • < β€” Drop the current octave down one. ⬇️
  • N n β€” Play note n, n being 1 to 84 or 0 for a rest of current time value. May be followed by sustain dots.
  • L n β€” Sets the current time value for notes. The default is L4, quarter or crotchet notes. The lowest possible value is 1; values up to 64 are accepted. L1 sets whole notes, L2 sets half notes, L4 sets quarter notes, etc.
  • P n β€” Pause (rest), with n interpreted as for L n. May be followed by sustain dots. May also be written ~.
  • T n β€” Sets the number of quarter notes per minute; default is 120. Musical names for common tempi are:
    • very slow β€” Larghissimo
    • very slow β€” Largo, 40-60
    • very slow β€” Larghetto, 60-66
    • very slow β€” Grave
    • very slow β€” Lento
    • very slow β€” Adagio, 66-76
    • slow β€” Adagietto
    • slow β€” Andante, 76-108
    • medium β€” Andantino
    • medium β€” Moderato, 108-120
    • fast β€” Allegretto
    • fast β€” Allegro, 120-168
    • fast β€” Vivace
    • fast β€” Veloce
    • fast β€” Presto, 168-208
    • very fast β€” Prestissimo
  • M[LNS] β€” Set articulation. MN (N for normal) is the default; the last 1/8th of the note's value is rest time. You can set ML for legato (no rest space) or MS for staccato (1/4 rest space).

Notes (that is, CDEFGAB or N command character groups) may be followed by sustain dots. Each dot causes the note's value to be lengthened by one-half for each one. Thus, a note dotted once is held for 3/2 of its undotted value; dotted twice, it is held 9/4, and three times would give 27/8. math girlie πŸ’…

A note and its sustain dots may also be followed by a slur mark (_, underscore). This causes the normal micro-rest after the note to be filled in, slurring it to the next one. (The slur feature is not supported in IBM BASIC.)

Whitespace in play strings is simply skipped and may be used to separate melody sections. whitespace as aesthetic. we love to see it πŸ¦‹


πŸŽ€ FILES πŸŽ€

  • /dev/speaker β€” speaker device file

🌈 SEE ALSO 🌈


πŸ“œ HISTORY πŸ“œ

The speaker device appeared in FreeBSD 1.0. ancient. legendary. she's been beeping since the beginning πŸ‘‘


πŸ’– AUTHORS πŸ’–

Eric S. Raymond <esr@snark.thyrsus.com>, June 1990


🫢 PORTED BY 🫢

Andrew A. Chernov <ache@astral.msk.su>


πŸ’€ BUGS πŸ’€

okay so listen. Due to roundoff in the pitch tables and slop in the tone-generation and timer hardware (neither of which was designed for precision), neither pitch accuracy nor timings will be mathematically exact. There is no volume control. so she's vibes-based, not science-based 😭

The action of two or more sustain dots does not reflect standard musical notation, in which each dot adds half the value of the previous dot modifier, not half the value of the note as modified. Thus, a note dotted once is held for 3/2 of its undotted value; dotted twice, it is held 7/4, and three times would give 15/8. The multiply-by-3/2 interpretation, however, is specified in the IBM BASIC manual and has been retained for compatibility. yes it's weird. no we're not changing it. periodt. πŸ’…

In play strings which are very long (longer than your system's physical I/O blocks) note suffixes or numbers may occasionally be parsed incorrectly due to crossing a block boundary.

so keep your play strings reasonable, bestie. long ones can trip over a block boundary and misparse a note suffix or a number, and that's just how it is. 🫠

k that's the whole page!! this one came from the Debian crew and it's dated November 10, 2005, and yes, SPKR(4) really is the girlies' beep bible. go make some noise, you've earned it πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from