Difference between revisions of "User:LordSputnik/Recording Style Guidelines"

From MusicBrainz Wiki
Line 18: Line 18:
 
Edit http://musicbrainz.org/doc/Style/Recording to change the section "What should and shouldn't be merged together?" to the following.
 
Edit http://musicbrainz.org/doc/Style/Recording to change the section "What should and shouldn't be merged together?" to the following.
  
==What should and shouldn't share recordings?==
+
==When should recordings be shared?==
A recording is intended to represent distinct audio. This means that generally two tracks should only share a recording if the audio that they contain sounds the same. 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.
+
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===
 
===Specific Cases===
#Tracks containing different performances of a single work should each use a separate recording, since each performance will result in distinct audio.
+
#Don't merge recordings of different performances of a single work. For example, re-recordings, live versions or versions with different lyrics.
#Releases of live performances that are recorded by different recording devices should each use a separate set of recordings.
+
#Don't merge two recordings of the same live performance if they were recorded by different people or if they sound different.
#Versions of a release that are mastered in audibly different ways should use separate recordings.  
+
#Don't merge recordings which have been mastered in different ways (this includes remasters, if there is an audible difference between recordings).
#If audio restoration is used to create remastered audio from an earlier recording, a track containing the remastered audio should use a recording specific to that remaster.
+
#Don't merge an original recording with any edited or remixed version of that recording.
#A track containing edited or remixed audio should always use a recording specific to that particular edit or remix.
+
#Don't merge recordings which have different numbers of audio channels. For example, a mono recording and a stereo recording.
#Tracks which contain different numbers of audio channels should always use separate recordings. For example, a mono recording and a stereo recording should never be merged.
+
#Don't merge recordings if they have conflicting relationships. If you're sure two recordings are the same and the relationships are wrong, correct them before you merge.
#If a track begins or ends in silence and a second track changes the length of the silence, but is otherwise identical, these two tracks should share a recording, so long as the silence isn't a significant part of the audio.
+
#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.
 +
 
 +
 
 +
These cases also apply when selecting recordings for a new release.
  
 
===AcoustIDs and ISRCs===
 
===AcoustIDs and ISRCs===

Revision as of 22:14, 8 November 2012


Status: This page describes an active style guideline proposal and is not official.



Proposal number: RFC-Unassigned
Champion: LordSputnik
Current status: RFC
Initial Discussion


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.

When should recordings be shared?

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

  1. Don't merge recordings of different performances of a single work. For example, re-recordings, live versions or versions with different lyrics.
  2. Don't merge two recordings of the same live performance if they were recorded by different people or if they sound different.
  3. Don't merge recordings which have been mastered in different ways (this includes remasters, if there is an audible difference between recordings).
  4. Don't merge an original recording with any edited or remixed version of that recording.
  5. Don't merge recordings which have different numbers of audio channels. For example, a mono recording and a stereo recording.
  6. Don't merge recordings if they have conflicting relationships. If you're sure two recordings are the same and the relationships are wrong, correct them before you merge.
  7. 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.


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. Different AcoustID fingerprints and ISRCs may be used as a reason for not merging, but bear in mind that they can sometimes be wrong.

Before attempting to work with AcoustIDs, please read the AcoustID Guide.