From 02fea9f42740e15cb95641a262b243212ba7f846 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Sat, 3 Sep 2016 21:13:36 +0200 Subject: [PATCH] Add link and other small updates --- .../switch.pulseaudio_loopback.markdown | 23 +++++++++---------- 1 file changed, 11 insertions(+), 12 deletions(-) diff --git a/source/_components/switch.pulseaudio_loopback.markdown b/source/_components/switch.pulseaudio_loopback.markdown index eb7c3aaea8a..33ff6c87927 100644 --- a/source/_components/switch.pulseaudio_loopback.markdown +++ b/source/_components/switch.pulseaudio_loopback.markdown @@ -14,25 +14,25 @@ ha_iot_class: "Local Polling" --- -The goal behind this switch is to allow a very flexible whole home audio system based upon PulseAudio. +The goal behind this switch is to allow a very flexible whole home audio system based upon [PulseAudio](https://www.freedesktop.org/wiki/Software/PulseAudio/). -For example, for a system with a 7.1 surround sound card, and 3 instances of mpd running, it is possible to quickly route the output of any mpd instance to any of the 8 possible (4 stereo) channels on the sound card, by loading/unloading a loopback module. This loading/unloading functionality is provided by this component. When the switch is 'on', the loopback module is loaded. When the switch is 'off', the module is not loaded. +For example, for a system with a 7.1 surround sound card, and 3 instances of [MPD](https://www.musicpd.org/) running, it is possible to quickly route the output of any MPD instance to any of the 8 possible (4 stereo) channels on the sound card, by loading/unloading a loopback module. This loading/unloading functionality is provided by this component. When the switch is `on`, the loopback module is loaded. When the switch is `off`, the module is not loaded. -The benefit of this approach is that this audio routing can occur without modifying the design-time configuration of mpd or PulseAudio. +The benefit of this approach is that this audio routing can occur without modifying the design-time configuration of MPD or PulseAudio. -This component uses a TCP connection to control a local or remote PulseAudio server- so there are no local dependencies. +This component uses a TCP connection to control a local or remote PulseAudio server. So there are no local dependencies. To enable this switch, add the following lines to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry switch: - platform: pulseaudio_loopback - name: mpd1 -> bedroom - host: 127.0.0.1 - port: 4712 - source_name: mpd1.monitor - sink_name: bedroom + - platform: pulseaudio_loopback + name: mpd1 -> bedroom + host: 127.0.0.1 + port: 4712 + source_name: mpd1.monitor + sink_name: bedroom ``` Configuration variables: @@ -46,7 +46,6 @@ Configuration variables: - **tcp_timeout** (*Optional*): How long to wait for a response from Pulseaudio before giving up. Default is 3 seconds.

-This component relies on raw TCP commands to PulseAudio. In order for PulseAudio to accept commands with -this component, module-cli-protocol must be loaded on the PulseAudio server. +This component relies on raw TCP commands to PulseAudio. In order for PulseAudio to accept commands with this component, `module-cli-protocol` must be loaded on the PulseAudio server.