Latest VfW Version

Latest VfW Version
January 1, 2008. REVISION 714b. DeathTheSheep United Click above for the la-*test*-('") version of the VfW. This post will be updated whenever a new version become available. Happy encoding! :D

Can you tell me on which revision is based newest VFW build? Thanks. I found little bug. When I click on value 4 in Particion Decision, Chroma ME isn't available at all. Can you fix it, please?

Hi KRP! I remember you from Doom9's forum. I was kicked out for wanting to use VfW. Pretty nice, huh? Well, this is not a bug. Chroma motion estimation should be disabled under ME5 because x264's chroma ME cannot function unless the sub pixel refinement (motion search precision) algorithm performs a fully QPel search decision--that's when chroma info is taken into account. x264 doesn't take this info into account under partition decision 5. Tools like MEGui have the real bug--they allow you to select it, even when it slows encoding and has no effect on the resulting file (usually the files are byte-by-byte identical). But then again, MEGui has tons of errors. And it doesn't even allow for interlaced encoding. :) Anyway, using less than partition decision 5, is pretty much not recommended.

Nice! I was so sorry to hear that x264 has gone completely cli. What's wrong with vfw, why did they suddenly dislike it so much?

Nice! I was so sorry to hear that x264 has gone completely cli. What's wrong with vfw, why did they suddenly dislike it so much? Devs decided that vfw isn't good for AVC, so they banned vfw. On Doom9 forum, if you just say the word "x264 VFW", ChronoCross or other members start to yelling almost immediately. P.S. DeathTheSheep, you didn't told me on which cli revision is based current x264 vfw build? On 594, or 590? P.S.S. I use motion search precision 4 because I record TV analog program directly in x264 codec. Value 5 has too high CPU usage on my system. As far I know, value 5 performs a fully QPel search decision, value 4 do it just partially.

Sorry, I just saw it. Current vfw revision is based on rev. 586, right? I can't wait new build, please compile it soon, devs.

Re: Latest VfW Version
October 9, 2006. Click for the la-*test*-('") version of the VfW. (10/09/06, based on revision ~586). This post will be updated when new version become available. Happy encoding! :D Thanks DeathTheSheep & kurtnoise. Long live VFW :D . PS.: Are you sure its 586 ? Because 586 was made ~22:55. Your Build ~17:00. So unless i mixed up the timezones its nearly impossible that this build is based on 586. 585 may be possible. Anyways it would be cool if you could include the revision Number too (And the nice Dead Sheep Pic maybe as logo ;) just kidding).

Heh, you may be right. Wow, how things slip your mind. Yes, now that I look back on it and the timestamp, 585 it was... Well, expect a new build for revision 600, regardless :)

http://kurtnoise.free.fr/index.php?dir=x264vfw/ silent updates to the revision 600.

http://kurtnoise.free.fr/index.php?dir=x264vfw/ -it's not work

because AutoIndex script doesn't like russian language..:p Use the old entry : http://kurtnoise.free.fr/x264vfw

because AutoIndex script doesn't like russian language..:p Use the old entry : http://kurtnoise.free.fr/x264vfw Thanks. Now - works What there is updattind? А по-русски: Приогромное спасибо, давай на русском общаться? :D

Nothing new...I just updated the library.

http://kurtnoise.free.fr/index.php?dir=x264vfw/ silent updates to the revision 600. Thanks kurtnoise, keep up your work. PS.: Could you include the revision no. somewhere in the vfw window (Some guys like me are just paranoid -> "No Version Number ? Oh god...maybe I'm using something old *shrieeek" ;)

ty guys :) PS.: Could you include the revision no. somewhere in the vfw window (Some guys like me are just paranoid -> "No Version Number ? Oh god...maybe I'm using something old *shrieeek" ;) About button next to configure in virtualdub

View Full Version: Latest VfW Version