<manpage name="pulse-daemon.conf" section="5" desc="PulseAudio daemon configuration file">
<synopsis>
- <p><file>~/.pulse/daemon.conf</file></p>
+ <p><file>~/.config/pulse/daemon.conf</file></p>
<p><file>@PA_DEFAULT_CONFIG_DIR@/daemon.conf</file></p>
</synopsis>
<description>
<p>The PulseAudio sound server reads configuration directives from
- a file <file>~/.pulse/daemon.conf</file> on startup and when that
+ a file <file>~/.config/pulse/daemon.conf</file> on startup and when that
file doesn't exist from
<file>@PA_DEFAULT_CONFIG_DIR@/daemon.conf</file>. Please note that the
server also reads a configuration script on startup
<option>
<p><opt>allow-module-loading=</opt> Allow/disallow module
loading after startup. This is a security feature that if
- dsabled makes sure that no further modules may be loaded into
+ disabled makes sure that no further modules may be loaded into
the PulseAudio server after startup completed. It is recommended
to disable this when <opt>system-instance</opt> is
enabled. Please note that certain features like automatic
desktop CPUs the float point resampler is a lot faster, and it
also offers slightly better quality. See the output of
<opt>dump-resample-methods</opt> for a complete list of all
- available resamplers. Defaults to <opt>speex-float-3</opt>. The
+ available resamplers. Defaults to <opt>speex-float-1</opt>. The
<opt>--resample-method</opt> command line option takes precedence.
Note that some modules overwrite or allow overwriting of the
resampler to use.</p>
</option>
<option>
- <p><opt>enable-lfe-remixing=</opt> if disabeld when upmixing or
- downmixing ignore LFE channels. When this option is dsabled the
+ <p><opt>enable-lfe-remixing=</opt> If disabled when upmixing or
+ downmixing ignore LFE channels. When this option is disabled the
output LFE channel will only get a signal when an input LFE
channel is available as well. If no input LFE channel is
available the output LFE channel will always be 0. If no output
<option>
<p><opt>use-pid-file=</opt> Create a PID file in the runtime directory
- (<file>$HOME/.pulse/*-runtime/pid</file>). If this is enabled you may
+ (<file>$XDG_RUNTIMEDIR/pulse/pid</file>). If this is enabled you may
use commands like <opt>--kill</opt> or <opt>--check</opt>. If
you are planning to start more than one PulseAudio process per
user, you better disable this option since it effectively
<option>
<p><opt>system-instance=</opt> Run the daemon as system-wide
- instance, requires root priviliges. Takes a boolean argument,
+ instance, requires root privileges. Takes a boolean argument,
defaults to <opt>no</opt>. The <opt>--system</opt> command line
argument takes precedence.</p>
</option>
+ <option>
+ <p><opt>local-server-type=</opt> Please don't use this option if
+ you don't have to! This option is currently only useful when you
+ want D-Bus clients to use a remote server. This option may be
+ removed in future versions. If you only want to run PulseAudio
+ in the system mode, use the <opt>system-instance</opt> option.
+ This option takes one of <opt>user</opt>, <opt>system</opt> or
+ <opt>none</opt> as the argument. This is essentially a duplicate
+ for the <opt>system-instance</opt> option. The difference is the
+ <opt>none</opt> option, which is useful when you want to use a
+ remote server with D-Bus clients. If both this and
+ <opt>system-instance</opt> are defined, this option takes
+ precedence. Defaults to whatever the <opt>system-instance</opt>
+ is set.</p>
+ </option>
+
<option>
<p><opt>enable-shm=</opt> Enable data transfer via POSIX
shared memory. Takes a boolean argument, defaults to
<section name="Paths">
<option>
- <p><opt>dl-search-path=</opt> The path were to look for dynamic
+ <p><opt>dl-search-path=</opt> The path where to look for dynamic
shared objects (DSOs/plugins). You may specify more than one
- path seperated by colons. The default path depends on compile
+ path separated by colons. The default path depends on compile
time settings. The <opt>--dl-search-path</opt> command line
option takes precedence. </p>
</option>
<p><opt>default-script-file=</opt> The default configuration
script file to load. Specify an empty string for not loading a
default script file. The default behaviour is to load
- <file>~/.pulse/default.pa</file>, and if that file does not
+ <file>~/.config/pulse/default.pa</file>, and if that file does not
exist fall back to the system wide installed version
<file>@PA_DEFAULT_CONFIG_DIR@/default.pa</file>. If run in system-wide
mode the file <file>@PA_DEFAULT_CONFIG_DIR@/system.pa</file> is used
<option>
<p><opt>log-target=</opt> The default log target. Use either
- <opt>stderr</opt>, <opt>syslog</opt> or <opt>auto</opt>. The
- latter is equivalent to <opt>sylog</opt> in case
- <opt>daemonize</opt> is enabled, otherwise to
- <opt>stderr</opt>. Defaults to <opt>auto</opt>. The
- <opt>--log-target</opt> command line option takes
- precedence.</p>
+ <opt>stderr</opt>, <opt>syslog</opt>, <opt>journal</opt> (optional),
+ <opt>auto</opt>, <opt>file:PATH</opt> or <opt>newfile:PATH</opt>. On traditional
+ systems <opt>auto</opt> is equivalent to <opt>syslog</opt>. On systemd-enabled
+ systems, auto is equivalent to <opt>journal</opt>, in case <opt>daemonize</opt>
+ is enabled, and to <opt>stderr</opt> otherwise. If set to <opt>file:PATH</opt>,
+ logging is directed to the file indicated by PATH. <opt>newfile:PATH</opt> is
+ otherwise the same as <opt>file:PATH</opt>, but existing files are never
+ overwritten. If the specified file already exists, a suffix is added to
+ the file name to avoid overwriting. Defaults to <opt>auto</opt>. The
+ <opt>--log-target</opt> command line option takes precedence.</p>
</option>
<option>
</option>
<option>
- <p><opt>log-time=</opt> With each logged messages log the
+ <p><opt>log-time=</opt> With each logged message log the
relative time since startup. Defaults to <opt>no</opt>.</p>
</option>
<option>
<p><opt>log-backtrace=</opt> When greater than 0, with each
- logged message log a code stack trace up the the specified
+ logged message log a code stack trace up the specified
number of stack frames. Defaults to <opt>0</opt>.</p>
</option>
the default real-time priority level as configured with
<opt>realtime-priority=</opt> fits in this resource limit, if
<opt>realtime-scheduling</opt> is enabled. The JACK client
- libraries require a real-time prority of 9 by default. </p>
+ libraries require a real-time priority of 9 by default.</p>
</option>
<option>
<p><opt>rlimit-rttime</opt> Defaults to 1000000.</p>
<opt>s16be</opt>, <opt>s24le</opt>, <opt>s24be</opt>,
<opt>s24-32le</opt>, <opt>s24-32be</opt>, <opt>s32le</opt>,
<opt>s32be</opt> <opt>float32le</opt>, <opt>float32be</opt>,
- <opt>ulaw</opt>, <opt>alaw</opt>. Depending on the endianess of
+ <opt>ulaw</opt>, <opt>alaw</opt>. Depending on the endianness of
the CPU the formats <opt>s16ne</opt>, <opt>s16re</opt>,
<opt>s24ne</opt>, <opt>s24re</opt>, <opt>s24-32ne</opt>,
<opt>s24-32re</opt>, <opt>s32ne</opt>, <opt>s32re</opt>,
<p><opt>default-channel-map</opt> The default channel map.</p>
</option>
+ <option>
+ <p><opt>alternate-sample-rate</opt> The alternate sample
+ frequency. Sinks and sources will use either the
+ default-sample-rate value or this alternate value, typically 44.1
+ or 48kHz. Switching between default and alternate values is
+ enabled only when the sinks/sources are suspended. This option
+ is ignored in passthrough mode where the stream rate will be used.
+ If set to the same value as the default sample rate, this feature is
+ disabled.</p>
+ </option>
+
</section>
<section name="Default Fragment Settings">
be subdivided into several fragments. It is possible to change
these buffer metrics for machines with high scheduling
latencies. Not all possible values that may be configured here are
- available in all hardware. The driver will to find the nearest
+ available in all hardware. The driver will find the nearest
setting supported. Modern drivers that support timer-based
scheduling ignore these options.</p>
<p>With the flat volume feature enabled, the sink HW volume is set
to the same level as the highest volume input stream. Any other streams
(with lower volumes) have the appropriate adjustment applied in SW to
- bring them to the correct overall level. Sadly hadware mixer changes
- cannot be timed accurately and thus this change of volumes can somtimes
+ bring them to the correct overall level. Sadly hardware mixer changes
+ cannot be timed accurately and thus this change of volumes can sometimes
cause the resulting output sound to be momentarily too loud or too soft.
So to ensure SW and HW volumes are applied concurrently without any
glitches, their application needs to be synchronized. The sink