picard‐config.ini Configuration Options

picard-config.ini Configuration Options

The picard-config.ini file configures picard_album_processor.sh. Copy picard-config.ini.example to picard-config.ini and fill in your paths — the real file is git-ignored. This is a separate config from artwork-config.ini; see artwork-config.ini Configuration Options for that one.

---

[paths]

music_directory

• Description: The root directory of your music library, in ARTIST/ALBUM/ layout.
• Purpose: Tells the script where to find albums to process.
• Required: yes — the script exits if this key is missing.
• Example:

  [paths]
  music_directory = /home/username/MusicToOrganize/

output_directory

• Description: Where successfully processed albums are moved, under a per-artist subfolder.
• Purpose: Keeps finished albums separate from ones still queued for processing.
• Required: yes — the script exits if this key is missing.
• Example:

  [paths]
  output_directory = /home/username/MusicToOrganize/Picard/

failed_directory

• Description: Where albums Picard failed on are moved, under a per-artist subfolder.
• Purpose: Isolates albums that need manual review, and is itself excluded from later processing passes.
• Required: no — defaults to <music_directory>/Failed if left unset.
• Example:

  [paths]
  failed_directory = /home/username/MusicToOrganize/Failed/

---

Example Configuration File

[paths]
music_directory = /home/username/MusicToOrganize/
output_directory = /home/username/MusicToOrganize/Picard/

# Optional. Defaults to "<music_directory>/Failed" if left unset.
#failed_directory = /home/username/MusicToOrganize/Failed/

---

Notes

• All three keys live under a single [paths] section.
• music_directory and output_directory are required; the script prints an error and exits if either is missing.
• See picard_album_processor/DOCS/README-picard_album_processor.md for how these paths are used during a run.