Custom Files

Example of JSON result: Audio & Video buckets of custom files with Audio & Video Recognition, Broadcast Monitoring, Hybrid Recognition and Offline Recognition projects.

JSON structure
{ 
        "status": {
            "msg": "Success",
            "code": 0,
            "version": "1.0"
        },
        "metadata": {
            "timestamp_utc": "2015-07-27 12:56:46",
            "custom_files": [
                {
                    "bucket_id": "51",
                    "title": "You are beautiful",
                    "artist": "James",
                    "acrid": "5343bc191634b042622bf474ed46121a",
                    "audio_id": "3",
                }
            ]
        },
        "result_type": 0 
}
Metadata fields
Name
Description
custom_files
Custom uploaded file fields
arcid
ACRCloud unique identifier
title
File name
audio_id
User defined identifier
play_offset_ms
Position of the recognition in the file if the file was playing (millisecond)
*db_begin_time_offset_ms
Position of beginning of the recognition on database file (millisecond)
*db_end_time_offset_ms
Position of end of the recognition on database file (millisecond)
*sample_begin_time_offset_ms
Position of beginning of the recognition in sample file sent by SDK/API (millisecond)
*sample_end_time_offset_ms
Position of end of the recognition in sample file sent by SDK/API (millisecond)
* fields are visible in Broadcast Monitoring service only, if you want to use these fields in recognition service, please contact us.
Please note: Only Title, ARCID, Audio_ID are required fields.

Metadata - Previous

Music (Broadcast Monitoring with Broadcast Database)

Next - Metadata

Live Channels

Last updated 8 months ago

Name	Description
custom_files	Custom uploaded file fields
arcid	ACRCloud unique identifier
title	File name
audio_id	User defined identifier
play_offset_ms	Position of the recognition in the file if the file was playing (millisecond)
*db_begin_time_offset_ms	Position of beginning of the recognition on database file (millisecond)
*db_end_time_offset_ms	Position of end of the recognition on database file (millisecond)
*sample_begin_time_offset_ms	Position of beginning of the recognition in sample file sent by SDK/API (millisecond)
*sample_end_time_offset_ms	Position of end of the recognition in sample file sent by SDK/API (millisecond)