oysteikt/mpd
0
0
Fork 0
Code Issues Pull Requests Releases Activity

doc/user: new section about external mixer

Browse Source
This commit is contained in:
Max Kellermann 2017-01-03 20:37:25 +01:00
parent 3b1c9aa026
commit 057f98ad45
1 changed files with 24 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
doc/user.xml
View File

@ -647,8 +647,10 @@ systemctl start mpd.socket</programlisting>
linkend="pulse_output">PulseAudio</link>), the linkend="pulse_output">PulseAudio</link>), the
software mixer, the "null" mixer software mixer, the "null" mixer
(<parameter>null</parameter>; allows setting the (<parameter>null</parameter>; allows setting the
volume, but with no effect) or no mixer volume, but with no effect; this can be used as a
(<parameter>none</parameter>). By default, the trick to implement an <link
linkend="external_mixer">external mixer</link>) or no
mixer (<parameter>none</parameter>). By default, the
hardware mixer is used for devices which support it, hardware mixer is used for devices which support it,
and none for the others. and none for the others.
</entry> </entry>
@ -1420,6 +1422,26 @@ buffer_size: 16384</programlisting>
</section> </section>
</chapter> </chapter>
<chapter id="client_hacks">
<title>Client Hacks</title>
<section id="external_mixer">
<title>External Mixer</title>
<para>
The setting '<varname>mixer_type</varname>
"<parameter>null</parameter>"' asks
<application>MPD</application> to pretend that there is a
mixer, but not actually do something. This allows you to
implement a <application>MPD</application> client which
listens for <varname>mixer</varname> events, queries the
current (fake) volume, and uses it to program an external
mixer. For example, your client can forward this setting to
your amplifier.
</para>
</section>
</chapter>
<chapter id="plugin_reference"> <chapter id="plugin_reference">
<title>Plugin reference</title> <title>Plugin reference</title>