Re: Query on Windows CE Video Renderer related to MaxBackBuffers!
- From: "mailto635@xxxxxxxxx" <mailto635@xxxxxxxxx>
- Date: Thu, 8 May 2008 23:09:49 -0700 (PDT)
Hi,
When we set IMemAllocator::SetProperties() during the
CBaseOutputPin::DecideBufferSize(),
video renderer allocator returns the actual properties matching my
properties. But still it does not take them into account.
It always seems to work with a single RGB offscreen surface.
Where as in case of GDI and other modes (DirectDraw overlay) it is
respecting the MaxBackBuffers registry setting.
Regards
On May 8, 8:44 pm, "Alessandro Angeli" <nob...@xxxxxxxxxxxxxxxxxx>
wrote:
From: "mailto...@xxxxxxxxx"
There is no effect of setting the allocator properties in
CBaseOutputPin::DecideBufferSize, as VR seems to ignore
these properties.
So it always returns the same surface/buffer to the
upstream filter.
When you call IMemAllocator::SetProperties() during
CBaseOutputPin::DecideBufferSize(), you will be told what
the actual properties are. If you request more than 1 buffer
but the result is 1, then the renderer can only supply 1
buffer.
--
// Alessandro Angeli
// MVP :: DirectShow / MediaFoundation
// mvpnews at riseoftheants dot com
//http://www.riseoftheants.com/mmx/faq.htm
.
- References:
- Query on Windows CE Video Renderer related to MaxBackBuffers!
- From: mailto635@xxxxxxxxx
- Re: Query on Windows CE Video Renderer related to MaxBackBuffers!
- From: Alessandro Angeli
- Re: Query on Windows CE Video Renderer related to MaxBackBuffers!
- From: mailto635@xxxxxxxxx
- Re: Query on Windows CE Video Renderer related to MaxBackBuffers!
- From: Alessandro Angeli
- Query on Windows CE Video Renderer related to MaxBackBuffers!
- Prev by Date: Synchronize 2 Capture Sources into one Stream to Display 3D
- Next by Date: Re: Filter release build giving problems in Muxing and Rendering
- Previous by thread: Re: Query on Windows CE Video Renderer related to MaxBackBuffers!
- Next by thread: File Source Push Filter - is it possible?
- Index(es):