|
a/doc/upmpdcli.txt |
|
b/doc/upmpdcli.txt |
|
... |
|
... |
| 13 |
|
13 |
|
| 14 |
*upmpdcli* is not audited for security issues, and, as far as I
|
14 |
*upmpdcli* is not audited for security issues, and, as far as I
|
| 15 |
know, it may be full of exploitable bugs. Do not run it on an
|
15 |
know, it may be full of exploitable bugs. Do not run it on an
|
| 16 |
Internet-facing host.
|
16 |
Internet-facing host.
|
| 17 |
|
17 |
|
| 18 |
[[upmpcli.audioformats]]
|
18 |
[[upmpdcli.audioformats]]
|
| 19 |
== Audio format support
|
19 |
== Audio format support
|
| 20 |
|
20 |
|
| 21 |
The actual audio decoding and playing is performed by *MPD*, the Music
|
21 |
The actual audio decoding and playing is performed by *MPD*, the Music
|
| 22 |
Player Daemon. In consequence, *upmpdcli* can accept most audio formats
|
22 |
Player Daemon. In consequence, *upmpdcli* can accept most audio formats
|
| 23 |
supported by *MPD*, meaning about anything, including DSD.
|
23 |
supported by *MPD*, meaning about anything, including DSD.
|
|
... |
|
... |
| 28 |
way to transfer these parameters to *MPD* (this is a limitation of the
|
28 |
way to transfer these parameters to *MPD* (this is a limitation of the
|
| 29 |
client protocol). There is actually little reason to use raw PCM, and, for
|
29 |
client protocol). There is actually little reason to use raw PCM, and, for
|
| 30 |
example, WAV streams, which have an identification header, will be handled
|
30 |
example, WAV streams, which have an identification header, will be handled
|
| 31 |
just fine.
|
31 |
just fine.
|
| 32 |
|
32 |
|
|
|
33 |
However, recent versions do support audio/L16, but only with the
|
|
|
34 |
development version of MPD (0.20) and there are conditions on the Media
|
|
|
35 |
Server (it must output the audio formats parameters with the MIME
|
|
|
36 |
type). See this Github issue for more details:
|
|
|
37 |
https://github.com/medoc92/upmpdcli/issues/36#issuecomment-227761220
|
|
|
38 |
|
|
|
39 |
[[upmpdcli.streaming]]
|
|
|
40 |
== Streaming services support
|
|
|
41 |
|
|
|
42 |
Upmpdcli versions 1.4 (not released yet) and later offer support for
|
|
|
43 |
accessing music on some streaming services (where you will need a valid
|
|
|
44 |
account).
|
|
|
45 |
|
|
|
46 |
The initial version only supports the http://www.tidal.com[Tidal] music
|
|
|
47 |
service.
|
|
|
48 |
|
|
|
49 |
When the function is activated, upmpdcli creates a separate auxiliary Media
|
|
|
50 |
Server, with the sole purpose of presenting the streaming server catalog
|
|
|
51 |
(and proxying the streams when necessary). You will see it appear on the
|
|
|
52 |
network if streaming service parameters are present in the configuration
|
|
|
53 |
file. The Media Server name is the one for the upmpdcli instance, with
|
|
|
54 |
"-mediaserver" appended.
|
|
|
55 |
|
|
|
56 |
Streaming is not limited to the local upmpdcli renderer, and the Media
|
|
|
57 |
Server should happily send music to other renderers.
|
|
|
58 |
|
|
|
59 |
=== Notes on Tidal support
|
|
|
60 |
|
|
|
61 |
The software is not unofficialy supported by Tidal, and may just stop to
|
|
|
62 |
work one day... It only works with a valid Tidal subscription.
|
|
|
63 |
|
|
|
64 |
The configuration parameters are described
|
|
|
65 |
link:#_tidal_streaming_service_parameters[further down].
|
| 33 |
|
66 |
|
| 34 |
[[upmpdcli.config]]
|
67 |
[[upmpdcli.config]]
|
| 35 |
== Configuration
|
68 |
== Configuration
|
| 36 |
|
69 |
|
| 37 |
See the man page for command line details. In most situations, *upmpdcli*
|
70 |
See the man page for command line details. In most situations, *upmpdcli*
|