Replies: 2 comments
-
This is weird. Why doesn't beet
I use the -A since I don't want beet to try musicbrainz for these files.
A beet info, no label here:
But when I issue a
|
Beta Was this translation helpful? Give feedback.
0 replies
-
It doesn't write even if I explicitly pass the -w flag to import. But a beet write afterwards work. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So I went ahead and started a beet update yesterday, thinking that my
custom rules would be in effect, i.e label:ocremix.
I imported those files a while back like this:
And the tracks were moved to exactly where I wanted them.
Now, when I did the update, however, beets created over a thousand new
artist directories, placing the individual tracks inside them. Just like
the ocremix label rule didn't exist anymore.
What I had to do now was a
and the files are back where they belong. However, the next time I'll
run the update this will happen again? It's not just those files either,
I have a mess to clean up now.
I know that I can use the
-M
flag for update, but there are things Iwant to move around according to new rules in my config.
So the question is: why didn't beet respect the custom rules that I
have setup, or why was the label tag no longer present when I was
running the update?
Here's my full configuration:
Beta Was this translation helpful? Give feedback.
All reactions