xvid does not encode one frame when max bvop>=2?

[vie2233hil]

Hello,

Is this a bug? A known bug? A feature?
I select 30 frames in avs script and encode it with the default xvid settings (max bvop=2), the resulting avi file has 29 frames.
Is this normal?
When I set max bvop to 1 I get 30 frames in avi.

Thanks in advance

[Koepi]

Use the search, this has been answered like a million times now.

Use avs2avi or max. vdub(mod) 1.5.4.1, it's a virtualdub bug.

[Asrial]

I was bored and played around with this a little bit since I'm noticing it too, with my recent dabblings with b-frames...

VDUBMOD: 1.5.4.1 (build 2066)
HUFFYUV: 21190 frames total (frame 21176 has a picture, frame 21177 is black)

2 b-frames produces 21189 frames total (frame 21176 has a picture, frame 21177 has a picture, 21178 is black -- I made sure to test this in a forward moving manner)

[Asrial]

AVISOURCE("EPISODE 1 -- HUFFY.avi")

last.trim(1,0)++last.trim(1,2)

What this does is it takes away 1 frame in the beginning and adds 2 frames at the end.

What happens during encoding is 1 frame is added in the beginning and 1 frame is taken away at the end. Everything matches up now like it's supposed to.

[EDIT: or maybe that should be "encoding adds 2 frames in the beginning"]

This is for 2 b-frames.

I'm tired so I wasn't searching for the best and most efficient method of resolution, but it's to get you started on the right path vie2233hil.