You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of a feature request. I would like set_fields option to be able to add things at the track level, rather than just the album level. Without it, I have to run a second modify command after import to query for tracks where the field is NOT set to yes or no, and set it to yes if so.
Running this command in verbose (-vv) mode:
$ beet -vv import "some_dir"
Led to this problem:
(There isn't a problem in the output).
Here's a link to the music files that trigger the bug (if relevant): N/A
Setup
OS: Gentoo Linux
Python version: 3.5.4
beets version: 1.4.6
Turning off plugins made problem go away (yes/no): n/a
Hi! We've just been discussing exactly this issue in #2797. I agree that this is probably the right resolution to the problem described there, as well as the more general issue you've brought up in this context.
Problem
This is more of a feature request. I would like set_fields option to be able to add things at the track level, rather than just the album level. Without it, I have to run a second modify command after import to query for tracks where the field is NOT set to yes or no, and set it to yes if so.
Running this command in verbose (
-vv
) mode:$ beet -vv import "some_dir"
Led to this problem:
Here's a link to the music files that trigger the bug (if relevant): N/A
Setup
My configuration (output of
beet config
) is:The text was updated successfully, but these errors were encountered: