| Commit message (Collapse) | Author | Files | Lines |
|---|
|
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.
|
|
This document has been unmaintained for more than a year now (since
the day it was submitted).
|
|
Same for "listplaylistinfo".
|
|
|
|
The new option "sample_rate" sets the sample rate for libmikmod.
|
|
|
|
|
|
This command prints a list of decoder plugins and their suffixes /
MIME types.
|
|
Same as the previous patch: create up to 16 configured source ports.
The plugin tries to do its best at guessing the right combination for
the given input file, the number of source and destination ports.
|
|
Be more clear which kind of port should be configured here.
|
|
Use the same name as in the libjack API documentation.
|
|
This new plugin parses extm3u files. Files without the "#EXTM3U"
header are still parsed by the plain old "m3u" plugin.
|
|
jack_client_new() is deprecated. This requires libjack 0.100
(released nearly 5 years ago). We havn't been testing older libjack
versions anyway.
As a side effect, there is the new option "autostart".
|
|
|
|
Instead of using MPD's audio output name (setting "name"), use a
separate configuration option. Change the default to "Music Player
Daemon".
|
|
Signed-off-by: Romain Bignon <romain@peerfuse.org>
|
|
|
|
|
|
|
|
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.
|
|
When the range end is missing, then the maximum possible value is
assumed.
|
|
|
|
The new command "replay_gain_mode" allows the user to switch the
replay gain mode on-the-fly. No more mpd.conf editing.
|
|
There was no setting for disabling replay gain. It was off when the
"replaygain" setting was not there.
|
|
|
|
|
|
|
|
This patch completes the configuration support.
|
|
|
|
|
|
"rescan" is the same as "update", but it discards existing songs in
the database.
|
|
Both options are deprecated, and should not be used anymore. Many
users get confused by their presence.
|
|
The update job id is positive. When used in a command list, MPD
prints one job id for each "update" command.
|
|
Add a second column of comment signs on some parameters which users
shouldn't usually set, unless they know what they're doing.
|
|
|
|
|
|
|
|
[mk: added autoconf test; fixed songlen_data_size type]
|
|
|
|
|
|
The recorder plugin writes audio played by MPD to a file. This may be
useful for recording radio streams.
This implementation is incomplete, because support for tags is
missing, and MPD should be able to record each track to a different
file.
|
|
Removed documentation about the global options mixer_type,
mixer_device and mixer_control.
|
|
The "group" configuration option is similar to "user" as it
sets user set what group MPD shall run as. With "user"
option, MPD changed GID to the GID of the user, however,
more control could be desired.
Moreover, the patch changes the way of checking whether no
setuid(2)/setgid(2) is required -- previously user names
were compered, now UID and GIDs are compered (ie. the one we
already have (getuid(2)/getgid(2)) with the one we want to
change to).
|
|
Since version 0.14, MPD has been logging to standard error instead of
standard output. The option name should reflect that. The old option
continues to work, we will remove it in a future MPD release.
|
|
|
|
|
|
|
|
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 command has been deprecated more than 5 years ago (0.10.0). Its
implementation is a kludge, let's remove it now.
|
|
Some clients have visual feedback for "database update is running".
Using the "database" idle event is unreliable, because it is only
emitted when the database was actually modified. This patch adds the
"update" event, which is emitted when the update is started, and again
when the update is finished, disregarding whether it has been
modified.
|
