Show help.

Show version information.

Choose the server to connect to.

Specify the client name pactl shall pass to the server when connecting.

Dump a few statistics about the PulseAudio daemon.

Dump all currently loaded modules, available sinks, sources, streams and clients.

Asks the PulseAudio server to terminate.

Upload a sound from the specified audio file into the sample cache. The file types supported are those understood by libsndfile. The sample in the cache is named after the audio file, unless the name is explicitly specified.

Play the specified sample from the sample cache. It is played on the default sink, unless the symbolic name or the numerical index of the sink to play it on is specified.

Remove the specified sample from the sample cache.

Move the specified playback stream (identified by its numerical index) to the specified sink (identified by its symbolic name or numerical index).

Move the specified recording stream (identified by its numerical index) to the specified source (identified by its symbolic name or numerical index).

Load the specified module with the specified arguments into the running sound server. Prints the numeric index of the module just loaded to STDOUT. You can use it to unload the module later.

Unload the module instance identified by the specified numeric index.

Suspend or resume the specified sink (which my be specified either by its symbolic name, or by its numeric index), depending whether 1 (suspend) or 0 (resume) is passed as last argument. Suspending a sink will pause all playback. Depending on the module implementing the sink this might have the effect that the underlying device is closed, making it available for other applications to use. The exact behaviour depends on the module.

Suspend or resume the specified source (which my be specified either by its symbolic name, or by its numeric index), depending whether 1 (suspend) or 0 (resume) is passed as last argument. Suspending a source will pause all capturing. Depending on the module implementing the source this might have the effect that the underlying device is closed, making it available for other applications to use. The exact behaviour depends on the module.