View Full Version : x264 not using cpu capabilities?
Eretria-chan
17th April 2010, 17:52
Everytime I use x264, it only says that it uses:
x264 [info]: using cpu capabilities: MMX2 Cache64
Yet, I know the cpu has capbility for SSE1/2/3 since it's a Core 2 Duo. These are builds from x264.nl.
Is this normal or am I missing something?
:thanks:
Dark Shikari
17th April 2010, 19:11
Sounds more like a Core Duo to me.
Eretria-chan
17th April 2010, 19:14
Is there a difference?
Cpu-Z lists the CPU as Intel Core Duo T2400 type: Yonah.
It also lists it supporting MMX, SSE1/2/3, VT-x.
Dark Shikari
17th April 2010, 19:18
Is there a difference?The Core 1 is a pile of crap with the world's slowest SSE unit. The Core 2 is pure concentrated awesome in silicon form.
Eretria-chan
17th April 2010, 19:20
Heh. I see.
I take it the CPU I am stuck with is this piece of crap unit, and that might explain why SSE isn't used?
nurbs
17th April 2010, 19:25
It isn't used because doing the function in SSE would be slower than the MMX version.
Eretria-chan
17th April 2010, 19:26
Ah, I see. So basically it's just a matter of sacrificing quality to bring up speed, then.
nurbs
17th April 2010, 19:31
It's not about quality. Lets say with your CPU encoding a frame using only the MMX optimized functions takes 1 second and encoding it using SSE would take 1.05 seconds. Using SSE you'd get exactly the same output, only slower.
Eretria-chan
17th April 2010, 19:33
I know, I didn't mean that. I meant that I have to use faster x264 settings to get the encode done at a sane time (to bump of encoding speed).
Lyle_JP
18th April 2010, 18:42
Well, if encode time is the one immutable factor for you, then yes, your processor will give inferior encoding results.
Eretria-chan
18th April 2010, 19:06
I cannot wait forever for the encodes to complete, because I have finite space and I need to record new videos on an almost daily basis, so yes, encoding speed is a factor.
Buying a new processor is out of the question, so lessening the settings is the only solution here, which is why I asked.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.