x264 vfw development and bugreports

[Doom9]

I suppose it will be mostly bugreport because hardly any developer cares about the VfW, but this is the thread for the VfW camp. Starting at the moment I hit the submittion button, it will no longer be permissible to post anything x264 VfW development or bug related except in this thread. I also do not want to see any messages about VfW not being adequante for x264 in this thread, as well as any discussion why somebody wants the VfW codec, and there will be no clamoring/asking/requesting/demanding for codec features to be added to the VfW interface.

Anybody who doesn't like what is written here or wants to argue semantics is eligible for a rule 16 strike and leniency is a word that from this point on I can't even spell.

[bob0r]

some known bugs:

Not properly working boxes:
VFW - Rate Control TAB: MIN QP
VFW - Rate Control TAB: MAX QP
VFW - Rate Control TAB: MAX QP Step
VFW - More... TAB: Threads

Easy solution, just need someone to do it :)
(i installed VC 6.0, next stap is to get in the mood :p)

Some features not in VFW:
Quality-based VBR (--crf *)
Fast P-Skip (--no-fast-pskip)
Custom quantization matrices (--cqm *)
Buffer control
Zones

Some are easy to add, again someone needs to be willing to code some VFW!

[Kurtnoise]

some known bugs:

Not properly working boxes:
VFW - Rate Control TAB: MIN QP
VFW - Rate Control TAB: MAX QP
VFW - Rate Control TAB: MAX QP Step
VFW - More... TAB: Threads
Could you elaborate this ?

[bob0r]

For example, go into the Threads box, put mouse cursor behind the 1 and try hit backspace.

[Kostarum Rex Persia]

http://files.x264.nl/force.php?file=./x264_vfw_fast_pskip.diff

Here it is, no-fast-p-skip patch for vfw. And if you look the date, you will see that this patch posted on files.x264.nl on February 12.

[celtic_druid]

I added that along with some other stuff way back in I think Dec as part of my fairuse wizard release. There is a patch of the changes somewhere around here.

[Yong]

Bug 1: the x264 vfw debug option: long level,
if i select the "info" or "debug", vdub will hang if i start encoding.

bug 2 : the strange-looking x264 error console :
http://img90.imageshack.us/img90/1340/x264debug3qw.png (http://imageshack.us)

[dragongodz]

there will be no clamoring/asking/requesting/demanding for codec features to be added to the VfW interface.
as an addendum to this i would like to point to this thread
http://forum.doom9.org/showthread.php?t=105899
this explains whats missing and what people can do about it if they want them. so there is no need for anyone to ask here.

[Sharktooth]

the fast p-skip patch needs a cleanup before sending it to pengvado

[Romario]

Yes, that right, Sharktooth. BTW, how about Trellis Quantization mode 2 in x264 vfw.

I can't see it, only value 1 for Trellis.

[celtic_druid]

I added a drop down list with 0/1/2 when I added the other stuff.
All someone needs to do is gather the patches, clean them up and add subme=7.

[Tommy Carrot]

indeed. but since i have some free time i could do it.
just point me to where are the patches...
I may be wrong, but i think he was talking about this patch:

http://celticdruid.no-ip.com/temp/x264vfw.diff

[Doom9]

I have just handed out months worth of strikes to participants of this thread and for the third or fourth time cleaned it up. Do I have to start banning people before they get the frigging message? I say it again:
NO FEATURE REQUESTS!!!
NO DISCUSSION ON MERITS AND FAULTS OF VFW AND ALTERNATIVES!!!!

Post here if you

have found a bug
have written a patch for the x264 VfW codec and want some feedback

in any other case
DO NOT POST HERE!

[Inventive Software]

I downloaded the no-fast-pskip diff, but I don't know how to apply it. "patch" doesn't want to cooperate with me, and it's driving me up the wall! I must add I'm trying to apply it in MinGW, as this is what I'm using to compile the VFW.

On a slightly unrelated note, I have added a dropdown combo box for the profile level, but as yet not related it to the settings.

[Kopernikus]

What commandline do you use? What error is reported?

[ChronoCross]

you should be able to do it using the following.

patch < patch.diff -p0

if you forget the -p0 it probably wouldn't work.

Here's a copy of the dll for anyone who is interested.

http://www.chronocrossdev.com/apps/x264/x264vfw.rar

[DeathTheSheep]

I made my own contribution to VFW development by making the first complete x264 VFW Guide with all kinds of detailed settings descriptions, directions, and suggestions to "bring out the Ultimate in your x264 encoding!" Find it here (http://forum.doom9.org/showthread.php?t=98247) if you're interested!

[bob0r]

the fast p-skip patch needs a cleanup before sending it to pengvado

It was created by me, so it should not used at all, i used visual studio 2005, which only makes a mess.

ChronoCross knows what he is doing (hopefully :p) so i guess he looked at the patch first.

Fast P-skip was easy to add as it was not depending on any other options.

The file is only there because i asked pengvado how the outcome looked, and it indeed was not as it should be.