x264 development

[DarkFoon]

@Kyle
It sounds like Akupenguin's suggestion is where you should begin. If you have more problems after trying that, maybe PM him (with his permission) so as not ot set off the anti-VFW trolls.

[Kyle_Katarn]

Allright ! I was not trying to feed the trolll... only to get some assistance ;-)

I'll contact Akupenguin.

[Kostarum Rex Persia]

Ugh...

Everybody, since we all know where we stand on the subject, let's just respect the other party's opinion, and let things be. Nobody is going to convince anybody else on this topic, that is clear. Therefore, it is a waste of time discussing (read: arguing) it at all.
Especially here.
If you want a VFW flame war, start a new thread titled "VFW sucks!" and enjoy. Or better yet, start your own forum website titled "DeathToVFW.net" and battle there.

And to you noobs out there about to post some problem you're having with x264 in Virtualdub: use your head a little bit before posting! Don't make a general acusation ("x264 is borken!") until you have pinpointed the problem. That is called making a good bug report. If the problem lies with VFW, you're S.O.L here. Use the CLI or a different codec. Or, fix the problem yourself.

Yeah, I support his attitude:angry: This isn't place for flame wars.

[ChronoCross]

Yeah, I support his attitude:angry: This isn't place for flame wars.

your one to talk. you create 99% of the flamewars that happen in this and other threads. Please do not try to make yourself look like a saint.

[DarkFoon]

your one to talk. you create 99% of the flamewars that happen in this and other threads. Please do not try to make yourself look like a saint.
Let ye who is innocent cast the first stone...

Don't point fingers Chrono, you're no saint either.

[ChronoCross]

Let ye who is innocent cast the first stone...

Don't point fingers Chrono, you're no saint either.

I don't create the illusion of sainthood either. So I'm allowed to point out things like this.

[Sharktooth]

Well, there's no saints here. PPL use what they want, but PPL should also understand VFW is mantained by contributors and not by official devs.
PPL should understand VFW is not the right way to encode with x264 or any other AVC codec.
So any x264 VFW problem is secondary and it's not granted to be fixed or even looked into.
So posting about x264 VFW problems can only make us (the ones you call anti-vfw) swear to remove the x264 VFW completely from the project and that will only piss the devs...
Is it clear? Problems with VFW? you wont find the answer here...

[dragongodz]

Is it clear? Problems with VFW? you wont find the answer here...
no you are right. you will only find the same old blather over and over and over etc etc etc.

So any x264 VFW problem is secondary and it's not granted to be fixed or even looked into.
hmm isnt the sticky about vfw lacking certain features pointing to that ?

actually since bond seems to share your views(from his postings) i would suggest he make a sticky where all vfw/avi haters can post all the reasons they think its wrong etc etc etc. then you can simply point to that instead of this constant polluting of threads with the same stuff over and over.

[DarkFoon]

i would suggest [bond] make a sticky where all vfw/avi haters can post all the reasons they think its wrong etc etc etc. then you can simply point to that instead of this constant polluting of threads with the same stuff over and over.
I concur.

I also would promote a separate thread where proponents of VFW could post their problems, and people kind enough who are interested in helping (instead of preaching why VFW is bad) can offer assistance.
A thread title like "x264 VFW problems"

If somebody goofs and asks a VFW question here (in x264 dev), they should be pointed to the correct thread (x264 VFW), and their post moved there. The important part would be NOT flaming the person for their folly.
People seem to get so angry over this topic. It's just a software standard. But I guess some people need something to be upset with. However, I digress...

All this flaming on the topic is silly, and an administrator taking sides is unfortunate. That means that the moving of threads will not happen should somebody goof the topics, and instead a simple mistake (e.g. posting a VFW question in x264 dev)will re-ignite the flaming. People make mistakes; keeping our heads here seems difficult. Seriously, it's worse than the OpenBSD mailing lists: people get attacked for the smallest things there.

Honestly Sharktooth, I did not know that VFW was maintained by contributors, and not the official devs, until you said that. I wonder how many other people did not know that. Is that stated somewhere (obvious) where people will see it?

You also assume I am one of the "VFW people" as you call them, but I haven't stated my opinions on VFW.
I'm going to say it once:
I don't use VFW. I have no reason to. I have moved on, and no thanks to anybody ranting in doom9 about how bad VFW is and that MKV or MP4 is far superior to AVI. I came to my own realization at how cool MKV is. (actually, I was curious about what it was, and when I experimented with it, I found that I like it)
I wish there were a program like VirtualDub for MKV, I am convinced that would convert many people. But there is not, and who knows, maybe I'll write one in a few years.

