wok view apulse/description.txt @ rev 25670
Up mediawiki (1.41.0), memcached (1.6.23), metasploit (6.3.56), modsecurity-apache (2.9.7), mutt (2.2.12), ncurses (6.4), nginx (1.25.4)
| author | Pascal Bellard <pascal.bellard@slitaz.org> |
|---|---|
| date | Sun Feb 25 17:20:49 2024 +0000 (8 months ago) |
| parents | |
| children |
line source
1 The program provides an alternative partial implementation of the PulseAudio
2 API. It consists of a loader script and a number of shared libraries with the
3 same names as from original PulseAudio, so applications could dynamically
4 load them and think they are talking to PulseAudio. Internally, no separate
5 sound mixing daemon is used. Instead, apulse relies on ALSA's dmix, dsnoop,
6 and plug plugins to handle multiple sound sources and capture streams running
7 at the same time. dmix plugin muxes multiple playback streams; dsnoop plugin
8 allow multiple applications to capture from a single microphone; and plug
9 plugin transparently converts audio between various sample formats, sample
10 rates and channel numbers. For more than a decade now, ALSA comes with these
11 plugins enabled and configured by default.
13 apulse wasn't designed to be a drop-in replacement of PulseAudio. It's
14 pointless, since that will be just reimplementation of original PulseAudio,
15 with the same client-daemon architecture, required by the complete feature
16 set. Instead, only parts of the API that are crucial to specific applications
17 are implemented. That's why there is a loader script, named apulse. It
18 updates value of LD_LIBRARY_PATH environment variable to point also to the
19 directory where apulse's libraries are installed, making them available to
20 the application.
22 Name comes from names of both ALSA and PulseAudio. As aoss was a
23 compatibility layer between OSS programs and ALSA, apulse was designed to be
24 compatibility layer between PulseAudio applications and ALSA.