Fingerprinting

Our fingerprinting environment provides direct access to media within MassiveMusic's infrastructure. This allows for bulk analysis of media without the media itself leaving the boundaries of our system, as stipulated by licensing arrangements.

Infrastructure

MassiveMusic provide virtual machines from which clients can install software to process our media for their specific requirements. The machines run Debian or Ubuntu Linux and you will be given access to the instances via SSH over a public IP.

Within the environment, access to media is provided by an HTTP endpoint whereby clients can request media by track and format.

We offer a range of different VM spec's, detailed below. The VM plans offer 3 different spec's on either standard discs (SD#) or solid state discs (SSD#), detailed in the below table. When requesting setup of a new VM please reference the below table when raising the request via your Client Success Manager.

Application Interface

Requests to our fingerprinting application look like the following:

http://api.fingerprinting.7digital.net/track/<int>/format/<int>?partnerId=<int>

All parameters are required.

Authentication and Access to Content

Whilst our public media endpoints provide authentication via OAuth 1.0, access to media via the fingerprinting environment does not require signing of requests. The request is instead authenticated via the combination of the originating source IP and partner ID provided on the URL. Requests are only permitted based on a source IP whitelist known ahead of time which we will configure.

Access to content is restricted by a label group whitelist, on a per-partner basis.

Formats & Recommended Fallback Scenarios

We recommend fingerprinting using AAC 320 format, as this format has the highest availability in our catalogue and they provide ample fidelity for most analysis applications.

Whereby our public streaming endpoints will always attempt to return a compatible format in the event we do not have the requested bitrate (most likely in a lower bitrate), the fingerprinting endpoint will not return media for an alternative format automatically. Should you receive an HTTP 404 status code from the endpoint, we recommend you retry the call with an alternative format ID, in the order indicated below: