View Full Version : x264 and b-frames flushing
bond
24th February 2005, 02:21
since r137 x264 includes a fix for flushing frames when using b-frames at the end of encodes
am i right that this doesnt affect the behaviour of the vfw encoder? at least here it seems as if the behaviour is still the same (number of delay frames in the stream is the number of the chosen consecutive b-frames)
sysKin
24th February 2005, 04:08
I think it will never affect vfw encoder - there is no way for VfW to know if encoding has finished and there is a need to flush - and even if there was, encoder has no way of transmitting the flushed frames to encoding application.
Like in Xvid.
virus
24th February 2005, 04:14
Seems to work perfectly in mencoder. You end up with an AVI without dummy frames at the start, and without missing frames at the end. Virtualdub(mod) doesn't support this kind of flushing.
BTW I'm having some problems both seeking and with the framenumber shown in ffdshow's OSD when decoding properly flushed mencoder clips; ffdshow seems to have troubles at the start and at the end of the clip. For example, it displays both the frames 0 and 1 as I-frames (and they aren't). It also doesn't display the last frame (it ends up with a B). Opening the clip in Vdub gives no problems at all.
Someone has seen the same? Maybe I should update ffdshow to a very recent build? (mine is Jan 17 I think)
akupenguin
24th February 2005, 05:27
Even when the stream is flushed, there's still a decoding delay in ffdshow. It displays the first frame twice, because it the first time it didn't know that the stream contained B-frames.
bond
24th February 2005, 10:57
virus, do you also now have the same framenumber in the output as in the input with mencoder? in vfw you loose the number of b-frames you set
also search for "b-frame decoder lag" with xvid :)
virus
24th February 2005, 11:16
Originally posted by bond
virus, do you also now have the same framenumber in the output as in the input with mencoder? in vfw you loose the number of b-frames you set
also search for "b-frame decoder lag" with xvid :)
bond, I know pretty well that lag message ;)
But yes, I can confirm what I wrote above: no dummies, no frame loss... mencoder produces an AVI with the same framenumber as the source. You don't lose anything. Unfortunately there's that duplicated first frame when opening it (either in VfW or DShow). I wonder if using a different container resolves this glitch or not. Anyway seeking in this build of ffdshow I'm using seems somewhat b0rked and may not be related to these particular (non-vfw) AVIs. I can't see the last frame in MPC, but Vdub definitely shows it.
bond
24th February 2005, 11:21
Originally posted by virus
Unfortunately there's that duplicated first frame when opening it (either in VfW or DShow). I wonder if using a different container resolves this glitch or nottry the rawvideo output of mencoder and mux into .mp4 with mp4creator :)
Doom9
24th February 2005, 11:22
try the rawvideo output of mencoder and mux into .mp4 with mp4creatorThis'll soon be done automatically in MeGUI (sorry, couldn't resist a little self promotion).
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.