I found the good answer here, Codec property.I have tried two kinds of decoders, the Intel Media SDK one and the. I can define each (simple) graph with a video source, a decoder, and the EVR filter. It seems to handle most things you throw at it.ĭon't forget to start a new thread if you have more questions as people may not come across your questions here on an old thread. Woot woot MSDN support men Im developing an application that executes several DShow graphs in order to decode and render H264 video streams. Otherwise, if your goal is to put them onto DVD, you might want to give these free programs a go.ĪVI2DVD They may do the job for you. You may have to hunt for them to find how to do the conversion properly. There are special procedures on the net for converting between those two frame rates. If this is what is occuring the pulsing you see would look quite fast as it would be happening at 6 times every second (30-24). The codecs support several levels (source formats) that range from Limited Definition (VCR quality) to full HDTV. It is possible that you are seeing 'beating' caused bu a mismatch of these two frame rates. The LEAD MPEG-2 Encoder and LEAD MPEG-2 Decoder provide everything needed to compress and decompress MPEG-2 videos in. Would these AVI's started their lives as NTSC DVD's? Maybe one started out as PAL or even film as I mention below.įrom looking at the Gspot results you posted there seems to be a frame mismatch between "film style" 24 frames per second and 30 frame per second NTSC (60 fields per second). That said, i'll describe what I think may be going on.įirst i'm wondering if the two AVI's, when made, were encoded the same way and from the same type of video file.
I'm not a complete expert so you might be best to post your question in a new thread on this forum.
0 kommentar(er)
