3 ms·

I see that they are plugged into musicbrainz[1]. Other than being a CLI, has anyone used this and picard[2]? What's the difference? I've used picard a lot. [1]

• jitl 13y ago
  beets keeps a persistent index of all your music, and manages it as a whole library. It has a bunch of plugins, including a web-based music player, and provides a rich Python API if you want to extend it yourself. You can use beets as a CLI replacement to Picard, but beets offers a lot more to the hacker.
• siddboots 13y ago
  I used to use Picard as "pre-processing" step. I ran any new music through it before I added it to my music player's library. You can use beets in exactly the same way if you want, and it would be a like-for-like CLI replacement. The key difference that Beets brings is to unify the concept of a tagger with the concept of a music library, which made a lot of sense in my mind. In other words, Beets maintains a persistent database of your music collection, which can be kept in sync with Musicbrainz. You can query the database from the command line to get a list of files, and then pipe that list into a music player of choice, or just query the database from a script or web-app and build your own lightweight music player.