Open topic with navigation

# Ingestion

Ingestion brings media into HPE Media Server so that it can be processed. For example, if you ingest video then HPE Media Server must extract the video and audio from the container and decode the streams so that they can be analyzed and transcoded.

Your configuration must include exactly one ingest task. For example:

    [Ingest]
    IngestEngine=LibAvIngest

    [LibAvIngest]
    Type=libav

This example specifies a single ingest task named `LibAvIngest`. The engine used to complete the task is the `libav` ingest engine. Notice that no source file or stream is specified in the configuration. You provide the path of a file or the URL of a stream to HPE Media Server in the `Process` action when you start processing.

Ingest engines produce one or more image tracks and possibly audio tracks:

- Each image track is named `Image_n`, where `n` is a unique number. Tracks are numbered from 1.
- Each audio track is named `Audio_lang_n`, where `lang` is the language and `n` is a unique number. Tracks are numbered from 1. If the language is unknown, each track is named `Audio__n` (note the double underscore), where `n` is a unique number.

For example, if you ingest video from a TV broadcast, HPE Media Server might produce one image track, `Image_1`, and three audio tracks: `Audio_French_1`, `Audio_English_2`, and `Audio_German_3`.

© 2017 Hewlett Packard Enterprise Development LP | Send documentation feedback to HPE Close Send documentation feedback To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a web mail client, and send this email to AutonomyTPFeedback@hpe.com. We appreciate your feedback! Product: Topic Title: Help Topic: Feedback:

_HP_HTML5_bannerTitle.htm