x264 VfW update request thread

[Kostarum Rex Persia]

Well, I really really really hope that main x264 developer (I don't know his name, suppose, perhaps pengvado) will continue to active develop x264 VFW, because VFW is much better to use, than CLI or MeGUI.

Celtic_Druid, any your comment on this? Can you integrate all recent missing patches in x264 VFW?

[Doom9]

With all the problems AVC in AVI has, it's not such a big loss.. And I strongly object to your negative rating of MeGUI... with all its capabilities it's vastly superior than what any VfW based tool can come up with. MeGUI does fully automated rips.. show me a VirtualDub build that does that.

And yes, x264 is in the main round.. I qualified it back in February already.. there's no point in putting codecs that obviously deliver good results through a qualification. Keep in mind, XviD was the reference, it didn't have to qualify either.

There are other participants of course, like VP7, DivX, HDX4 (it's no secret now that it's on their homepage), VC-1, and obviously XviD. In total, there are 11 codecs in the main round, but now that's all I'm going to say. Some time next week, you can read all about the main round, and then the week thereafter, all about the finals.

[acidsex]

I agree, MeGUI is definitely a quality product with a fantastic cost. I definitely appreciate having it at my disposal. Thanks again Doom and others that develop for MeGUI.

[Doom9]

I end up using all the facilities for the comparison.. dgindexer, avisynth script creator, bitrate calculator, and the d2v preview is fantastic.. with it I can check if a codec really jumps to frame X if I tell it to. Obviously, mp4 muxing is done in MeGUI as well...I guess I should try AVI muxing as well.

[Kostarum Rex Persia]

With all the problems AVC in AVI has, it's not such a big loss.. And I strongly object to your negative rating of MeGUI... with all its capabilities it's vastly superior than what any VfW based tool can come up with. MeGUI does fully automated rips.. show me a VirtualDub build that does that.

Ok then. Why you or someone else (Sharktooth, Celtic_Druid) make a x264 VFW build with support for *.MP4 container. That's solution for all problems that AVC in AVI has.

If most people here don't like *.AVI container, then you peoples may include MP4 container, instead of AVI, in x264 VFW builds.

[Sharktooth]

well...there's no solution. The problem is VFW is bound to AVI.
VFW is bad... VFW is dead... VFW is buggy... leave it ALONE. It's there only as the last option.
i think i will remove VFW from the next builds just coz ppl continue to push on VFW. it's outdated, slower and leads only to place h.264 in AVI and that's WRONG!

[Doom9]

actually, in theory it isn't.. but KRP (who has a real nack of scratching just in places that you should not dare touch) wants to use VirtualDub with it.. and that's where the problem comes in. VirtualDub cannot and will not read MP4s.. so forget about editing. VirtualDub will also never write output in another format than AVI. So, while you could theoretically write a whole new software that uses VfW codecs, open AviSynth files and writes out the output to an MP4, it's a whole new program and a lot of effort. And in the end, you still cannot edit the MP4 file as you can edit an AVI.

So, to make sure you don't have to ask again: if you want all x264 options in the VfW, you have to do it on your own. Please don't keep repeating your request anymore.

[Kostarum Rex Persia]

Ok. Doom9, can you help me how to compile my own x264 VFW build with ALL missing patches that MeGUI has. In Delphi 6, or Visual C++?

Give me also the link to patches who has been comitted to SVN.

[Sharktooth]

you obviously dont want to understand.
VFW and MeGUI have nothing in common!
x264 is a codec... MeGUI is an external program that provides a graphical interface for the x264 CLI codec.
You cant add MeGUI patches to x264!!!
Also, x264 is written in plain C. you cant compile it with Delphi or any other language compilers.
The SVN contains the sources and you dont need the "patches who has been committed to SVN" to compile x264... (what you said means nothing anyways)
Also there's a dedicated thread where you can find help in compiling x264.
:search: and dont come back asking for help with VFW. All the info are there.

[DeathTheSheep]

Wow, didn't see this thread. Maybe it should be split into: "x264 and VFW support," because that seems to be what it's about, not x264 in a codec comparison. *shrug*

[Tommy Carrot]

You shouldn't ask vfw update from the developers, for some reason they have a severe dislike towards the vfw version of the codec, and this nagging would lead only to the discontinuity of vfw support. I guess someone must volunteer and write a patch to update the vfw interface, until then we have to be satisfied with the current one (even a feature-lacking version is better than nothing).

[DeathTheSheep]

Yes, I agree. I just thought this thread should be titled differently so people (like me) won't start new threads pushing for vfw.

[Doom9]

so here's how it is: you want it, I'm afraid you have to code it on your own. The core developers only update the cli version.. you have to respect their decision to do that. In fact, the VfW has always been externally maintained and at this point there's just nobody to do that.