#beets

When importing https://musicbrainz.org/release/55aa528d-72d9-4... , Beets does complain about the data track missing: Missing tracks (1/11 - 9.1%): / ! [data track] (#1) (9:16). Should there be an empty "01. [data track].flac" in the import directory? or is this expected behavior?

sampsyo: how?

sampsyo: I'm importing a big collection of files with import .

actually I downloaded all my google music account, wanting to sort and drop unneeded stuff

Take a look at the documentation for the `import` command and, in particular, the `--singleton` flag.

Laverne: It looks like there was an effort some time ago to treat data tracks specially, but it never got quite wrapped up: https://github.com/beetbox/beets/pull/1638

sampsyo: he wants the opposite of that pull request :)

Yeah, it seems so. :)

I wasn't aware mb treats data tracks at the beginning differently from data tracks at the end :/

sampsyo: thanks again

:)

btw is beet the right tool for my goal?

i.e. deduplicate, then (automagically) tidy tags

I think so! The duplicates plugin is pretty powerful, and the importer is good at fixing up tags after the fact.

sampsyo: so I don't need to go checking duplicates on a fs-basis, like I was thinking about

good

Probably—but, as usual, I'd recommend keeping a backup.

Hey all. Moving my collection to a new server. Was going to just reimport the whole thing (my old db has cruft in it). I just ran a test import and got "Fell back to default replacements when naming file 16 - Win.mp3. Configure replacements to avoid lengthening the filename."

in my config, under paths: I have default: %upper{%left{%title{$albumartist},1}}/%title{$albumartist}/$year - $album/$track - $title

Which on the old computer worked fine, put stuff into sub folders, etc.

But on the new computer, I get the above. Any tips would be greatly appreciated.

how deep is the base path on the new computer?