Difference between revisions of "Track"

From MusicBrainz Wiki
(To what real-world concept does Track correspond? (Imported from MoinMoin))
((Imported from MoinMoin))
Line 17: Line 17:
  
 
It would be helpful to define what real-world entity the [[MusicBrainz]] term "Track" is intended to model. Sure, it's logically coherent to say "a track is an entry in the track table of the database", but it's also circular. There are clues about the real-world entity in other pages. [[Database Schema/Tracks|DatabaseSchema/Tracks]] says, "broadly speaking, [table] track represents a particular recording of a song, and [table] albumjoin represents the inclusion of that recording on each release it appears on."  [[Release]] implies, but doesn't quite say, that a vinyl LP and a CD can be two different [[Release Event|ReleaseEvent]]<code><nowiki></nowiki></code>s of the same Release, as long as they have the same content and same artists and are derived from the same master recordings.  Thus I'd propose this: "A Track is intended represent a specific audio recording of a  specific musical performance. A particular track is transformed to various recorded data formats for distribution to listeners. If an artist performs a song and makes a master recording, that is one Track. The Track can be transformed to an analogue format on a vinyl LP; and a AIFF digital format on a Compact Disc; and an MP3 digital format in a computer file; it is still one Track. The [[MusicBrainz]] concept of Track also represents related entities: e.g., a block of data stored on media together with music tracks ([[Data Track|DataTrack]]), or an audio recording that is not musical (a spoken word performance)."  That isn't perfect, but it's a start. --[[User:JimDeLaHunt|JimDeLaHunt]] 2008-01-14  
 
It would be helpful to define what real-world entity the [[MusicBrainz]] term "Track" is intended to model. Sure, it's logically coherent to say "a track is an entry in the track table of the database", but it's also circular. There are clues about the real-world entity in other pages. [[Database Schema/Tracks|DatabaseSchema/Tracks]] says, "broadly speaking, [table] track represents a particular recording of a song, and [table] albumjoin represents the inclusion of that recording on each release it appears on."  [[Release]] implies, but doesn't quite say, that a vinyl LP and a CD can be two different [[Release Event|ReleaseEvent]]<code><nowiki></nowiki></code>s of the same Release, as long as they have the same content and same artists and are derived from the same master recordings.  Thus I'd propose this: "A Track is intended represent a specific audio recording of a  specific musical performance. A particular track is transformed to various recorded data formats for distribution to listeners. If an artist performs a song and makes a master recording, that is one Track. The Track can be transformed to an analogue format on a vinyl LP; and a AIFF digital format on a Compact Disc; and an MP3 digital format in a computer file; it is still one Track. The [[MusicBrainz]] concept of Track also represents related entities: e.g., a block of data stored on media together with music tracks ([[Data Track|DataTrack]]), or an audio recording that is not musical (a spoken word performance)."  That isn't perfect, but it's a start. --[[User:JimDeLaHunt|JimDeLaHunt]] 2008-01-14  
 +
<ul><li style="list-style-type:none">Jim, have you read through [http://wiki.musicbrainz.org/ObjectModel/TrackObject http://wiki.musicbrainz.org/ObjectModel/TrackObject] and the associated [http://wiki.musicbrainz.org/ObjectModel http://wiki.musicbrainz.org/ObjectModel] ? (I'd link to the summit 8 NGS schema too, but I can't recall where the fullsize one luks did is stored :P).  -- [[Brian Schweitzer|BrianSchweitzer]] 02:22, 15 January 2008 (UTC)
 +
</ul>
  
 
[[Category:To Be Reviewed]] [[Category:Terminology]] [[Category:Track]]
 
[[Category:To Be Reviewed]] [[Category:Terminology]] [[Category:Track]]

Revision as of 02:22, 15 January 2008

Template:TrackHeader

In MusicBrainzTerminology, a track is an entry in the track table of the database. It usually contains a single song, but there are tracks with more than one song by the same artist, or tracks with more than one song by different artists, not collaborating.

A track is part of a Release and has a TrackTitle. Each track has a unique TrackID.

Examples

Template:FooterHeader

Discussion

It would be helpful to define what real-world entity the MusicBrainz term "Track" is intended to model. Sure, it's logically coherent to say "a track is an entry in the track table of the database", but it's also circular. There are clues about the real-world entity in other pages. DatabaseSchema/Tracks says, "broadly speaking, [table] track represents a particular recording of a song, and [table] albumjoin represents the inclusion of that recording on each release it appears on." Release implies, but doesn't quite say, that a vinyl LP and a CD can be two different ReleaseEvents of the same Release, as long as they have the same content and same artists and are derived from the same master recordings. Thus I'd propose this: "A Track is intended represent a specific audio recording of a specific musical performance. A particular track is transformed to various recorded data formats for distribution to listeners. If an artist performs a song and makes a master recording, that is one Track. The Track can be transformed to an analogue format on a vinyl LP; and a AIFF digital format on a Compact Disc; and an MP3 digital format in a computer file; it is still one Track. The MusicBrainz concept of Track also represents related entities: e.g., a block of data stored on media together with music tracks (DataTrack), or an audio recording that is not musical (a spoken word performance)." That isn't perfect, but it's a start. --JimDeLaHunt 2008-01-14