History:Object Model/Track Object
The Track Object
This page describes the track object and its role in the ObjectModel.
Definition
A track is the result of the whole music production process that started with the idea described in the ../SongObject. The track is defined by a name and a position on a ../ReleaseObject (e.g. a track number on a CD) on a release medium. The ../TrackObject defines a single audible object on a specific ../ReleaseObject.
The following is DonRedman's point of view and not necessarily shared by others
- Note that the track object itself does not contain any information about audible data. Instead the track object belongs to exactly one ../MasterObject. It is this master that defines the audio that is stored on the track. At the same time a track object belongs to exactly one ../ReleaseObject. That means that with this model, we will never merge tracks (except when merging releases). We will only merge higher level objects like the ../MasterObject, the ../PerformanceObject, or the ../CompositionObject. The ..TrackObject itself just contains this info: * The related (single) ../MasterObject * appears on (this ../DiscObject of) this related (single) ../ReleaseObject * at position [propperty] * under the TrackTitle [propoerty or relation to a ../TrackTitleObject?] * attributed to the artist of this (single) ../AttributedName.
Fuchs, however wrote:
- As long as the audio data and the title, artist, and other metadata of two tracks are 100% identical they belong to the same ../TrackObject.
Which suggests that he has a different concept of a track.
Boundaries
Boundaries to the MasterObject
The master that isn't directly accessible by the public needs to be used to create the track on a release. When a piece of music can be baught and listened to, it is a track on a release.
Boundaries at the bottom
There are no boundaries at the bottom. Each ../TrackObject is unique in audio and meta-data.
Relationships
Relationships to the MasterObject
- A ../TrackObject has exactly 1 ../MasterObject
- The master represents the audio data that the track contains, so there can be only one master for each track.
Relationships to the ReleaseObject
- A ../TrackObject belongs to exactly 1 ../ReleaseObject
- The track is defined by its position on a unique release.