Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

Queues an IPin::NewSegmentcall to the connected input pin after all queued samples have been passed to the input pin.

Syntax 

HRESULT NewSegment(
  REFERENCE_TIME 
tStart,
  REFERENCE_TIME 
tStop,
  double 
dRate 
);

Parameters

tStart

[in] Start time of the segment.

tStop

[in] Stop time of the segment.

dRate

[in] Rate of the segment.

Return Value

Returns an HRESULTvalue.

Remarks

This member function calls the IPin::NewSegmentmethod on the output pin after all previous data has been delivered.

Like COutputQueue::EOS, the COutputQueue::NewSegmentcall and its parameters are queued as a special control sample if the COutputQueueobject is in queued mode, and the IPin::NewSegmentmethod is called from the worker thread in COutputQueue::ThreadProc.

Special control samples, as implemented by this member function, are only relevant if you plan to change or extend the default base class implementation of COutputQueuein a derived class. Normal use of the COutputQueueclass does not require the use of control samples.

This member function allows filters that process buffers containing more than one sample to delineate the rendering of the samples between start and stop time, as indicated by the tStartand tStopparameters.

COutputQueue::NewSegmentis intended to be implemented on an input pin. A connected output pin on the upstream filter calls this member function after completing delivery of previous data and before calling IMemInputPin::Receivewith any new data. It indicates that all data arriving after this call is part of a segment delineated by the parameters.

Requirements

Windows Embedded CE Windows CE 2.12 and later
Windows Mobile Windows Mobile Version 5.0 and later
Note Microsoft DirectShow applications and DirectShow filters have different include file and Library requirements
For more information, see Setting Up the Build Environment,
Version 2.12 requires DXPAK 1.0 or later