AM Toolkit Programs (binaries)

The Audible Magic (AM) Toolkit contains three command-line programs (identify, analyze, and identifyStream) that can determine the presence of audio and video material that has previously been registered with AM.

identify:

accepts an input media file and produces JSON output including a list of any matches that were made between the media file and entries in Audible Magic’s databases.

Command-line usage:

.\identify -c configFile -i inputFile -e assetID

Arguments:

-i inputFile (a media file, or an output file from the analyze program. Preferably expressed as a relative or absolute path to a local file

-c configFile (relative or absolute path to an SDK configuration file)

-e unknownAssetID (caller-defined identifier; returned in the response as unknownAssetID.


analyze:

separates the generation of the fingerprints from the process of posting to Audible Magic's Databases. This "analysis" file can later be fed to identify for identification

Command-line usage

.\analyze -c configFile -i inputMediaFile -o outputFile -e assetID

Arguments:

        -i inputMediaFile (an audio or video file. Preferably expressed as a relative or

                absolute path to a local file, but can also be a URL beginning with "http://" or "https://".

        -o outputFile (fingerprint package, to be identified later by the 'identify' executable)

        -c configFile (relative or absolute path to an SDK configuration file)

        -e unknownAssetID (caller-defined identifier; returned in the response as unknownAssetID)


identifyStream:

accepts an input of real-time stream URL and returns a JSON output and log files with match information

Command-line usage

.\identifyStream -c configFile -i streamURL -e streamID -O outputDirectory

Arguments:

-i streamURL (URL of a live stream, beginning with http://, https://, rtmp://, or rtmps://, etc.)

-c configFile (relative or absolute path to an SDK configuration file)

-e streamID: Customer-specified string that uniquely and fully identifies the stream in the customer's systems.

        -O outputDirectory (where JSON files will be written)