beetbox/beets

Picard settings migrator

Open

#1352 opened on Mar 10, 2015

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (12,133 stars) (1,837 forks)batch import
featuregood first issue

Description

Anyone knows an automatic and easy way for migrating MusicBrainz Picard settings (especially file naming, tagging and scripting) to Beets?

The settings I talk about above are named: file_naming_format, tagger_script, ignore_tags, windows_compatible_filenames, ascii_filenames, clear_existing_tags, id3v2_encoding.

I think(!) most other settings aren’t that important.

Here’s an example configuration of Picard: http://lpaste.net/124392

Contributor guide

Tech stack
python
Domain
cli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Python programmingUnderstanding of beets configurationUnderstanding of Picard settings
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Research Picard configuration file format (e.g., .ini files in ~/.config/MusicBrainz/Picard) and beets config format (config.yaml). Look for existing beets plugins that handle data migration or import from other tools. Study beets' plugin API to see how to add a `picardimport` command or plugin. Consider mapping settings like `file naming format` to beets' `paths` config and `tagger script` to beets' scripting language.