Replies: 2 comments 8 replies
-
How are you importing? Command? Beets version? Latest from git? |
Beta Was this translation helpful? Give feedback.
7 replies
-
One unrelated comment @Stampede, use this for the bancamp plugin: https://github.com/snejus/beetcamp The original one is not maintained anymore and has some issues. HTH |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm just starting to import my collection and this is confusing to me. I would like Beets to update the metadata tags in the music files. I'm pretty sure I have it configured to do so, but the files aren't changed until I
$ beet write
. And the odd thing is that that when I type$ beet write
, then Beets will re-write metadata to the tracks, even when it had already applied the metadata previously. According to the docs, it should not be doing that:As for Beets not writing metadata during the initial import, I'm running the import in incremental mode and when I want to pause and do something else, I wait for the next prompt from Beets and the choose the a[B]ort option. Maybe "abort" makes it stop without writing metadata? Is there a better way to pause importing to go do something else for while?
To start the import sessions, I first cd into the parent music directory and then run
beet import -i .
Here is the import section of my config file. Thanks for any help!
Other info:
It's been a couple of months, but I'm pretty sure that I installed beets with pip.
Beta Was this translation helpful? Give feedback.
All reactions