 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. |
Retrieves the allocator interface that this input pin identifies as the interface for the output pin to use.
Syntax
HRESULT GetAllocator( IMemAllocator** ppAllocator ); |
Parameters
- ppAllocator
-
Pointer to an obtained IMemAllocatorobject.
Return Value
Default implementation returns either E_OUTOFMEMORY, if an allocator cannot be created, or NOERROR upon success.
Remarks
This member function implements the IMemInputPin::GetAllocatormethod, which is called by the connected output pin to retrieve an allocator to use for transporting media samples.
By default, this member function creates a CMemAllocatorobject and obtains the IMemAllocatorinterface, to which it adds a reference count for the pin when assigning it to the m_pAllocatordata member, and adds another reference count before passing it back to the output pin.
Override this member function if your filter has another allocator, such as one from a downstream pin, or a specialized allocator to offer the connected output pin.
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.