doc/README-pulse
changeset 116: 14ac70da1259
parent 21:doc/README-polyp@8b5ea758dd06
manifest: 14ac70da1259
author: tiwai
date: Mon Oct 29 11:07:01 2007 +0100 (6 months ago)
permissions: -rw-r--r--
Fix unexpected assert with pulse plugin

This patch fixes the unexpected assert call at calling snd_pcm_hw_params
in PREPARED state. Since multiple hw_params calls are allowed, the pulse
plugin shouldn't call assert.

Handled in ALSA bug#3470.

From: Sean McNamara <smcnam@gmail.com>
        1 PulseAudio <--> ALSA plugins
        2 ============================
        3 
        4 This plugin allows any program that uses the ALSA API to access a PulseAudio
        5 sound daemon. In other words, native ALSA applications can play and record
        6 sound across a network.
        7 
        8 There are two plugins in the suite, one for PCM and one for mixer control. A
        9 typical configuration will look like:
       10 
       11     pcm.pulse {
       12         type pulse
       13     }
       14 
       15     ctl.pulse {
       16         type pulse
       17     }
       18 
       19 Put the above in ~/.asoundrc, or /etc/asound.conf, and use "pulse" as device
       20 in your ALSA applications. For example:
       21 
       22     % aplay -Dpulse foo.wav
       23     % amixer -Dpulse
       24 
       25 PulseAudio will accept more or less any format you throw at it. So a plug
       26 wrapper is unnecessary. Mixing is also handled so dmix will only cause a
       27 performance hit without any gain.
       28 
       29 The plugins will respect your PulseAudio environment variables (like
       30 PULSE_SERVER), but you can override these in ALSA's configuration files.
       31 
       32 Both plugins accept the "server" parameter, specifying which PulseAudio server
       33 to contact. Both also accept the "device" parameter, which indicate which
       34 source and sink to use.
       35 
       36 The mixer control plugin also accepts the parameters "source" and "sink" for
       37 when you need to specify a sink/source combination with different names. If
       38 you need to do this with PCM:s then specify two PCM:s with different "device".
       39 
       40 If you do not specify any source and/or sink, then the server's defaults will
       41 be used.