Andrew Sha

Hi All,

The situation:

I wrote a virtual filter-centric AV Stream renderer and it works fine in the
graphedit - I feed it from the WM ASF reader; I can see arriving frames in
my Process callback- the renderer swallows them by setting BytesUsed =
BytesAvailable - everything is ok,
But when I access this renderer by the waveOutOpen function and as soon as I
submit the only buffer by the waveOutWrite function, my Process callback is
called in endless loop, it seems like the same frame is delivered again and
again and again.
Any ideas why it happens?
What the difference between these two cases?

TIA
Andrew

Max Paklin

What does your Process callback return?
Do you advance stream pointers?
What is the type of the stream that you create? Is it identical in the two
tests that you are running? If not, what's the difference?
Is the format of the stream negotiated dynamically after the connection has
been made?

-- Max.


"Andrew Sha" <universalkludge@hotmail.com> wrote in message
news:e$WhNuA0FHA.3856@tk2msftngp13.phx.gbl...
> Hi All,
>
> The situation:
>
> I wrote a virtual filter-centric AV Stream renderer and it works fine in
> the graphedit - I feed it from the WM ASF reader; I can see arriving
> frames in my Process callback- the renderer swallows them by setting
> BytesUsed = BytesAvailable - everything is ok,
> But when I access this renderer by the waveOutOpen function and as soon as
> I submit the only buffer by the waveOutWrite function, my Process callback
> is called in endless loop, it seems like the same frame is delivered again
> and again and again.
> Any ideas why it happens?
> What the difference between these two cases?
>
> TIA
> Andrew
>
>