Difference between revisions of "User:LordSputnik/Recording Style Guidelines"
LordSputnik (talk | contribs) |
LordSputnik (talk | contribs) |
||
Line 33: | Line 33: | ||
===AcoustIDs and ISRCs=== |
===AcoustIDs and ISRCs=== |
||
− | Both of these identifiers can be incorrectly attached to recordings. For this reason, neither AcoustIDs nor ISRCs should be used as the sole reason for merging two recordings. |
+ | Both of these identifiers can be incorrectly attached to recordings. For this reason, neither AcoustIDs nor ISRCs should be used as the sole reason for merging two recordings. |
+ | |||
+ | However, if two recordings do have different ISRCs or multiple, visibly different AcoustID fingerprints, the recordings and identifiers should be carefully examined for correctness before merging. |
||
Before attempting to work with AcoustIDs, please read the [[Guides/AcoustID|AcoustID Guide]]. |
Before attempting to work with AcoustIDs, please read the [[Guides/AcoustID|AcoustID Guide]]. |
Revision as of 22:48, 12 November 2012
Status: This page describes an active style guideline proposal and is not official. |
JIRA ticket STYLE-159 |
Introduction
This proposal is designed to improve the guidelines on merging recordings. It is felt that the current guidelines are too vague, and that they don't cover all cases where recordings might be merged. This proposal seeks to expand these guidelines and make them clearer.
Proposal
Edit http://musicbrainz.org/doc/Style/Recording to change the section "What should and shouldn't be merged together?" to the following.
A recording is intended to represent distinct audio. This means that two recordings should only be merged if the audio that they contain sounds the same. Likewise, when adding a release, a new recording should be made if audio is different from existing recordings. If it isn't clear whether to merge two recordings or not, keep them separate. Where two recordings of the same work are separate for a reason, a meaningful disambiguation should be provided for one or both of the recordings.
Specific Cases
- Don't merge recordings of different performances of a single work. For example, re-recordings, live versions or versions with different lyrics.
- Don't merge two recordings of the same live performance if they were recorded by different people.
- Don't merge recordings which have been mastered in different ways (this includes remasters, if there is an audible, documented difference between recordings).
- Don't merge an original recording with any edited or remixed version of that recording.
- Do merge recordings if the only difference between them is in the length of silence at the beginning or end. This is provided that the silence isn't a significant part of the audio.
- Generally, don't merge recordings if they have conflicting relationships. However, if you're certain that two recordings are the same and relationships are wrong, merge the recordings and correct the relationships.
These cases also apply when selecting recordings for a new release.
AcoustIDs and ISRCs
Both of these identifiers can be incorrectly attached to recordings. For this reason, neither AcoustIDs nor ISRCs should be used as the sole reason for merging two recordings.
However, if two recordings do have different ISRCs or multiple, visibly different AcoustID fingerprints, the recordings and identifiers should be carefully examined for correctness before merging.
Before attempting to work with AcoustIDs, please read the AcoustID Guide.