First of all, please remember that English is not my native tongue, I don't even live in an English-speaking country, so what follows will certainly need some reformulation. I am so unsure about this that I avoided entering it in PiratePad at this stage.
Here we go: The MusicBrainz Recordings table is a list of distinct significant audio steps previous to the last mastering. Common examples of these audio steps are editing and mixing. - Distinct because we don't want or need to have two identical rows. - Significant because adding a row should allow to enter specific data (ARs) which could not be entered otherwise. No need to create a Recording for the editing step and one for the mixing step if editing and mixing were the only things which happened to a a given audio; just create one Recording and link both ARs to it. - Previous to the last mastering because mastering is not intended to be specified at Recording level. Mastering may have it's own level in MusicBrainz in the future, but until then all final mastering information will go to release/track level. Mastered audio may be part of the steps which led to a Recording, but mastering should not be the last step. Comments about above: I am not saying a MB Recording is a common world recording, I am not confusing the (common world) object and our representation. Furthermore, I am not suggesting a Recording matches a real world object. I try to avoid this (IMO) false idea by defining the Recordings table as a list rather than trying to define a single Recording row. I thought about replacing "significant" with "relevant", but I felt that "significant" fit better what I meant. BTW, I notice that LordSputnik tried to achieve similar results in his last attempts :-) 2013/5/6 Frederic Da Vitoria <davito...@gmail.com> > OK, that's what I thought. I guess this would be better with a little > explanation in a separate sentence/paragraph. > > > > 2013/5/6 LordSputnik <ben.s...@gmail.com> > >> Frederic Da Vitoria wrote >> > Why "is an abstract grouping of release tracks"? Are you referring to >> the >> > fact that a Recording could be issued in several releases? >> >> Well, a recording is typically used on several tracks, therefore those >> tracks are grouped together by the recording. The recording indicates that >> all tracks in the group are based on the same audio/mix/edit/whatever. >> >> eg. http://musicbrainz.org/recording/1f518811-7cf9-4bdc-a656-0958e130f312is >> a grouping of all the tracks that use that particular version of "Love Me >> Do" as their audio source, before mastering. >> >> >> >> -- >> View this message in context: >> http://musicbrainz.1054305.n4.nabble.com/RFC-STYLE-208-New-Recordings-Guidelines-tp4651054p4652535.html >> Sent from the MusicBrainz - Style mailing list archive at Nabble.com. >> >> _______________________________________________ >> MusicBrainz-style mailing list >> MusicBrainz-style@lists.musicbrainz.org >> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style >> > > > > -- > Frederic Da Vitoria > (davitof) > > Membre de l'April - « promouvoir et défendre le logiciel libre » - > http://www.april.org > -- Frederic Da Vitoria (davitof) Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org
_______________________________________________ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
