See Also
 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. |
This interface enables an application to request how many buffers a filter creates and the buffer size. Any pin that connects using the IMemInputPin interfacecan expose this interface, but is typically exposed on the output pins of capture filters.
When two pins connect through IMemInputPin, they agree on an allocator object that is responsible for creating buffers. Normally this process is transparent to the application, but in some situations the application needs more control. If a pin exposes IAMBufferNegotiation, then the application can suggest how many buffers to create, the size of the buffers, and other properties. If your application performs preview of captured audio, you can specify a smaller buffer size to reduce latency. Teleconferencing applications should specify a minimal number of buffers.
To use this interface, call the SuggestAllocatorPropertiesmethod before the pins connect. After the pins connect, call the GetAllocatorPropertiesmethod to determine whether the pin honored the request.
Filter developers: Capture filters should always support this interface when possible.
In addition to the methods inherited from IUnknown, this interface exposes the following methods.
| Method | Description |
|---|---|
|
Retrieves the allocator properties that the pin is using. |
|
|
Informs the pin of the application's preferred allocator properties. |