CSSTREAM_HEADER_OPTIONSF Values (Windows Embedded CE 6.0)
1/6/2010
The following table shows macro values that are used to describe attributes of a data stream. These values are used in the OptionsFlags member of the CSSTREAM_HEADER structure.
Value | Description |
---|---|
CSSTREAM_HEADER_OPTIONSF_DATADISCONTINUITY |
Specifies that there has been a discontinuity in the data stream before the data contained in this packet. This implies that the filter may need to reset its internal state before processing the data. No actual data buffer need be attached. |
CSSTREAM_HEADER_OPTIONSF_DURATIONVALID |
The value for CSSTREAM_HEADER.Duration is valid. |
CSSTREAM_HEADER_OPTIONSF_ENDOFSTREAM |
Indicates that this frame represents the end of the data stream. This can then be used to generate an end-of-stream event. |
CSSTREAM_HEADER_OPTIONSF_FLUSHONPAUSE |
If the stream is paused, this buffer should be flushed. This parameter is used, for example, by live data sources, where a pause renders the current data stale. |
CSSTREAM_HEADER_OPTIONSF_LOOPEDDATA |
This data buffer is the start of looped data. The driver should loop on this data until explicitly stopped. |
CSSTREAM_HEADER_OPTIONSF_PREROLL |
The data in this buffer is used to prime the device state. This is a stream-specific option. |
CSSTREAM_HEADER_OPTIONSF_SPLICEPOINT |
The data stream is at a natural point for splicing. A client uses this, for example, when sending data that uses inter-frame compression, such as MPEG video, to indicate that it is safe to splice at this point. |
CSSTREAM_HEADER_OPTIONSF_TIMEDISCONTINUITY |
There is a discontinuity in the data stream after this packet. This flag may be used for positional oriented interfaces to indicate an end of stream data. No actual data buffer need be attached. |
CSSTREAM_HEADER_OPTIONSF_TIMEVALID |
The value for CSSTREAM_HEADER.PresentationTime is valid. Indicates that this buffer has a valid timestamp associated with it. |
CSSTREAM_HEADER_OPTIONSF_TYPECHANGED |
The data format for this stream has changed. The data buffer actually contains the CSDATAFORMAT structure that defined the new format. Valid only for streams that have previously negotiated dynamic type changing. On a Stream Write, the new data format must be contained in place of a media sample, and if the media-specific extension size is different, must be the last header in a list of headers for that stream request. The data allocator is not used to contain the new media format. On a Stream Read, any further I/O remains pending until the new format is retrieved through CSPROPERTY_CONNECTION_DATAFORMAT (see CSPROPERTY_CONNECTION). On a Stream Write, the header must not be extended, and must be the only header in the Write. |
Requirements
Header | cs.h |
Windows Embedded CE | Windows Embedded CE 6.0 and later |
See Also
Reference
Camera Driver Macros
CSSTREAM_HEADER
CSDATAFORMAT
CSPROPERTY_CONNECTION