Re: Direcshow problems with WMV9 Decoder for XP platform

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: "Kris"

Here are the logs ... let me know if you want more info.
I did not print the getTime values from the receiving end
since it was not set.

I asked you to normalize the system time so that it is
zero-based, anyway...

As clearly stated in the docs, IMediaSample::IsSyncPoint()
returns an HRESULT, not a BOOL, where S_OK (0) means TRUE
and S_FALSE (1) means FALSE, not the other way around, so
you are inverting all the flags (and you should also handle
other HRESULTs as errors). The same applies to the other
flags.

Look at the difference of the system time between
consecutive frames: it is taking you on average 1300..1500
millisecs (< 1 fps) to process a frame instead of < 66.7
millis (15 fps).

Either your code takes too long to process the frames or you
are not dispatching window messages or the light is so low
that the camera has a hard time shooting or the encoder is
too slow (and you should change the complexity as I told you
before).

A side question ... I was looking for other encoders
(other than WMV3) for the pocket pc but could not find
any. Do you know if others exits?

It depends on the OEM.


--
// Alessandro Angeli
// MVP :: DirectShow / MediaFoundation
// mvpnews at riseoftheants dot com
// http://www.riseoftheants.com/mmx/faq.htm



.