max_rec (#98): more lenient defaults

These defaults more closely reflect the current behavior of beets, which I
think is desirable.
This commit is contained in:
Adrian Sampson 2013-02-07 23:39:13 -08:00
parent 7a4c228c79
commit fa4d8d96e7
2 changed files with 10 additions and 7 deletions

View file

@ -61,6 +61,6 @@ match:
medium_rec_thresh: 0.25
rec_gap_thresh: 0.25
max_rec:
partial: low
tracklength: medium
tracknumber: medium
partial: medium
tracklength: strong
tracknumber: strong

View file

@ -363,13 +363,16 @@ To define maxima, use keys under ``max_rec:`` in the ``match`` section::
match:
max_rec:
partial: low
tracklength: medium
tracknumber: medium
partial: medium
tracklength: strong
tracknumber: strong
If a recommendation is higher than the configured maximum and the condition is
met, the recommendation will be downgraded. The maximum for each condition can
be one of ``none``, ``low``, ``medium`` or ``strong``.
be one of ``none``, ``low``, ``medium`` or ``strong``. When the maximum
recommendation is ``strong``, no "downgrading" occurs for that situation.
The above example shows the default ``max_rec`` settings.
.. _path-format-config: