[x264-devel] cpu capabilities: none

[BugMaster]

On Thu, 2 Dec 2010 17:33:50 -0200, Carlos Eduardo Moreira dos Santos wrote:
> Thank you. I compiled it myself and cpu is correctly detected.
> However, the output is trash, like a TV in a non-working channel and
> I can't figure out why. Besides that, it could not detect fps and
> resolution anymore, but I solved this last problem by renaming the
> file to *_widthxheigth.mpg and adding --fps option.

> Thank you

> On Thu, Dec 2, 2010 at 5:12 PM, Lou <lou at fakeoutdoorsman.com> wrote:
> On Thu, 2 Dec 2010 11:28:59 +0100
> James Darnley <james.darnley at gmail.com> wrote:

>> On 02/12/2010, Carlos Eduardo Moreira dos Santos
>> <cems at cemshost.com.br> wrote:
>> > x264 [info]: using cpu capabilities: none!
>> >
>> > Is this the expected behavior? My yasm version is much newer than
>> > others I've read to cause troubles in cpu detections. I've tried to
>> > force capabilities with --asm, but I did not find numbers for MMX
>> > and SSE.
>>
>> Stop using --disable-asm when compiling.

> This appears to be x264 from the repository. Looks like he already
> filed a bug report:

> [Bug 684198] [NEW] CPU extensions are not detected
> https://bugs.launchpad.net/ubuntu/+source/x264/+bug/684198

> To the OP: if you don't want to wait for an Ubuntu fix you can compile
> x264 yourself:

> HOWTO: Install and use the latest FFmpeg and x264
> http://ubuntuforums.org/showthread.php?t=786095

> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel


You probably compiled it without lavf support so it think that all you
give to it is uncompressed files. That is why it doesn't work with mpg
(it is compressed source).