Open l-t-k opened 9 years ago
For what purpose?
Beets adds a tremendous amount of options in the postprocessing stage. E.g. plugins to fetch genres from last.fm and a zero and scrub plugin to remove all sorts of unwanted metadata. I would prefer a setup where beets takes full responsibilty of the postprocessing stage. An option to skip the postprocessing tasks done by headphones and simply call in a beet import path/to/download/directory
command would be great.
It would be awfully nice to have Headphones hook into an existing beets database. I don't use the post-processing features at all, because I want there to be one central DB (not to say that I'm not in love with Headphones, I'm just not using it to it's full potential).
+1
+1
+1
Is it possible to force headphones to make use of a certain beets config file that can be modified?