Previews are special resources that are used to provide users with a track to sample – with the hope that the consumer will buy (or otherwise pay for the) full track or album. In many cases previews are short snippets from the "full" track.
Signalling that an album has preview binaries
To signal that a ten-track album has one preview resource for each of the ten tracks would mean that the Release contains:
- Ten Sound Recording composites, each with
TechnicalSoundRecordingDetailscomposite for the "full" binary and
TechnicalSoundRecordingDetailscomposite for the preview binary and
- One image resources (the cover art), with a
Two ways to communicate preview binaries
NewReleaseMessage supports to means to furnish a DSP with preview binaries: Either the label sends preview binaries as part of their release delivery (in which case the delivery comprises 21 binaries), or the label communicates instructions for the DSP to generate them itself (in which case the delivery comprises 11 binaries).
The two XML snippets on the right show
TechnicalSoundRecordingDetails for an audio preview and
TechnicalVideoDetails for a video preview. The fact that the record company has created the snippets is indicated by the inclusion of
<ExpressionType>Informative</ExpressionType> (instead of
Deals for Previews
While the DSP is expected to regognise preview binaries by the presence of the
<IsPreview>true</IsPreview> flag, the record company still needs to provide relevant deal information. This can be done by the relevant tags in
DealTerms such as:
For avoidance of doubt: the same rules for communicating multple resources/binaries also apply to communicating multiple binaries for one resource, whether they are previews or not.