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. |
Determines a media type for a pin connection.
Syntax
virtual HRESULT TryMediaTypes( IPin* pReceivePin, const CMediaType* pmt, IEnumMediaTypes* pEnum ); |
Parameters
- pReceivePin
-
Pointer to the IPininterface of the receiving pin.
- pmt
-
Pointer to a returned media type.
- pEnum
-
Pointer to an IEnumMediaTypesenumerator interface.
Return Value
Returns an HRESULTvalue, which can include the following.
Value | Description |
---|---|
FAILED |
Resetting of the enumerator failed. |
NOERROR |
Media type found. |
No acceptable media types were found. |
Remarks
Given an enumerator, this member function cycles through all media types proposed by the enumerator.
Each type is suggested to the derived pin class and, if acceptable, is tried with the connected pin in a call to the IPin::ReceiveConnectionmethod.
This means that if the owning pin proposes a media type, it is still checked to determine whether it is supported. This is deliberate so that, in simple cases, the enumerator can hold all media types, even if some are not currently available.
This member function is protected.
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 |
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.