Re: waveformatex and fillbuffer()
- From: Thore Karlsen [MVP DX] <sid@xxxxxxxx>
- Date: Tue, 24 May 2005 08:53:36 -0500
On Mon, 23 May 2005 23:03:43 -0700, "James" <j.w at No_Spam_Please zoom
co uk> wrote:
>Hi Thore, Sorry, I looked one too far... I was actually returning 128KB from
>CBaseOutputPin::DecideBufferSize(). What I am actually doing is implementing
>my own audio renderer to captrure PCM data, transform it, then feeding it
>back into a recompression graph (to save it back to disk... I am doing more
>than can be applied to a transform filter).
>
>I got the 128KB from the incoming audio renderer (I then use this to set the
>output on the outgoing wav source filter). The trouble turns out to be in
>the renderer. I have overriden just two funcs:
>
>DoRenderSample() and CheckMediaType()
[...]
>Could you advise why FillBuffer is comming back with 128KB in DoRenderSample
>when I would expect 125KB as per CheckMediaType? Have I just got my math
>wrong?
The buffer size is decided when the filters are negotiating an
allocator. Try overriding CBaseInputPin::GetAllocatorRequirements() on
your renderer and propose a buffer size of 128000 bytes, and see if the
upstream filter respects that.
--
New to newsgroups? Read: http://dev.6581.com/newsgroups.html
.
- Follow-Ups:
- Re: waveformatex and fillbuffer()
- From: Chris P. [MVP]
- Re: waveformatex and fillbuffer()
- References:
- waveformatex and fillbuffer()
- From: James
- Re: waveformatex and fillbuffer()
- From: Thore Karlsen [MVP DX]
- Re: waveformatex and fillbuffer()
- From: James
- waveformatex and fillbuffer()
- Prev by Date: Re: accessing activity of VideoWindow (VMR)
- Next by Date: Re: rendering WMV keyframes
- Previous by thread: Re: waveformatex and fillbuffer()
- Next by thread: Re: waveformatex and fillbuffer()
- Index(es):
Relevant Pages
|