Why no new x264vfw?

[HulkHoganRules]

This might sound like a stupid question as I know little of how this codec business works.

It seems that x264 is getting constant updates so why is the x264vfw latest version from March 2013? Surely integrating a newer x264 would improve compression efficiency since the 6 months it has laid dormant?

Also it's probably false but the user derwischtariqua on the sourceforge page of x264vfw states the latest version has a memory leak.

Thanks

[MasterNobody]

There is no new version on sourceforge because I am too lazy. Also there were no really anything BIG for quality/compression between r2274 and current version except OpenCL support (which is not very stable and I don't want to enable it in current state) and AVC-Intra (which is mostly irrelevant for VfW version).
And no, I don't know about any memory leak in current version of x264vfw. Nonsense reviews without any provided information are iirelevant. If you really found out bug you need to provide full information and fill bug report.

P.S. If you want x264vfw with new enough libx264 you can always try komisar's build (but it have old school configuration dialog). Ops. Looks like he also didn't build anything newer then r2273 for VfW.
P.P.S. Ok. There was also AVX2 optimizations after r2274 but it is not so big deal also (speed up from it is no so big).

[HulkHoganRules]

Thanks for the info. That's good to know. I absolutely love x264vfw for game capturing. Its lossless mode (with keep input colorspace enabled) has way lower data rates than Lagarith for my YUY2 sources.

[edison]

The "slow" lossless mode of x26vfw would cause error in virtualdub.

[MasterNobody]

Originally Posted by edison

The "slow" lossless mode of x26vfw would cause error in virtualdub.

Be more specific what do you mean by error (error message/screenshot/samples) and what parameters you used. I don't have any problems with encoding in lossless mode and preset "slow" in VitrualDub (all other options at default + "VitrualDub Hack" option enabled).