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

This method returns the range of times in which seeking is efficient.

Syntax 

HRESULT GetAvailable(
  LONGLONG* 
pEarliest,
  LONGLONG* 
pLatest
);

Parameters

pEarliest

[out] Earliest time that can be efficiently seeked to.

pLatest

[out] Latest time that can be efficiently seeked to.

Return Value

Returns an HRESULTvalue that depends on the implementation of the interface. The default DirectShow implementation returns S_OK for success and E_NOTIMPL if the method is not implemented.

Remarks

This method is intended primarily for seeking in media streams that might have excessive latency, such as when playing back media live from an Internet server.

The returned values indicate cached data that has already arrived, which can be easily seeked.

It is assumed that seeking to values beyond these returned parameters will cause a delay while waiting for the data to arrive.

Requirements

Windows Embedded CE Windows CE 2.12 and later
Windows Mobile Pocket PC for Windows Mobile Version 5.0 and later, Smartphone for 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

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.