Advanced Linux Sound Architecture

Advanced Linux Sound Architecture (ALSA) is a software framework and part of the Linux kernel that provides an application programming interface (API) for sound card device drivers.

ALSA
Screenshot of Alsamixer 1.0.14
Original author(s)Jaroslav Kysela
Developer(s)ALSA team[1]
Initial release1998 (1998)
Stable release
1.2.1 / November 15, 2019 (2019-11-15)[2]
Written inC[3]
Operating systemLinux
Type
License
Websitealsa-project.org
The Linux API is composed out of the System Call Interface of the Linux kernel, the GNU C Library (by GNU), libdrm, libalsa and libevdev (by freedesktop.org).
ALSA is part of the Linux kernel, while PulseAudio is middleware, a part of the lower levels of the desktop stack. So is SDL.

Some of the goals of the ALSA project at its inception were automatic configuration of sound-card hardware and graceful handling of multiple sound devices in a system. ALSA is released under the GNU General Public License (GPL) and the GNU Lesser General Public License (LGPL).[4]

The sound servers PulseAudio and JACK (low-latency professional-grade audio editing and mixing), the higher-level abstraction APIs OpenAL, SDL audio, etc. work on top of ALSA and implemented sound card device drivers. On Linux systems, ALSA succeeded the older Open Sound System (OSS).

History

The project to develop ALSA was led by Jaroslav Kysela, and was based on the Linux device driver for the Gravis Ultrasound sound card. It started in 1998 and was developed separately from the Linux kernel until it was introduced in the 2.5 development series in 2002 (2.5.4–2.5.5).[5]

In the 2.6 version, it replaced the previous system, Open Sound System (OSS), by default (although a backwards-compatibility layer does exist).[6]

ALSA has a larger and more complex API than OSS, so it can be more difficult to develop an application that uses ALSA as its sound technology. While ALSA may be configured to provide an OSS emulation layer, such functionality is no longer available or is not installed by default in many Linux distributions.

Interactions between different parts of Linux sound output stack

Features

ALSA was designed with some features which were not, at the time of its conception, supported by OSS:

Besides the sound device drivers, ALSA bundles a user-space library for application developers who want to use driver features through an interface that is higher-level than the interface provided for direct interaction with the kernel drivers. Unlike the kernel API, which tries to reflect the capabilities of the hardware directly, ALSA's user-space library presents an abstraction that remains as standardized as possible across disparate underlying hardware elements. This goal is achieved in part by using software plug-ins; for example, many modern sound cards or built-in sound chips do not have a "master volume" control. Instead, for these devices, the user space library provides a software volume control using the "softvol" plug-in, and ordinary application software need not care whether such a control is implemented by underlying hardware or software emulation of such underlying hardware.

Applications

Additional to the software framework internal to the Linux kernel, the ALSA project also provides the command-line utilities alsactl, amixer, arecord/aplay and alsamixer, an ncurses-based TUI.

There also are GUIs programmed by third-party developers, such as gnome-alsamixer (using GTK+), kmix, xfce4-mixer, lxpanel, qashctl, pavucontrol, alsamixergui (using FLTK) and probably even more.

Concepts

This section provides an overview of basic concepts pertaining to ALSA.[7][8][9]

Typically, ALSA supports up to eight cards, numbered 0 through 7; each card is a physical or logical kernel device capable of input and output. Furthermore, each card may also be addressed by its id, which is an explanatory string such as "Headset" or "ICH9".

A card has devices, numbered starting at 0; a device may be of playback type, meaning it outputs sound from the computer, or some other type such as capture, control, timer, or sequencer;[10] device number 0 is used by default when no particular device is specified.

A device may have subdevices, numbered starting at 0; a subdevice represents some relevant sound endpoint for the device, such as a speaker pair. If the subdevice is not specified, or if subdevice number −1 is specified, then any available subdevice is used.

A card's interface is a description of an ALSA protocol for accessing the card; possible interfaces include: hw, plughw, default, and plug:dmix. The hw interface provides direct access to the kernel device, but no software mixing or stream adaptation support. The plughw and default enable sound output where the hw interface would produce an error.

