1XMMS2D(1) General Commands Manual XMMS2D(1)
2
6 xmms2d - XMMS2 daemon which handles the playback of music and storage
7 of music metadata
8
10 xmms2d [ -vqn ] [ -? / --help ] [ -V / --version ] [ -p plugin_path /
11 --plugindir= plugin_path ] [ -o output_plugin / --output= output_plugin
12 ] [ -c path_to_config_file / --conf= path_to_config_file ] [ -s fd /
13 --status-fd= fd ]
14
16 XMMS2 is a redesign of the XMMS (http://www.xmms.org) music player. It
17 features a client-server model, allowing multiple (even simultaneous!)
18 user interfaces, both textual and graphical. All common audio formats
19 are supported using plugins. On top of this, there is a flexible media
20 library to organise your music.
21 xmms2d is the daemon through which XMMS2 clients playback and manage
23 music. A client library provided allows third parties to easily write
24 XMMS2 clients, especially using the Python and Ruby bindings.
25 xmms2d uses a three part method to playback music. Music is accessed
27 from disk or network using a transport plugin, the data is then passed
28 on to a decoder plugin which decodes the audio into a form that can be
29 played back by an output plugin.
30 xmms2d includes command line options to change the way in which the
32 daemon functions.
33 These options are currently recognised:
35 -v Increases the vebosity of xmms2d
37 -q Decrease the verbosity of xmms2d
39 -V | --version
41 Returns the XMMS2 version
42 -? | --help
44 Displays basic help information for xmms2d
45 -n | --no-logging
47 Disables logging
48 -o output_plugin | --output=output_plugin
50 Specifies a different output plugin to use in place of the
51 default
52 -p plugin_path | --plugindir=plugin_path
54 Specifies a different plugin directory path than the default
55 -c path_to_config_file | --conf=path_to_config_file
57 Specifies a path to an alternative configuration file
58 -s fd | --status-fd=fd
60 Specifies a file descriptor to write to when started
61
63 XMMS2 clients uses IPC sockets to communicate with xmms2d. These IPC
64 sockets are specified in a URL based format with three possible trans‐
65 port methods: unix, tcp, and tcp6.
66 The TCP methods allow clients to connect over IPv4 and IPv6 to xmms2d
68 and therefore allow remote control of XMMS2.
69 A typical IPC socket path using TCP would be:
71 tcp://127.0.0.1:9667
72 The UNIX transport method is for local clients only and creates a file
74 through which XMMS2 clients can access xmms2d.
75 A typical IPC socket path using the UNIX transport would be:
77 unix:///tmp/xmms-ipc-foobar
78
80 $HOME/.config/xmms2/medialib.db or $XDG_CONFIG_HOME/xmms2/medialib.db
81 An sqlite3 database that includes information about each song
82 that has been added to the XMMS2 media library
83 $HOME/.config/xmms2/xmms2.conf or $XDG_CONFIG_HOME/xmms2/xmms2.conf
85 An XML formatted configuration file that allows you to change
86 the default settings of xmms2d
87 $HOME/.config/xmms2/startup.d or $XDG_CONFIG_HOME/xmms2/startup.d
89 A directory populated with programs that run when xmms2d is exe‐
90 cuted
91 $HOME/.config/xmms2/shutdown.d or $XDG_CONFIG_HOME/xmms2/shutdown.d
93 A directory populated with programs that run when xmms2d is
94 shutdown correctly
95 /tmp/xmms-ipc-USER
97 The typical location for the UNIX IPC Socket. USER is the name
98 of the user that executed xmms2d.
99
101 XDG_CONFIG_HOME
102 The path where the xmms2 configuration files and resources are
103 located
104
106 xmms2(1), xmms2-launcher(1), http://xmms2.xmms.org
107
109 The XMMS2 Project was started by Tobias Rundström and Anders Gustafs‐
110 son. It is developed with their lead by a small group of contributers
111 from all over the world.
112
114 This manual page was written by Alexander Botero-Lowry <alex@foxy‐
115 banana.com>
116 XMMS2D(1)