Adrian Sampson

> There's also the issue of artist name versus unique artist id. That's a good point. Yes, the link should probably be used when the server supports it (it need...

Thanks for the list, @ZenithDK! That's very helpful. I'm going to steal "comments" at least for the AURA list. Feel free to add more too.

Thanks, @andrewrk—this is helpful. It might be a good idea to borrow the "artistName", etc., field names as opposed to "artist" to avoid confusion with the links in AURA resources.

> I was wondering about that. Another scenario for multiple track titles I can think of are classical pieces. I admittedly don't have much experience trying to tag classical music....

Thanks for the examples, @tilboerner and @canpolat! I can totally see how these classical works ideally have multiple names. Any guesses as to whether this is something that anyone will...

Thanks for the background @yoasif. In AURA, our "track" objects correspond to recordings in MB's schema. Perhaps this is a good argument for including a `work_mbid` field to make it...

Sorry to revive an old thread, but I'm getting back to working on AURA again. Here's something that I'm having trouble deciding: For tracks, should the "artist" string exist distinctly...

Hi there! Yes, this is actually intended behavior—a consequence of MediaFile's aim to maximize compatibility with a "read any, write all" policy. There's much more discussion in https://github.com/beetbox/beets/issues/350. In short,...

Yes and yes! It would be great to have help with that. It would indeed need to start with an option on MediaFile itself, which would work similarly to the...

Agreed—and it's certainly related to #18 in that there is a trade-off here between flexibility and simplicity. If we stick with something like the status quo, I'd say the sensible...