x264 CLI MV prediction

[Sirber]

VFW version has much more mode. CLI only have:

* i4x4
* p8x8
* b8x8

Are those exemples or the only possible choice?

[akupenguin]

i4x4, p8x8, p4x4, b8x8 are the short names.
p8x8 = "8x16, 16x8 and 8x8 P-frame search"
and so on.

[Sirber]

if I understand well...

i4x4 = i4x4, i8x4, i4x8, i8x8, i4x16, i16x4, i8x16, i16x8, i16x16 ?

[akupenguin]

p8x8 = "8x16, 16x8 and 8x8 P-frame search"
p4x4 = "4x8, 8x4 and 4x4 P-frame search"
b8x8 = "8x16, 16x8 and 8x8 B-frame search"
i4x4 = "4x4 Intra search"

16x16 I, P, and B are always enabled. (in all frontends. What would it do if you didn't allow any macroblock types?)
8x8 Intra is part of high profile. I've got it mostly working, but it's not in svn yet.
There is no i8x4 or i16x8.
I haven't implemented b4x4, since it appears to be even less useful than p4x4.

[Sirber]

k, thanks for all these infos!

P.S.

I'm asking all this coz I'm implementing x264 CLI in RealAnime :D

http://www.detritus.qc.ca/forum/viewtopic.php?p=509#509

[akupenguin]

BTW, I would recommend removing exhaustive motion search from the list. UMHex (added 2 days ago) is several times faster, and there's rarely a measurable difference in quality (i.e. around .01 dB).

Your "Max MV" is really a "Max delta MV". (This could easily be confusing, since Nero has a "Max MV" option which does something else. That option is not configurable in x264 (always unlimited)).

And the "disable all CPU optimizations" really isn't something a user should see. Sure, most people are smart enough not to select an option that does nothing except make the encode 3 times slower, but it doesn't deserve screen realestate.

[Sirber]

BTW, I would recommend removing exhaustive motion search from the list. UMHex (added 2 days ago) is several times faster, and there's rarely a measurable difference in quality (i.e. around .01 dB).
Was it added to SVN? I'm building the UI with the features present in rev 239. Like RV10, I don't mind upgrading my UI to reflect codec changes :)
Your "Max MV" is really a "Max delta MV". (This could easily be confusing, since Nero has a "Max MV" option which does something else. That option is not configurable in x264 (always unlimited)).
I'll rename it! Thanks!
And the "disable all CPU optimizations" really isn't something a user should see. Sure, most people are smart enough not to select an option that does nothing except make the encode 3 times slower, but it doesn't deserve screen realestate.
I have space left, and it can be cool :D

[akupenguin]

Originally posted by Sirber
Was it added to SVN? I'm building the UI with the features present in rev 239. Like RV10, I don't mind upgrading my UI to reflect codec changes :)
rev238. (--me "umh")

I have space left, and it can be cool :D
Then I guess I have to add another feature to bump it off ;)

[Sirber]

Originally posted by akupenguin
rev238. (--me "umh")
I have it, not default yet.

Originally posted by akupenguin
Then I guess I have to add another feature to bump it off ;)
Then x264 will be no fun anymore. ;) Would be like forbidding silly walk...

http://unmediated.org/images/20041116_silly-walk.jpg

lol

[lexor]

this is sort of going off on a tangent, but I noticed that there doesn't seem to be an xvid like rate control present, where you tell it the time length and MB size to fit and it decides on the rate by itself, with x264 (I use vfw) you can only set the bitrate and I'm not sure how that supposed to work, specifically that doesn't seem to allow for final size prediction (if I allow bitrate variability, which by default is 60%).

So yeah, are there plans to add xvid like settings for bitrate? Or are they present in cli version somehow, and I should open up lamented DOS window?

[Sirber]

XviD can produce filesize based on the FPS and frame number from it's stat file. You can do the same using a bitrate calculator. About the rate control, CLI has lots of options to build it. You can even make your own equation.

[ChronoCross]

I'm guessing that perhaps lexor is asking if there are any plans to make a built in rate control for users who are not experts. Basically a more beginner friendly rate control in the vfw and CLI's. this could even possibly be an addon feature to your tool sirber.

[Sirber]

Yep. But the problem is that I don't understand curve equation much :)

[lexor]

Originally posted by Sirber
Yep. But the problem is that I don't understand curve equation much :)

what is this curve equation you speak of? is there some sort of math paper on this? (not programming, although I suppose that would be good too)

P.S. btw what I was asking for in above post was something like what I get if I click on Calc button in xvid vfw. but not 'couse I'm a noob and can't use cli, it's just that I have to stare/work with unix command prompt all day, I just can't take anymore command lines when I get home.

[Sirber]

Look "x264.exe -h" (can't paste now, I'm at work)

[JoeBG]

Originally posted by akupenguin
BTW, I would recommend removing exhaustive motion search from the list. UMHex (added 2 days ago) is several times faster, and there's rarely a measurable difference in quality (i.e. around .01 dB).


That´s really interesting I think. Faster and good is always very intersting :)

In the moment I use:
First pass
--analyse none
Second pass
--analyse all

Should I use:
First pass
-- analyse none
Second pass
-- analyse p8x8 --me "umh"

instead of this?

[Sirber]

no block size in analysis? why?