From fa4d8d96e772d8afb98ed3ae11f8a1a896f74e56 Mon Sep 17 00:00:00 2001 From: Adrian Sampson Date: Thu, 7 Feb 2013 23:39:13 -0800 Subject: [PATCH] max_rec (#98): more lenient defaults These defaults more closely reflect the current behavior of beets, which I think is desirable. --- beets/config_default.yaml | 6 +++--- docs/reference/config.rst | 11 +++++++---- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/beets/config_default.yaml b/beets/config_default.yaml index 032a457ff..c8696ecf9 100644 --- a/beets/config_default.yaml +++ b/beets/config_default.yaml @@ -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 diff --git a/docs/reference/config.rst b/docs/reference/config.rst index fc85e2b97..95af534ab 100644 --- a/docs/reference/config.rst +++ b/docs/reference/config.rst @@ -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: