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
I’m looking into managing my existing audio collection with beets.
When I import (or reimport) my files, I only get to see very little information about what beets is going to do a given file or set of files.
More specifically, I’d basically like to be able to see all changes beets will perform for every file, i.e.:
old path => new path, when moving files is enabled, especially important for me is to know whether it considers something a compilation, audiobook, soundtrack, etc and will move it to the configured folder or just the normal album folder
every change to every tag, whether that is "deleting a comment", "adding a genre tag", or changing from "rock" to "classical rock" or whatever
files ignored in a processed folder, because sometimes they contain notes, album art, lyrics, whatever I or some tool thought would be good to accompany the audio files and I want to know when something is just "left behind" so I can take care of it immediately and don’t have to get back to it later when the context is gone
I tried with -v but that seems to be mainly for diagnostic, in that it spews out a lot of lines about what beets is doing in terms of its logic but doesn’t really increase the amount of information about the points listed above.
Similar with --pretend: it only lists which files would be processed but not what changes it would make to them.
Am I missing some option, plugin, or approach I could be using to get this information?
If it’s not possible yet, could this be added as a feature request? Or bug? Depending on point of view, I guess this could be seen as a bug as having a --noop flag that goes through all the motions without actually performing them could be considered standard for tools that potentially perform lossy operations
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi
I’m looking into managing my existing audio collection with beets.
When I import (or reimport) my files, I only get to see very little information about what beets is going to do a given file or set of files.
More specifically, I’d basically like to be able to see all changes beets will perform for every file, i.e.:
I tried with
-v
but that seems to be mainly for diagnostic, in that it spews out a lot of lines about what beets is doing in terms of its logic but doesn’t really increase the amount of information about the points listed above.Similar with
--pretend
: it only lists which files would be processed but not what changes it would make to them.Am I missing some option, plugin, or approach I could be using to get this information?
If it’s not possible yet, could this be added as a feature request? Or bug? Depending on point of view, I guess this could be seen as a bug as having a
--noop
flag that goes through all the motions without actually performing them could be considered standard for tools that potentially perform lossy operationsThank you very much
henk
Beta Was this translation helpful? Give feedback.
All reactions