brainchild

question: support update facility (XUF)

If you wanted a format for representing the associations between file names and metadata, then it would be a cumbersome addition to the application. For single-album invocations of the application, the need is removed to associate various metadata with particular files in the input format. An easier way may be available, however, even for the bulk case. It is unlikely that all available values for barcode or another field in a collection intersect with multiple possible values for any file. Thus,...

I searched the forum for posts made using your handle, and found a good number of hits, but noticed none that address this particular topic. I did find your announcements of the release of the software. Do you suppose the earlier discussions may have been lost in some system-wide event, such as migration to new forum software? Otherwise, do you think you might misremember the forum in which you discussed the specific topic, since you obviously have given the LMS forum quite a bit of contributions?...

At the moment, flactag seems to be the only utility that reads TOC or cue data, computes a MusicBrainz Disc ID, fetches releases data, and applies them to an audio file that captures a full disc. MusicBrainz has developed its own tagging tool, Picard, which is tightly integrated with the design of the service, but the only current support in the project for whole-disc files so far has been as a vaguely-specified item on a long list of possible future features. I have casually tested the tags generated...

Well, the straightforward answer, though it may seem evasive, is that given a choice between two data sets, the minimum necessary information for resolving the choice is at least some of the differences. At the moment, the application displays a static set of fields for each option, such that, in many cases, all fields are identical across the multiple matching releases. A truly complete solution would allow the user to explore the differences. Although such a solution may be more complicated, for...

Well, the straightforward answer, though it may seem evasive, is that given a choice between two data sets, the minimum necessary information for resolving the choice is at least some of differences. At the moment, the application displays a static set of fields for each option, such that, in many cases, all fields are identical across the multiple matching releases. A truly complete solution would allow the user to explore the differences. Although such a solution may be more complicated, for both...

The use case I am considering is attaching a set of basic metadata, needed for selecting an asset from others in a library, to the file that contains the related music. The relevant question is less about viewing the full record from MusicBrainz, and more about having a way to select the best match from a list. If this use case is important, then it may be useful to consider how feasible it is for a user to make this choice manually, based on the way the interactive interface presently is arranged....

I understand your response. A number of small issues come to mind, in case you are considering further enhancements at some time. Consider the following: The error messages are confusing. No method is offered to express rules for automatic resolution, such as country preferences. Often, the information displayed in the interactive session lacks the fields needed to make the correct choice. For example, text would often be the same, or differ only slightly, whereas the important difference would be...