DeathTheSheep United: x264 Guide and VfW Builds

[SergeyFedosov]

My sympathy to DeathTheSheep and CronoCross. By the way, Bond, I presume that you have a car. Do you know, that its engine was described in 1509 and industrially implemented in 1823? Since that time the only progress was associated with new metals, bigger cylinders, some electronics and polished surface. More or less the same about ships, trains, planes, electricity and encoding with VfW. Does this mean that you reject all the above items because of their obsolete technology? I am encoding since appearance of DivX slow/fast motion (was it 1998-1999?) and your position looks pretty bizarre to me.

[check]

The comparison of vfw to an engine is misleading - while the petrol engine has not yet been replaced with a newer version, vfw has. You would be better to compare it to the phase out of leaded petrol in favour of unleaded petrol.

[Egh]

Originally Posted by GodofaGap

I think an MP4source or MatroskaSource wouldn't be that different from DirectShowSource, since you'd still rely on DirectShow to do decoding. If you want to move away from DirectShowSource, perhaps something like ffmpegSource would be necessary.

To wrap up the discussion about alternatives to DSS().

I've spoken with Haali himself on the topic.

To sum up: atm he is not quite interested in the development of either MP4Source() or MKVSource() (or HaaliSource() to handle them all, as I suggested :P)

(But I guess if you beg him he might change his position :P)

He reminds ppl of his tool called mkv2vfr which from recent versions supports AVC video streams as well.

N.B. the reason avc is not quite suitable for VfW is "b-pyramide", this feature, to my knowledge, can't be correctly implemented on VfW.

[Sharktooth]

Originally Posted by G_M_C

Exactly what I ment, but I do want to be able to encode stuff in H264 through VirtualDub(mod).

"I want" are not the correct words. If "you want" then do it by yourself.
Pretending is the right way to get just nothing.

And ... i'm just used to doing things this way (been using virtualdub for so long now, i couldn't see myself switching easily ... maybe im finaly getting old )

so long the tools you used to encode are so old they're no longed supported. it's time to learn how to use new tools.
However as i said thousands of times, you can use the Vdub frameserving capability to feed the frames to x264 CLI (or even to megui), so you can get the best of both "worlds".

[tomos]

but how to edit mp4 files? i've tried avidemux but it doesnt work with large files from what i've tried. e.g 7gig file wont open but i cut a small (5mb) sample and that loaded fine.

[Sharktooth]

actually if avidemux doesnt open it, you cant. try splitting the file with mp4box then edit it. When you're done, rejoin the files.
However the problem exists also with AVI files (cant be bigger than 4 gigz) but that's an AVI limitation.

[xyloy]

He's talking about large MP4 files.

so long the tools you used to encode are so old they're no longed supported. it's time to learn how to use new tools.

If a tool works, why trash it... The choice should be left up to the user.

[G_M_C]

Originally Posted by Sharktooth

"I want" are not the correct words. If "you want" then do it by yourself.
Pretending is the right way to get just nothing.

so long the tools you used to encode are so old they're no longed supported. it's time to learn how to use new tools.
However as i said thousands of times, you can use the Vdub frameserving capability to feed the frames to x264 CLI (or even to megui), so you can get the best of both "worlds".

If you're not able to help me, or just plainly don't want to help, please dont react.

And the other case: Not everybody is from a country where English is the native language. So the "want" thing you are on about just might be some form of translational error, expressing my wish for some workable form of H264 encoding-posibillities in VDmod.

About VD(mod); I just like to work with those tools. They work just fine with my avisynth scripts & XviD encodings, because XviD encoding is the biggest bulk of stuff I do. And there was a new release of VDmod not to long ago, so it's not THAT old.

[DDogg]

G_M_C, take a look at this and let us know if that is a possible solution for you. We still need to update the information about whether colormatrix comes in to play as frameserving is rgb. Anybody that has a good grasp of that subject can update the wiki (correct, check?) Frameserving from VDM to x264 cli, or one of the GUI's, is a lot simpler than it might sound.

[SergeyFedosov]

