| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
The real and detailed documentation is in the user manual.
|
|
Move from doc/mpd.conf.5.
|
|
Move from doc/mpd.conf.5.
|
|
|
|
|
|
|
|
2 MB was too small for cross-fading a 24 bit file. Increasing to 4 MB
is still not too large for weak machines, but is enough for
cross-fading.
|
|
|
|
Look for "$XDG_CONFIG_HOME/mpd/mpd.conf", similar to where mpd looks
for the file under Windows.
|
|
|
|
mpd.conf.5 lists follow_outside_symlinks and follow_inside_symlinks
under REQUIRED, yet also documents a default value for these options,
which only makes sense if they're not actually required.
|
|
|
|
|
|
Additionally, update mpdconf.example to refer to mpd.conf(5) for the
complete list of tags instead of trying to repeat it.
|
|
config options
|
|
Allow port specification in "bind_to_address" settings.
|
|
|
|
When set, MPD will not auto-start playback on startup; it will be in
"paused" state.
|
|
Added a new optional parameter for the shout plugin called "url".
|
|
|
|
Limits the depth of the watched directories. This is useful to keep
resource usage down and speed up MPD startup.
|
|
Add an option for each audio output which enables the use of the
hardware mixer, instead of the software volume code.
This is hardware specific, and assumes linear volume control. This is
not the case for hardware mixers which were tested, making this patch
somewhat useless, but we will use it to experiment with the settings,
to find a good solution.
|
|
Instead of using MPD's audio output name (setting "name"), use a
separate configuration option. Change the default to "Music Player
Daemon".
|
|
|
|
An asterisk means that this attribute should not be enforced, and
stays whatever it used to be. This way, some configuration values
work like masks.
|
|
There was no setting for disabling replay gain. It was off when the
"replaygain" setting was not there.
|
|
Removed documentation about the global options mixer_type,
mixer_device and mixer_control.
|
|
Do all the software volume stuff inside each output thread, not in the
player thread. This allows one software mixer per output device, and
also allows the user to configure the mixer type (hardware or
software) for each audio output.
This moves the global "mixer_type" setting into the "audio_output"
section, deprecating the "mixer_enabled" flag.
|
|
|
|
|
|
This allows you to select controls with duplicate names.
|
|
The old global settings "http_proxy_host", "http_proxy_port",
"http_proxy_user" and "http_proxy_password" continue to work.
|
|
Even if libsamplerate support is enabled, compile the fallback
resampler. When the user specifies the option
"samplerate_converter=internal", it is chosen in favor of
libsamplerate. This may help users with a weak FPU who don't want to
compile a custom MPD from source, because the fallback resampler does
not use floating point operations.
|
|
|
|
"Stickers" are pieces of information attached to existing MPD objects
(e.g. song files, directories, albums). Clients can create arbitrary
name/value pairs. MPD itself does not assume any special meaning in
them.
|
|
Without a music_directory, MPD is an excellent streaming client.
|
|
|
|
mpd uses some additional files to work, such as pid_file, state_file,
db_file, etc. when running mpd as non-root user, it is often that those
files end in ~/.mpd
in that case, we end up with 2 entries in a user's home, .mpdconf and
.mpd - which clutters homedirs.
this patch allows ~/.mpd/mpd.conf as an alternative to ~/.mpdconf,
allowing for a cleaner homedir
|
|
There is no reason to use the shortcut "mix" instead of "mixer".
|
|
|
|
Allow logging to syslog if log_file is configured to "syslog".
|
|
Removed the "error_file" option. There is only one log file now. If
a user wants to see only the errors, he should configure a log_level.
|
|
|
|
The "user" option does not work if MPD is started by an unprivileged
user.
|
|
Additionally, add an example in mpdconf.example.
|
|
MPD 0.13 and older followed all symbolic links. Although this can be
a security problem (as it has always been), 0.14 should offer the same
default behaviour as 0.13.
|
|
The configuration options "follow_outside_symlinks" and
"follow_inside_symlinks" let the user control whether MPD should
follow symbolic links in the music directory.
[mk: converted variables to "bool"; moved configuration to
update_global_init()]
|
|
The manual page suggests that you can specify multiple servers, but it
did not clarify what that means.
|
