digitalFAQ.com Forums [Archives] - VirtualDub: Will not load video

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)

- Video Encoding and Conversion (http://www.digitalfaq.com/archives/encode/)

- - VirtualDub: Will not load video - codec problem? (http://www.digitalfaq.com/archives/encode/11523-virtualdub-load-video.html)

VirtualDub: Will not load video - codec problem?

I dont understand it...

bf frame decode lag??
look this pic

http://www.4techs.com.br/casemod/problem.jpg

Try another source.

-kwag

I think that is a XviD codec issue.
You can see whole movie?
If you can see it, not problem, I heard that standalones don't show this advise. But in any case you can cut first frames of your mpeg file with TMPGEnc mpeg tools.

Im not in deep Xvid Settings but Dialhot already gave an answer to this issue in another thread.
Logially seen: It seems that your source was encoded using special advanced XVID settings which are not supported by your decoder in your system. So maybe an update to the latest XVID codec could solve your problem!?

But Dialhot could give you a more precise answer ;-)

It's not exactly related to any specific build of XviD, I think that all codecs have the same issue but for example Nic's build just doesn't show the error message. Absolutely nothing to worry about :wink:

Quote:

Originally Posted by Hiro2K @ Doom9

It's a problem with the VFW structure. A B-frame refrences the frame before it to make it's picture. But VFW won't let you move the frame order around and so that's why it will tell you bframe decoder lag. Using a directshow decoder will fix this and that is why you won't see it when your playing the file. It's not a problem, and the reason that it doesn't happen in divx is that it uses some hacks to the avi container to get the b-frames to work right. Xvid stores the b-frames in the order that they go and that isn't supported by the VFW structure.

movie was encoded without "packed bitstream" on. not a problem for directshow, but it is one for VFW as doom9 pointed out.

two possible solutions:
1. use a XviD build, that doesnt show the message (it will probably dupe a frame then)... using DivX to decode it should work too, but perhaps that might give jerkiness.
2. use a DS-decoder

*me ducks*

Quote:

Originally Posted by incredible

StephanV already answered to the current problam, and Boulder remembered what I also said : this problem was in all Xvid realese but formers ones just didn't gave any warnign on the screen ;-)

But what you are related Inc is different : there are new features in Xvid codec that are not even UNDERSTOOD by the VFW decoder delivered with Xvid. In this case, Vdub does not show anything but a "Error -100" in the bottom line and does not decode any frame at all !
In this case, as StephanV said, you must used the DS filter decoder (that can be done with virtualDub Mod by using "use Avisource" in the open file dialog). And of course you have to use "DirectShowSource" in an avisynth script.