Most metadata fields can be overwritten on a per track basis in the config yaml. However, album art cannot.

while a rare case -- there are times where having the front/back of a vinyl rip as the album art could be helpful. There is no real reason that album art should be handled differently.

the -f CLI flag doesn't exist anymore. Re-add and make it so metadata can be completely overwritten.

Album art in the metadata can significantly impact the size of a track's file.

PIL can be used to resize and convert filetype. Being able to set this in config would be excellent:

album art:
    dimensions: 500x500 # pixels
    target filetype: jpg
    location: some_file.png

Note: for bandcamp this isn't important because they automatically replace metadata on upload.

Right now adt will overwrite existing files' metadata. This isn't ideal.

• audio files should be copied to a new deployment directory
• deployment directory should be named: album-code_album-name
• audio file name should be: album-code_track-number_artist-name_track-name

it is unclear which fields are required and which are not. It might be ideal to make a minimal set of fields required (or none at all).

Implementation wise, it might be good to use a model (Pydantic or Dataclass) to represent the config. This could also be used to generate an example config through CLI (to show required vs non-required fields)?