KSPROPERTY_STREAM_RATECAPABILITY
The KSPROPERTY_STREAM_RATECAPABILITY property allows a graph manager to query all connection points involved in the flow of a particular stream (obtained through KSPROPERTY_PIN_DATAROUTING) for their capability in adjusting a requested rate to the nominal rate.
Usage Summary Table
| Get | Set | Target | Property Descriptor Type | Property Value Type |
|---|---|---|---|---|
Yes |
No |
Pin |
Remarks
KSPROPERTY_STREAM_RATECAPABILITY should be implemented if a pin allows rate changes, or the interface between topologically-related pins is different and results in the use of a different time stamp format. The property can also be used to translate time stamp formats in general, such as skip degradation requests.
The property is supported by pins that modify the rate of data through resampling or time stamp changes. All rate changes involve requesting a rate and determining how much a specific pin can correct that rate to obtain the nominal 1.0 rate. For example, a pin requesting a video playback rate of 2.0 would imply a request to render at twice the nominal rate of the video clip; a rate request of 0.5 would imply a half-speed rendering.
The rate request contains both the presentation start time and the duration for that rate request. This allows for constraints that might apply to specific portions of a data stream to be taken into account. The presentation time, numerator/denominator pair, and duration units are expressed in terms of the Interface specified in the structure. If a standard interface is not used, the initial rate change queries cannot be sent to a pin.
A pin must be able to accept interface identifiers used by any pin with similar topology. It must also translate the interface identifier and time units to its own corresponding values. In this manner, a client can traverse a graph from one known interface point and have units translated by connection points at each step of the way.
It is important to support this property if Interface changes are made even if rate changes cannot be made, so the Interface and time units can be adjusted when queries are made. The result would not change the rate returned but would change the Interface, PresentationStart, and Duration.
Rate capability requests can only be performed in Pause or Run state and become invalid after changing to any other state. Queries where the rate is initially 1.0 should always succeed as they typically are just requests to translate time stamp formats.
Requirements
Header |
Ks.h (include Ks.h) |