Re: Output Pin Custom Allocator
- From: Thore Karlsen [DShow MVP] <sid@xxxxxxxx>
- Date: Sun, 19 Feb 2006 17:24:13 -0600
On 19 Feb 2006 14:52:16 -0800, "Roman Ryl..." <ryltsov@xxxxxxxxx> wrote:
As far as I remember, VMR9 connects on ARGB32 first and once the graph
is started it attempts to reagree format with upstream filter via
dynamic reconnection (it is most likely to try 16-, 24- or 32-bit RGB
format depending on your display settings, or some FOURCC format
supported by hardware). You will have Color Space Converter inserted if
you don't support ARGB32. I remember this is mentioned in DirectX 9
.CHM doc file but unsure where exactly.
I think you may be thinking of the old renderer, not the VMR9. The old
renderer can revert to GDI rendering, so it first connects with a media
type representing the current display depth (to ensure that the upstream
filter can provide it with the correct data for software rendering), and
then it switches to a hardware accelerated surface after you run the
graph. The VMR9 never reverts to GDI rendering, so it should give you
the correct media type when you connect, and it should hopefully not
change it after you connect.
--
New to newsgroups? Read: http://dev.6581.com/newsgroups.html
.
- References:
- Output Pin Custom Allocator
- From: SmartSentry
- Re: Output Pin Custom Allocator
- From: Thore Karlsen [DShow MVP]
- Re: Output Pin Custom Allocator
- From: SmartSentry
- Re: Output Pin Custom Allocator
- From: Roman Ryl...
- Output Pin Custom Allocator
- Prev by Date: Re: Output Pin Custom Allocator
- Next by Date: Re: Output Pin Custom Allocator
- Previous by thread: Re: Output Pin Custom Allocator
- Next by thread: Re: Output Pin Custom Allocator
- Index(es):
Relevant Pages
|
