Frequently Asked Questions
- Google Play
- iTunes/Apple Music
- All Merlin reports
Delivery time to most major DSPs is within a few hours / same day.
Our distribution system is fully hosted on a cloud infrastructure, and benefits from their integrated security, and furthermore follow best practices for security.
Please see PayPal’s fees here — note that we use the newer API (left column).
We have a support team that works with you. Response time is generally within 24 hours of email.
Yes, we process mechanical reporting with our platform in the following ways:
- Indicate the mechanical amounts due on each payee statement
- Provide a master mechanical report to you showing all amounts due by each payee (but not the splits of those dues to the writers/publishers)
- All distribution workflows in one platform which saves time & money.
- Create trust & transparency with end to end visibility of your reported earnings and daily trending in one unified dashboard. Our enterprise-level permission-based software allows you to share only what you want with your team, stakeholders and artists.
Why does it show live on the UI when it is not live yet on YT, Yandex, iMusica and Nuuday and Shazam?
Live on the UI for the following DSPs YouTube, Yandex, iMusica, Nuuday and Shazam simply means that they have confirmed ingestion.
This is just how Shazam works: they don’t respect release dates. But you can’t play the song yet… If you don’t want it to appear at all before the release date, you must not send it to Shazam before that date.
Yes. Email us with your pre-order requests.
For all DSPs that provide a method to obtain a URI or a weblink, we retrieve those and display them in your files section.
Can you offer any guidance for releasing singles, where those singles will also be the same version that will appear on an EP or Album coming later down the line?
There is no issue with releasing singles that will later be included on an EP or an album at a later date except when distributed to Facebook (see below). The single, the EP, or album will share tracks with the same ISRC numbers but each product will each have a unique UPC number.
What do I do when delivering to Facebook?
The issue that arises delivering to Facebook/Instagram involves the sale start dates. Facebook has this quirky process where for deliveries that include the same ISRC, they will take the data from the latest fingerprint batch into account.
If the same ISRC that is already live is delivered again with a new EP or album, the start date will be overwritten to that new EP or album. Facebook uses the date of the last release delivered.
If you need the ISRC on a previous release to be live, you need to redeliver THAT release again. For example, if you first deliver the single to be released to a specific date and then you release the EP with another future date. The single’s start date will be overwritten and will be released using the date of the EP (the last delivered ISRC).
To fix this you need to send a redelivery of the single that you want live.
Can they co-exist on the streaming services when they share the same track ISRC ?
Yes they can co-exist on DSPs when they share the same track ISRC.
Due to new YouTube requirements, there are some preconditions for being able to use our deal for Content ID. All of these requirements come from YouTube, so there is nothing that we can do about it. Furthermore, it jeopardizes our royalty rate when these requirements are not followed, so please note that we cannot allow any errors here. Here are the requirements:
- If you distribute to YT CID, then you MUST also distribute to YT M at the same time. There can never be a case of a release/asset on YT CID without it ALSO being on YT M. So also: do not allow takedowns from CID without also doing a takedown from M. Note: it is OK to distribute to M and not to CID.
- Furthermore, the territorial rights MUST be exactly the same, or, at the very least, YT M must NOT have fewer territories than CID.
In short: YouTube wants to ensure that YT M NEVER has less content or rights than YT CID.As a result of issues in the past, we need to validate that your UI will enforce this behavior so that your users don’t make a mistake. Until then, distribution to YT CID is blocked. If you need to send something to CID before we can validate your UI, please send an email to email@example.com and we will send the item to CID.
You may require your Spotify URI before the release date if you are looking to push for playlist inclusions or prepare certain buy links.
To get the URI, please send us the below information to firstname.lastname@example.org.
- Account Name [Label Name]
- Catalog #
- UPC Code
- ISRC Code [if requesting a URI for a specific track]
Important: Please ensure your release has been delivered to Spotify before requesting this.
When delivering audio to YouTube, an Art Track will be automatically generated.
The audio Sound Legends delivers to YouTube generates an Art Track which consists of the sound recording, the album art, and metadata about the recording, such as its title and artist name.
The Art Track will be automatically delivered to:
A) the Artist – Topic channel or
B) the Various Artists – Topic channel
You are able to choose a release date for either as soon as possible or on a specific date in the future.
When distributing a release, you are able to choose a release date for either as soon as possible or on a specific date in the future.
The Release start date is the date you would like the release to go live on the DSPs. There are two options:
1. As soon as possible
The soonest release possible primarily depends on the response time from each service. Typically this requires anywhere from a few hours up to a few days. Each service has their own requirements and will make the release public independent of any other service.
2. On a specific date
On a specific date allows you to choose any date in the future. By choosing this option your release appears publicly on all services at the same time. For unreleased material this helps control the rollout for streamlined promotion.
To ensure that the release does not go live before your chosen specific date, follow the below instructions:
A) The release should be marked as NOT previously released in your Revelator account and no previous release date should be chosen.
B) When distributing the release, a future release start date needs to be chosen to prevent the release from going live upon delivery. Click the button “On a specific date” and select your desired release date.
Sometimes you need a little help. Don’t worry… we’re here for you.
Have a question? Our team will help you find answers.
Simply click the chat button on the bottom right of the screen or fill out our contact form and get the support that you need. Make sure to include the information below for prompt assistance.
- Account Name [label name]
- Clear description including:
- UPC and/or ISRC code
- Artist Name
- Release Name
- User Steps In Order to Reproduce the Issue if needed
- Screenshots when applicable
Please start a new conversation for each unique issue or request.
We may need to reproduce the issue to troubleshoot or investigate for you.
You can use Sound Legends to distribute or deliver your music to nearly all popular stores & services worldwide. You keep 100% of your profits.
Sound Legends integrates with a wide range of digital music services, platforms and exchanges for asset delivery and sales data processing.
Sound Legends supports content distribution and sales reporting from an extensive and growing list of existing digital services and platforms. Customers who do not have direct deals in place can distribute their releases to these online stores and services. As well, Sound Legends can receive and manage the collection, processing and analysis of consumption data and financial reporting.
Currently, we integrate with the following DSPs:
- Facebook Audio Library
- Facebook Rights Manager
- Google Play
- iTunes/Apple Music
- Music Time
- Napster / Rhapsody
- YouTube Content ID
- YouTube Music