Custom Report¶
A Search Custom Report can be requested by companies that would like to perform an audit on their existing published content and identify any music that exists in those posts. The general procedure for getting a custom report run is:
- Provide Vobile your content. You can send us either:
- Media Files
- Post URLs
- Currently supported platforms include: YouTube, Instagram, X (Twitter), TikTok, Facebook
- Once the content is received, Vobile will run a search on their end. When the search is complete, a csv/excel file will be returned with the results of that search.
Currently, the report contains the following information:
| Field | Description |
|---|---|
| Query File | Information about the file (query) submitted for a search |
| .File | File name or identifier |
| Match Summary | High level information about the query and any matches |
| .Match Identified? | Yes if the query matched to an asset |
| .100% Match? | Yes if the query match % was a 100% match to an identified match |
| .Majors Match? | Yes if the query matched to an identified asset distributed by a Major label |
| .Modified Match? | Yes if the query was a modified match (either via pitch, speed or transposition) to an identified asset |
| Matched Asset | Metadata for the identified asset |
| .ISRC | ISRC of the identified asset |
| .Title | Track title of the identified asset |
| .Subtitle | Track subtitle (if available) of the identified asset |
| .Artist | Artist name of the identified asset |
| .Album Name | Name of the album the identified asset is associated with |
| .Label | Label of the album the identified asset is associated with |
| .Distributor | Distributor of the album the identified asset is associated with |
| .Release Date | Released Date of the album the identified asset is associated with |
| .DSP Links | DSP links for the identified asset |
| Match Details | Match details between the query and the identified asset |
| .Query Match % | Match percentage (query match duration / query duration) of the query that matched to the identified asset |
| .Asset Match % | Match percentage (asset match duration / asset duration) of the identified asset that matched to query |
| .Pitch Difference (cents) | For audio matches only: Difference in pitch (in terms of cents) between the query and the identified asset. For example a value of 0 indicates the pitch of both the query segment and the asset segment is the same. A value of 400 indicates the pitch of the query segment is 400 cents higher (or 4 semitones higher) than the speed of the asset segment |
| .Speed Difference (%) | For audio matches only: Difference in speed (in terms of %) between the query and the identified asset. For example a value of 100 indicates the speed of both the query segment and the asset segment is the same. A value of 125 indicates the speed of the query segment is 25% faster than the speed of the asset segment |
| .Transposition (semitones) | For melody matches only: Pitch transposition (in terms of semitones) between the query and the identified asset. For example a value of 0 indicates the there is no transposition between the query segment and the asset segment. A value of -2 indicates the query segment is 2 semitones lower than the identified asset segment |
| .Match Segments | Timecodes for the match segments identified between the query and the identified asset |