An application typically describes sound output by combining all of the aforementioned specifications together in a device string, which has one of the following forms (which are case-sensitive):

  • interface:card,device,subdevice
  • interface:CARD=1,DEV=3,SUBDEV=2.

An ALSA stream is a data flow representing sound; the most common stream format is PCM that must be produced in such a way as to match the characteristics or parameters of the hardware, including:

  • sampling rate: often 44.1 kHz on home stereos, or 48 kHz on home theaters, yet up to 88.2 kHz, 96 kHz, or even 192 kHz for hi-fi audio production or reproduction.
  • sample width: measured in some number of bits per sample (such as 8, 16, 24, or 32 bits/sample)
  • sample encoding: such as endianness
  • number of channels: 1 for mono, 2 for stereo, or 6 for AC-3/IEC958

Implementations

The ALSA System on Chip (ASoC) layer aims to provide better support for ALSA on embedded systems that use a system-on-chip (SoC) design.[11]

gollark: Clearly, I MUST avoid refreshing.
gollark: It vaguely hurts my eyes somehow so perhaps I should decrease the scrolling speed.
gollark: This is actually interesting. The music being played seems to be missing a chunk of the frequency spectrum for some reason.
gollark: It would need good amplifiers, I suppose, but it's possible. I'll have to survey all our listeners to determine how many actual listening people each thing corresponds to (factoring in time spent with it running but away from the computer, and such).
gollark: JS doesn't support **C** properly, so no.

See also

References
  1. Alsa Team, alsa-project.org, 2008-09-29, retrieved 2012-01-08
  2. Changelog between 1.1.9 and 1.2.1 releases, alsa-project.org, retrieved 2019-11-15
  3. "ALSA", Analysis Summary, Ohloh, retrieved 2012-01-08
  4. "Introduction". alsa-project.org. Retrieved 2012-01-08.
  5. Linux 2.5.5 release notes, retrieved 2012-01-08
  6. OSS Emulation, archived from the original on 2012-06-05, retrieved 2012-07-07
  7. Tranter, Jeff (October 2004), "Introduction to Sound Programming with ALSA", Linux Journal, retrieved 2012-01-08
  8. Phillips, Dave (June 2005), "A User's Guide to ALSA", Linux Journal, archived from the original on 2012-01-09, retrieved 2012-01-08
  9. Alsa C library Doxygen documentation, October 2007, retrieved 2012-01-08
  10. "ALSA project - the C library reference: Sequencer interface". www.alsa-project.org. Retrieved 2019-04-30.
  11. ALSA SoC Layer, kernel.org, 2017-07-13
Various layers within Linux, also showing separation between the userland and kernel space
User mode User applications For example, bash, LibreOffice, GIMP, Blender, 0 A.D., Mozilla Firefox, etc.
Low-level system components: System daemons:
systemd, runit, logind, networkd, PulseAudio, ...		 Windowing system:
X11, Wayland, SurfaceFlinger (Android)		 Other libraries:
GTK+, Qt, EFL, SDL, SFML, FLTK, GNUstep, etc.		 Graphics:
Mesa, AMD Catalyst, ...
C standard library open(), exec(), sbrk(), socket(), fopen(), calloc(), ... (up to 2000 subroutines)
glibc aims to be fast, musl and uClibc target embedded systems, bionic written for Android, etc. All aim to be POSIX/SUS-compatible.
Kernel mode Linux kernel stat, splice, dup, read, open, ioctl, write, mmap, close, exit, etc. (about 380 system calls)
The Linux kernel System Call Interface (SCI, aims to be POSIX/SUS-compatible)
Process scheduling
subsystem		 IPC
subsystem		 Memory management
subsystem		 Virtual files
subsystem		 Network
subsystem
Other components: ALSA, DRI, evdev, LVM, device mapper, Linux Network Scheduler, Netfilter
Linux Security Modules: SELinux, TOMOYO, AppArmor, Smack
Hardware (CPU, main memory, data storage devices, etc.)
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.