we are discussing the expected behavior of the set_fields configuration, which uses the
set_fields configuration file block and the
--set command line option.
Question: Should fields be set on the imported album only, or also on each individual track?
In the current implementation, fields are set on the imported album only. Hence
beet list won’t let you filter for those fields unless you provide the
-a flag. With
-a, however, you will see a list of albums instead of individual tracks.
There are some discussions on the board (e.g. here or here or here) and on the internet (e.g. here) where people expect that fields are also set on each individual track. In particular, this would imply that the fields are also written to the metadata of the track files instead of only beets’ database.
Main question: Would changing the implementation from album in database only to write each individual track file break your setup?
Please share your thoughts.
PS: Also posted on github.