G_M_C, just go to the site
http://gabextreme.googlepages.com/x264vfwunited
download x264 VfW and do whatever you wish with the codec and VDub.
A comment. Many inventors often forget about COMPATIBILITY with previously available technique (obsolete but customary). If something was started and became widespread, it is practically impossible to change the habitual way of things. Example: the letters on our keyboards are situated in the most stupid order just because the original typewriters had mechanical problems in typing, let us say, “the”. Yet, none of the attempts to make a more convenient layout succeeded.

[G_M_C]

Originally Posted by DDogg

G_M_C, take a look at this and let us know if that is a possible solution for you. We still need to update the information about whether colormatrix comes in to play as frameserving is rgb. Anybody that has a good grasp of that subject can update the wiki (correct, check?) Frameserving from VDM to x264 cli, or one of the GUI's, is a lot simpler than it might sound.

Originally Posted by SergeyFedosov

G_M_C, just go to the site
http://gabextreme.googlepages.com/x264vfwunited
download x264 VfW and do whatever you wish with the codec and VDub.

A comment. Many inventors often forget about COMPATIBILITY with previously available technique (obsolete but customary). If something was started and became widespread, it is practically impossible to change the habitual way of things. Example: the letters on our keyboards are situated in the most stupid order just because the original typewriters had mechanical problems in typing, let us say, “the”. Yet, none of the attempts to make a more convenient layout succeeded.

This is more or less the thought that occurred to me; Why should backwards compatibillity be thown overboard so easyly ? Think of the fact that (estimated) 80% of video-stuff is done bij amateurs that are happy using the product they got with their camera, wich happens to be based upon VfW codecs.

But enough about this pro vs. con argumenting; I'm gonna make some time of in the next few weeks to set up one of my computers to work with X264/H264. Maybe even try stuff like nVidia's PureVideo decoder and such (on my 7800GS plus). See if I can find out what works best, but from the standpoint that I have to be able to keep using AviSynth and all its filter-possibillities. Thx all for the insight

[check]

Originally Posted by SergeyFedosov

A comment. Many inventors often forget about COMPATIBILITY with previously available technique (obsolete but customary). If something was started and became widespread, it is practically impossible to change the habitual way of things. Example: the letters on our keyboards are situated in the most stupid order just because the original typewriters had mechanical problems in typing, let us say, “the”. Yet, none of the attempts to make a more convenient layout succeeded.

Another fallacy! Argumentum ad antiquitam - just because we have always done something one way does not mean it is right or correct. Just because it is customary to do things one way in no way validates future choices of similar decisions.
As to the second prong of your argument (change is hard), you forget that examples - by themself - prove nothing.

[GodofaGap]

We still need to update the information about whether colormatrix comes in to play as frameserving is rgb.

You don't need colormatrix, but you will need to use Converttoyv12 with the correct matrix for the encoder.

[Sharktooth]

Originally Posted by SergeyFedosov

G_M_C, just go to the site
http://gabextreme.googlepages.com/x264vfwunited
download x264 VfW and do whatever you wish with the codec and VDub.
A comment. Many inventors often forget about COMPATIBILITY with previously available technique (obsolete but customary). If something was started and became widespread, it is practically impossible to change the habitual way of things. Example: the letters on our keyboards are situated in the most stupid order just because the original typewriters had mechanical problems in typing, let us say, “the”. Yet, none of the attempts to make a more convenient layout succeeded.

To make what? A 7Gb AVI? Sorry its not possible...
Think before you speak.

[tomos]

Originally Posted by Sharktooth

To make what? A 7Gb AVI? Sorry its not possible...
Think before you speak.

7gb avi? yes it is possible. i know since i have one on my drive right now.

[GodofaGap]

Opendml avis can exceed the 2 GB standard AVI limit by a very large amount (~2^64-1 bytes (?))

[Sharktooth]

True, but AFAIK vdub(mod) isnt able to edit them.

[GodofaGap]

You are wrong. It would be pretty silly if VirtualDub couldn't read its own files right?

[Sharktooth]

it may be. it has been... well, a lot of time since i dont use vdub.
however i clearly remember it had problems with huge AVIs. Maybe things have changed with new versions.

[GodofaGap]

If you don't use and don't know a tool, don't talk about it. Very simple.