Well, the answer is about the same as for other questions along the lines of “why doesn’t beets to worthwhile thing X yet?” In a word: effort.
Everything, even the most valuable-seeming feature, takes work—and, for beets, there are hundreds (maybe thousands?) of worthwhile tasks one could take on. So, we do our best, and progress does continue, but each individual worthwhile task actually has a fairly low probability of being at the front of the queue. A more specific answer is that adding fields is a little more complicated than it might seem at first glance. For the recent composer fields, for example, the PR’s author had to interface with a whole new ID3 frame type to store the data in MP3s. And for the artist country and dates, there’s a nontrivial matter of finding exactly where to extract these from the MusicBrainz API responses reliably. I hope that helps! Adrian > On Dec 29, 2016, at 6:03 AM, Bearcat Şándor <[email protected]> wrote: > > I don't get it. In the past few weeks we've had additions to the codebase to > add composer and another to add artist country and artist start/end date. > > If Beets is designed to be for we OCD music types, why not just make beets > grab EVERYTHING with an option to ignore fields that one doesn't care about? > > I want it all baby!! > > > > -- > You received this message because you are subscribed to the Google Groups > "beets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "beets" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
