Does xvid drops frames?

[movmasty]

just encoding a movie in parts, the number of frames encoded by xvid is always less than that showed in vdub, and changes with b frames settings.

Last part i just made:

VirtualDub 4423 frames

xvid b sensitivity -10,4422

xvid b sensitivity -6, 4421

[Koepi]

Wrong forum - this belongs into the xvid forum.

Also, if you look into the FAQ or use the search you'll find your encoding application to be guilty.

[movmasty]

i did a search but didnt find nothing, found only about time shift in vdub with b frames,

but the source is not in xvid, then original frame number should be correct, and i read the number of frames encoded on the xvid encoding status, not in the main panel of vdub, as this was a first pass i dont have any movie to open in vdub

[stephanV]

use virtualdub 1.6.0. it should be fixed there.

its not just the fault of VirtualDub, its also VFW having no real support for b-frames.

[movmasty]

Originally posted by stephanV
use virtualdub 1.6.0. it should be fixed there.
didnt read in the bugfix

[movmasty]

encoded another piece, vdub1.6 shows 4656 frames, xvid encoded 4653....
Bmax 2, b sens 0

So i cant encode this movies in pieces like i would like, too many frames will be dropped,
and dunno what will happen to audio sync.

I am encoding with xvid 1.01, does the 1.02 fix this??

[movmasty]

encoded the same clip without b frames, xvid encoded the right number of frames, 4656,

there are 3 frames less with B frames on, and, sice i set max b to 2,
it dint just drop the last 2 b frames

[movmasty]

http://forum.doom9.org/showthread.php?s=&threadid=73882&perpage=20&pagenumber=2
Originally posted by theuser86 6th April 2004
I have one problem with the XviD 1.0 line, all versions from RC1 to RC4 drop ONE/TWO frames when I encode. I have not had any other problems with previous versions of the xvid codec.

For example, my source of my last encode was 40748 frames, but the AVI (2-pass) encoded with XviD 1.0 RC1/2/3/4 is 40747 frames. All the settings in the codec are left as default except for the target size set on the 2nd pass. Everything else is the same, but I still have this problem. Each new version that is released I hope that problem is fixed, but I get the problem each time.
Originally posted by Leak 7th April 2004
The problem here is that it's not XviD screwing this up but VirtualDub. IIRC, VirtualDub has a workaround that'll compensate for this problem (the codec not getting enough frames so that the last frame is a P or I frame, as B-frames can't just hang in the air and the codec can't make extra frames up as it can only ever return one output frame for one input frame) by serving extra (duplicated) last frames to the codec until it gets a P- or I-frame, but it doesn't recognize the newest versions of XviD anymore (probably because the code for the workaround hasn't been updated for some time).

It's VirtualDub that needs to be fixed (probably by adding the new XviD version string somewhere), not XviD.

that could be, prob is with b frames, but then vdub needs to be upgraded at every new version of xvid?

and dont understad why frames dropped are up to 3 when max b frames are two

[movmasty]

Originally posted by Leak 7th April 2004
I guess it's quite different - at least with the stuff I encode (anime episodes mostly), the end usually consists of a few black frames, which I couldn't care less about if they go missing.

I guess that's why nobody notices it or cares much about this...

and what about if you like to compress a movies in several pieces??

[Aktan]

The answer Koepi is talking about is prob to use vdub version 1.5.4 or vdubmod ver 1.5.4.1

[movmasty]

where could i find those versions?

but xvid could not implement a routine that,is a frame is the last to encode, it is forced to be a P frame?

[lordadmira]

Aktan meant to say that those versions have the bug.

If 1.6 is still doing it, a workaround it to create a zone at the end of the section with Bsens = -9999999 and Begin With Keyframe checked. e.g. if 5000 frames, start zone at 4999. That should do it.

Xvid has no way of knowing the last frame although a way could be made for 2 pass encodes. That's a deficiency in the system if u ask me.


LA

[movmasty]

Originally posted by lordadmira
Aktan meant to say that those versions have the bug.

If 1.6 is still doing it, a workaround it to create a zone at the end of the section with Bsens = -9999999 and Begin With Keyframe checked. e.g. if 5000 frames, start zone at 4999. That should do it.
yes, sure, many thanks,

hope that a one frame zone wont crash