View Full Version : MeGUI and WMV9 Problem
dud
15th March 2008, 10:27
I'm having some problems trying to convert some WMV9 videos encoded with Windows Media Encoder 9. The encoded video plays too fast and jumps around to different places in the video throughout. I've updated everything there is to update in MeGUI.
Sharktooth
15th March 2008, 15:42
try using ffdshow as WMV9 decoder. the M$ decoder seems to have some problems when used with directshowsource...
dud
15th March 2008, 17:43
Tried it and got the same results. Is there any other solutions?
setarip_old
16th March 2008, 01:35
@dud
Hi!Is there any other solutions?Instead of trying to use the WMV that you created, use the original source material, that you orignally used to create the WMV video, to create the .MP4...
dud
16th March 2008, 18:56
The original source is a game. I'm using Windows Media Encoder to capture in-game footage since it is the highest quality screen capture program I can find that is free. So there is no original video file to speak of.
setarip_old
16th March 2008, 18:59
Does your captured WMV video play properly?
dud
16th March 2008, 23:41
It plays fine in both Media Player Classic and Avisynth Script Creator's video preview. The video properties are as follows:Video: Windows Media Video 9 640x480 29.97fps 3548Kbps [Raw Video 1]
I tried lowering the bitrate all the ways down to 352Kbps but that didn't help either.
Sharktooth
17th March 2008, 13:57
it's not a matter of bitrate.
sadly i heard other ppl having problems with WMV as input.
you need to work-around the problem but i have just no idea in how to do it since i NEVER use WMV.
DarkZell666
19th March 2008, 15:28
I recently have been trying to convert some WMV files to other formats, and have found as only solution to encode them to mpeg2+mp3 inside mpg using ffmpeg, and work with the mpg file.
Off the top of my head, here is what I did :
ffmpeg -i "whatever.wmv" -r 29.97 -acodec libmp3lame -ab 320 -vcodec mpeg2video -b 10000000 -f mpeg "whatever.mpg"
I chose mpeg2video because it was far faster than xvid, and also far faster than ffv1, which caused the HDD to trash severely, actually slowing the process down compared to mpeg2, with almost no quality gain.
The -b 10000000 is disputable, but I couldn't find the quantizer option, otherwise I would have set it to 2 instead of choosing an arbitratily high bitrate.
The manual "-r xx.xxx" was necessary for me since ffmpeg reported my wmv files as 1000 fps. It's good you actually managed to get the "true" framerate, since I spent a couple of hours getting mine right.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.