LibEnvVars: Difference between revisions

From AlsaProject
Jump to navigation Jump to search
(s/ALSA_CONFIG_PATH_VAR/ALSA_CONFIG_PATH/ (the _VAR suffix is only used in the code: alsa-lib/src/conf.c:2579: #define ALSA_CONFIG_PATH_VAR "ALSA_CONFIG_PATH"))
mNo edit summary
 
(One intermediate revision by the same user not shown)
Line 7: Line 7:
; ALSA_MIXER_SIMPLE_MODULES : path to modules .so files
; ALSA_MIXER_SIMPLE_MODULES : path to modules .so files
; LADSPA_PATH : path to ladspa plugins
; LADSPA_PATH : path to ladspa plugins
Proposed
; LIBASOUND_PCM_DUMP : =1  dump pcm_hw_params to console from any app (similar to aplay -v)

Latest revision as of 08:28, 10 February 2010

The settings of these environment variables affect the operation of alsa-lib

LIBASOUND_DEBUG
=1 print errors to stderr, dump hw_params
=2 also assert(0)
ALSA_CONFIG_PATH
file to use instead of ALSA_CONFIG_DIR/alsa.conf"
ALSA_MIXER_SIMPLE
file to use instead of ALSA_CONFIG_DIR/smixer.conf
ALSA_MIXER_SIMPLE_MODULES
path to modules .so files
LADSPA_PATH
path to ladspa plugins

Proposed

LIBASOUND_PCM_DUMP
=1 dump pcm_hw_params to console from any app (similar to aplay -v)