History:Object Model/Representing Remixes

Thoughts on Representing Remixes in the ObjectModel

Remixes make the layers of the ObjectModel between the ../PerformanceObject and the ../TrackObject a royal pain. Actually remixes would be the only reason to use the ../MixObject at all.

The whole issue can be greatly simplified if a remix is seen as a performance. If we define a remix of being a ../PerformanceObject of its own, this has the following consequences:

• A ../MasterObject belongs to exactly one ../PerformanceObject. Anything that combines multiple performances is a remix and therefore a performance of its own again.
• The ../MixObject can be merged with the ../MasterObject. Defining the boundaries between these two objects was close to impossible.
• Remixes can be modelled by AdvancedRelationships from the ../MasterObjects that get remixed to the ../PerformanceObject they get remixed in.

So things have becom simple again. Good sign.

But there are also negative consequences: If youhave no differentiation between recording and mix and every remix becomes an own performance then you have to relate the performing artists to all of them - which was the reason again to originally build several layers.