8.4 DJ mix profile
A release for a DJ mix profile release shall meet the following rules in addition to the rules stipulated in Clause 7:
The
NewReleaseMessage
shall contain exactly oneSoundRecording
, classified as a Primary Resource that is directly referenced from theRelease
via theResourceGroup
element (the "mix").The
NewReleaseMessage
shall contain at least twoSoundRecordings
classified as Secondary Resources that are not directly referenced from theRelease
via theResourceGroup
element (the mix components).These Secondary Resources shall have the
IsSupplemental
flag set totrue
.The mix components shall be referenced, together with a
StartPoint
andDurationUsed
, from the mix by aRelatedResource
of typeHasContentFrom
.Each mix component shall be pointed to from the mix.
Notwithstanding the rules on the identification of Secondary Resources elsewhere in this part of the ERN standard, mix component
SoundRecordings
shall be identified with anISRC
. There is no requirement to identify them with aProprietaryId
.If a record company or distributor wishes to send DJ mixes but does not have access to the data required above, that record company or distributor cannot use the DJ mix profile. Instead, such releases can be communicated using the audio profile (as set out in Clause 6.2).