Choose the Rate of Ingestion

Some analysis operations are resource-intensive and cannot process video frames as quickly as they can be ingested. For this reason, and because processing every frame does not necessarily improve detection performance or capture rates, analysis tasks usually do not process every frame of a video.

The interval at which an analysis task selects frames to be analyzed is called the sample interval. For example, if a task has a sample interval of 125 milliseconds then any two frames analyzed by the task will be separated by at least 125 milliseconds. This means that at most eight frames are analyzed for every second of video.

Media Server uses default sample intervals that have been chosen to produce good accuracy in most cases. HPE recommends using the default values but you can increase or decrease the sample interval for an analysis task by setting the SampleInterval configuration parameter.

If you are processing a live stream, Media Server is ingesting video at a fixed rate and must keep up with the video. This means that if your Media Server does not have sufficient resources, it will not be able to process all of the frames that have been selected for analysis. In this case, your analysis tasks will drop some of the frames that were selected to ensure that analysis keeps up with the video. This might cause a reduction in accuracy. When you are processing a live stream, you cannot change the rate at which video is ingested, so to prevent frames being dropped the only solution is to increase the resources (CPU cores) available to Media Server.

If you are processing video that is ingested from a file, you can choose the rate at which video is ingested. The rate at which Media Server ingests video is controlled by the IngestRate configuration parameter. You can set this parameter to one of the following values:

Tip: The sample interval and rate of ingestion have no effect on the speed at which a video frame is analyzed. The speed of analysis is determined by the resources available to Media Server. If your server has sufficient resources (CPU cores) and an analysis task supports it, you can set the NumParallel parameter. This specifies the number of video frames for an analysis task to process concurrently. Processing frames in parallel can increase the total number of frames processed in a certain time. Depending on the ingest rate, this will either result in fewer frames being dropped or result in the file being processed in less time.

The following table summarizes the combinations that are available for IngestRate and SampleInterval:

Options Default SampleInterval SampleInterval = 0

IngestRate=1

HPE recommends using IngestRate=1 and the default sample intervals for processing live streams.

Media Server does not attempt to process every frame, but selects frames for analysis based on the specified sample interval. The default sample interval should provide good accuracy in most cases. However, Media Server might drop sampled frames to ensure that analysis occurs at normal (playback) speed.

If your Media Server does not have sufficient resources, it will not be able to analyze all of the frames that are sampled and will drop frames, causing a reduction in accuracy.

Media Server attempts to analyze every frame but frames are dropped if the analysis tasks you have configured cannot process the frames at normal (playback) speed.

HPE does not recommend the combination of IngestRate=1 and SampleInterval=0 in any scenario because Media Server is likely to drop large numbers of frames.

IngestRate=0

HPE recommends IngestRate=0 and the default sample intervals for processing video from files.

Media Server does not attempt to process every frame, but selects frames for analysis based on the specified sample interval. The default sample interval should provide good accuracy in most cases. If analysis is slow, Media Server ingests the file at a slower rate and does not drop frames.

If your Media Server does not have sufficient resources, it will take longer to process the file, but accuracy will be maintained.

Ensures that all frames are analyzed and no frames are dropped.

HPE does not recommend the combination of IngestRate=0 and SampleInterval=0 because in most cases this will take much longer and may not result in a large increase in accuracy.

Use this mode only if it is critical that every frame is analyzed.


_HP_HTML5_bannerTitle.htm