Buffering in the Stream Buffer Engine

Microsoft DirectShow 9.0

Buffering in the Stream Buffer Engine

This topic applies to Windows XP Service Pack 1 or later.

The Stream Buffer Sink filter stores the data that it captures in temporary backing files. By default, it uses six files, each holding 5 minutes of data, for a total buffer of 30 minutes. (The default settings can be changed through the IStreamBufferConfigure interface.)

Once the buffer limit is reached, the Stream Buffer Sink filter begins to delete files, starting from the oldest file. If a source graph is currently reading from that file, the sink filter deletes the next oldest file instead, creating a "time hole" in the playback. Time holes are caused when the source graph pauses for too long or seeks backward to the beginning of the buffer.

When the Stream Buffer Source filter reaches the gap where the file was deleted, it moves to the next file. However, because the presentation times haven't changed, the last frame from the older file is displayed for the duration of the deleted file. The video therefore appears to freeze for that period of time. To avoid this, the source graph should seek forward to the next valid data.

The Stream Buffer Engine sends several graph events to warn the application when files have gone stale or are about to go stale:

• STREAMBUFFER_EC_CONTENT_BECOMING_STALE. Sent when the source filter lags behind the sink filter by more than a preset number of files. See IStreamBufferConfigure::GetBackingFileCount.
• STREAMBUFFER_EC_STALE_DATA_READ. Sent when the source filter is reading a file that has been marked for deletion.
• STREAMBUFFER_EC_STALE_FILE_DELETED. Sent when a file is deleted.
• STREAMBUFFER_EC_TIMEHOLE. Sent when the source filter reaches a time hole. The event parameters indicate the time and size of the hole.

For more information, see Stream Buffer Engine Event Codes.

The content in a recording never goes stale. For more information, see Creating Stream Buffer Recordings.