Salesforce

Video ingestion requirements

« Go Back
Information
Video ingestion requirements
000006907
Public
Product Selection
aiWare - aiWare
Article Details

In Data Center, you can ingest data for various jobs. When video is ingested, it may be chunked, transcoded, tagged, indexed, thumbnailed, and/or subjected to other "normalizing" operations so that the system can operate on all ingested files with the same expectations, no matter where a file originally came from. In aiWARE, a file can undergo cognitive processing only if it has first been ingested.

Stream URL requirements

Providing a valid stream URL that Veritone can pull from is essential for video ingestion. The URL must:

  • Be a direct stream URL or IP address (e.g., SRT, RTMP, HLS, or other supported protocols).
  • Point to a consistent and static location. Dynamic or temporary URLs are not supported.
  • Avoid redirecting to media player pages or other non-direct sources.

Supported transport protocols and streaming formats

Transport protocols:

  • SRT (Secure Reliable Transport) 
  • RTMP (Real-Time Messaging Protocol)
  • RTSP (Real-Time Streaming Protocol)
  • HTTP (HyperText Transport Protocol - commonly used for adaptive streaming protocols like HLS)

Streaming format:

  • HLS

    • Supports MPEG-TS 

  • Encapsulation formats for transport protocols

    • MPEG-TS 

    • Raw Streams H.264

Ingestion requirements

Video ingestion format requirements

HLS or RTMP stream

Video stream format and encoding requirements

Display resolution

480p minimum to 1080p maximum

Aspect ratio 

16:9

Video frame rate

15 fps minimum-60 fps maximum

Video codec

H.264 (AVC) 

Audio codec

AAC or MP3

Audio bit depth (bits per sample)

16-32 bit

Audio sample rate

44.1-48kHz

Audio channels

Stereo or mono

File format (container), if applicable

mp4

Stream bitrate

Variable - 1 Mbps minimum - 10 Mbps maximum

Direct streams

If you plan to ingest via direct stream URL, provide the direct URL or IP address/port to your live video feed. Important: URLs to media player pages on websites are not sufficient. We require the actual stream URL that Veritone can directly connect to for ingesting your broadcast.

Supported audio formats and quality

  • Audio must be in MP3 (minimum bitrate: 128 kbps) or AAC (minimum bitrate: 64 kbps).
  • Ensure the stream maintains consistent quality for accurate transcription.

Ad content

If using a public stream URL, the stream must not include pre-roll or mid-roll ads.

[Note]This is not the case with a direct feed from master control or a similar direct feed.

It should be an exact copy of your Over-the-Air (OTA) program feed, reflecting live broadcast content.

Consistent and static URL

The stream URL must remain constant and not change. Dynamic or temporary URLs are not supported.

Alternative ingestion option

The closed file ingestion method may be used. 

[Note]This option requires approval before proceeding due to technical limitations and capabilities. Contact your sales account executive for more information.

If your video is compatible with FFMPEG, review the latest documentation. To facilitate this directly:

  1. Process the video in time sliced chunks (must be 5-15 minutes in length).
  2. Append metadata tags to include time correlated start time and end time and program info.
  3. Upload the chunks to an Amazon S3 bucket.
  4. Provide Veritone with the Amazon S3 credentials.
  5. Veritone will copy the files from Amazon S3 and process them.
Additional Technical Documentation Information
Properties
3/13/2025 6:16 PM
3/17/2025 5:38 PM
3/17/2025 5:38 PM
Documentation
Documentation
000006907
Translation Information
English

Powered by