[ChronoCross]

Also remember doom9 closed all the vfw help threads, feature request threads, and development threads.....so I kinda think the boards position on the subject is made.

[DarkFoon]

Well, then the VFW camp is screwed.
How unfortunate.

[dragongodz]

Also remember doom9 closed all the vfw help threads, feature request threads, and development threads.....so I kinda think the boards position on the subject is made.
ahh so now you can read minds too ? i have to assume that since no reason was given for the closure except in the case of people asking about features being added to the vfw version. in that case it was simply that it had been asked many times before and people asking again would infact be violating rule 1/1a.

however look at what those threads turned in to, exactly what you are seeing here now. nothing more than the same things being pushed by the exact same people. both pushing for vfw to be updated or pushing for people to stop using it do not really belong here. the first has been answered in a sticky, which opponents of vfw should be pointing out, instead of posting the same thing repeatedly, and the second should be stopped just as hard IMHO because it advances nothing. just pushes ,not suggests, a persons opinion on what others should do or use. you want to give real reasons then make 1 post, such as the sticky i suggested, and point to that. arguing or trying to ram your opinion down someones throat with multiple posts every time someone asks something will get you nowhere.

if all else fails you CAN ignore such posts ,as you have already been told.

[ChronoCross]

Your doing the same thing you protesting against. your telling me to not say anything about being anti-vfw. you are saying they have a right to talk. so basically your saying they can talk but I can't? I could remind them as many times as I want the problems with AVC in vfw. as long as there are people posting about it I will continue to advocate against it. Until both sides STFU completely I will continue to advocate for the cause.

[max-holz]

Which is the use of --enable-shared?

[ChronoCross]

--enable-shared build libx264.so

[akupenguin]

Which is the use of --enable-shared?
If you don't know, then it's not for you.

[max-holz]

If you don't know, then it's not for you.
As I can understand is not for win OS.

[squid_80]

So posting about x264 VFW problems can only make us (the ones you call anti-vfw) swear to remove the x264 VFW completely from the project and that will only piss the devs...
Removing vfw completely from x264 would be quite a disaster, since avisynth is vfw based... Strange that none of the anti-vfw posts have mentioned this. :sly:

[dragongodz]

Your doing the same thing you protesting against.
hmm so me asking for all this constant repeating of the same b.s. to stop is the same as what you are doing ? riiiight.

your telling me to not say anything about being anti-vfw. you are saying they have a right to talk. so basically your saying they can talk but I can't?
try actually reading what i typed instead of trying to say i said something i didnt.
i said to put your arguements in 1 thread, preferably a sticky, and point to that instead of these pointless arguements that keep going on and get nowhere. also you could then mention they would be breaking rule 1/1a, especially so if it was a sticky so stuck there for all to see.

as long as there are people posting about it I will continue to advocate against it. Until both sides STFU completely I will continue to advocate for the cause.
cause ? its now a crusade is it ? :)
nobody is asking you to like it and nobody is saying you have to answer questions about it. you do that on your own. however you also contribute greatly to this thread pollution whenever it starts. i have suggested what i think would be a better and cleaner way to handle it. if you dont like that idea then why not suggest a better way yourself, because all these repetative posts are just a waste of space and convices nobody of anything.

[akupenguin]

Removing vfw completely from x264 would be quite a disaster, since avisynth is vfw based... Strange that none of the anti-vfw posts have mentioned this.
LoadLibrary("avisynth.dll");
See avs2yuv for an implementation this way. No vfw involved, unless of course the script itself uses it, but that wouldn't be x264's problem.

[Sharktooth]

DarkFoon and dragongodz have you finished polluting this thread with you VFW bullshit?
No support for VFW here, and please stop discussing about it.
This thread is about x264 development and x264 VFW is not part of x264 development. it's mantained by contributors and actually there aren't any.
:search: :readrule: read the stickies and STFU, please.

[Guest]

@Sharktooth

Please read and follow forum rules, specifically, rule 4: be nice to each other, do not use profanities, etc.

http://forum.doom9.org/forum-rules.htm

[buzzqw]

please... fair play !
no offensive word or whatever to offence

BHH

[Sharktooth]

@Sharktooth

Please read and follow forum rules, specifically, rule 4: be nice to each other, do not use profanities, etc.

http://forum.doom9.org/forum-rules.htm
i played fair till now. there are stickies and other threads where discussing those things.
everytime i get here there are ppl whining about something that's cleartly wrong...
im sick of repeating always the same things (as other competent ppl do and keep doing).