Guide to Content Delivery Specifications and Best Practices

Understanding the contents of this document is crucial as it outlines all specific requirements for our platform, detailing the standards and practices for audio and image submissions, clip generation, release type specifications, and genre tagging. Adhering to these guidelines ensures that your content is correctly ingested, categorised, and represented across the platform.

Accepted Audio Formats

Only FLAC files are accepted, with specific requirements for 16-bit and 24-bit depths across a range of sample rates.

Generated Lossy Formats

Detailed list of lossy formats derived from the provided FLAC files, used for streaming, downloading, and preview clips.

MP3 Clip Previews

Guidelines for generating 30 and 60-second clips, including default and custom start times.

Image Delivery Specifications

Requirements for JPEG format images, including size and aspect ratio.

Release Type Specifications

Supported values for release types, ensuring proper categorization and management.

Genre Submission Guidelines

Best practices for genre tagging to enhance searchability and accurate representation of music.

Audio Delivery Specifications

MassiveMusic supports the ingestion of FLAC files with the following bit depths and sample rates. Any content that does not conform to these specifications will not pass our validation rules and will be rejected during ingestion, preventing it from going live.

🚧

MassiveMusic only accepts FLAC as a source format. Therefore, any release delivered in WAV or other lossless codec will be rejected.

Supported Delivery Audio Formats

• FLAC 16-bit

  • Supported sample rates: 44.1kHz, 48kHz
  • Usage: These files are used to generate all of our lossy formats (listed below) for delivery to partner platforms. If an HD agreement is in place, they are also available for download.

• FLAC 24-bit

  • Supported sample rates: 44.1kHz, 48kHz, 88.2kHz, 96kHz, 176.4kHz, 192kHz
  • Usage: These files are used to generate all of our lossy formats (listed below) for delivery to partner platforms. If an HD agreement is in place, they are also available for download.

🚧

Please deliver your highest available quality assets.

Generated Lossy Formats

From the delivered FLAC files, we generate the following lossy formats for delivery to our diverse range of clients. These formats cater to download, streaming, and preview clip services. We will only provide the appropriate format to a client when the necessary agreement and approvals are in place and the relevant commercial model type is provided.

Streaming Formats

• AAC 320 kbps
• AAC 160 kbps
• AAC 64 kbps
• OGA VBR q0
• OGA VBR q2
• OGA VBR q5
• MP3 128 - 30sec clip
• MP3 128 - 60sec clip
• MP3 320 - 30sec clip
• MP3 320 - 60sec clip

Download Formats

• MP3 320 kbps
• FLAC 16-bit 44.1kHz
• FLAC 16-bit 48kHz
• FLAC 24-bit 44.1kHz
• FLAC 24-bit 48kHz
• FLAC 24-bit 88.2kHz
• FLAC 24-bit 96kHz
• FLAC 24-bit 176.4kHz
• FLAC 24-bit 192kHz

Generating MP3 Clip Previews

From the delivered FLAC files, MP3 clips are generated for use on licensed services with the following specifications:

• 30-second clips: Available in 128 kbps and 320 kbps.
• 60-second clips: Available in 128 kbps and 320 kbps.

Default Clip Start Times

• If no start time is provided, clips will default to starting 43 seconds from the beginning of the track.
• A start time of 0 seconds will generate a clip from the very start of the song.
• When a track is under 30s or 60s, we will utilise the whole track as the clip.

Updating Clips

To update the start time of a clip, a full asset redelivery with the updated start time specified in the <StartPoint> must be provided. We will then transcode the clip from the updated start point for distribution to partner services.

Usage of Clips

Clips are utilised by various clients for different purposes ranging from preview clips on a download service to embeds within social media platforms. Services may stream clips directly from our platform or host them on their own platform; this will be stipulated within the licensing and approvals process.

Image Delivery Specifications

Supported Image Format

• JPEG Only: JPEG format is required; all other formats will be rejected at ingestion, resulting in the release not going live on the platform.

Image Sizing

• The minimum size requirement is 1400 pixels by 1400 pixels. Any artwork delivered smaller than this will be rejected, resulting in the release not going live on the platform.
• Please provide your highest quality artwork up to 5000 pixels by 5000 pixels. We work with several partners who display artwork on HD screens, and to ensure optimal results, we will offer these services artwork in a larger size where available.
• Images must be square. Non-square images will be automatically resized, which may lead to distortion.

Updating Images

To update an image, add the new image resource to the delivery and update the corresponding information in the DDEX message. As the artwork is embedded into some of the audio assets, please include the FLACs within the redelivery.

Release Type Specifications

Supported <ReleaseType> Values

• Single: Indicates that the release is a single track, typically released on its own rather than as part of a larger album.
• Album: Specifies that the release is a full album, consisting of multiple tracks.
• EP: Denotes that the release is an EP (Extended Play), which is longer than a single but not long enough to be considered a full album.
• TrackRelease: Used when a particular track is being highlighted from an album or EP, often for promotional purposes.

Single
Album
EP
TrackRelease

Note on Unsupported Release Types

• UserDefined: Not supported. Our platform does not support the <ReleaseType> value UserDefined.
• Boxsets: The use of Boxsets, especially those containing multiple ICPNs, is not supported due to the complexities involved in managing these types of releases.
• Audio Book: Not supported.

🚧

Any attempts to submit releases categorized under these types will lead to rejections during the content ingestion process. This policy ensures that all content is consistent and reliably managed across our services.

Genre

Genres help classify and organise music, making it easier for users to find the content they are looking for. While the Genre field is free-form text, allowing you to categorise your music in a way that best represents its unique style, we have some best practice guidelines to help ensure your music gets optimal placement on services that utilise genre for search and grouping functionality.

Best Practices for Genre Submission

• Be Specific: Use detailed and specific genre terms to accurately describe your music. For example, "Break Beat Jungle" is more specific and informative than just "D&B."
• Avoid Comma-Separated Lists: Ensure each genre is submitted as a single term rather than a list of genres. For instance, instead of "House, Techno" use "Tech House" if it best describes the fusion of styles.
• Choose the Most Relevant Genre: Avoid using slashes (/) to list multiple genres in a single entry. This can lead to confusion and poor categorisation. Instead, select the genre that best fits the primary style of your music. For example, rather than "Rock/Jazz," determine which genre most accurately represents the track or release and use that single term.
• Consistency: Be consistent in your genre tagging across similar releases to help with categorisation and searchability.

By following these guidelines, you can help ensure that your music is accurately represented and easily discoverable across our platform and partner services.