-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arm
hardware acceleration / NEON (libx264
)
#395
Comments
You'd have to check with x264 folks what kind of acceleration it has for your arch. |
@BtbN: Well, before you posted the comment, I manually built My expectations with using ARM/NEON had been a bit higher. In fact, I have really hoped that even a 2-core ARM CPU with NEON extensions allows the realtime re-encoding of a 2K H.264 stream (its flaky data necessitating a re-encode). I think I avoided this workaround now by updating the firmware of the stream source and some changes to the protocol and video-copy settings used. |
Not sure what specific device you got there, but even the latest Raspberry Pis will struggle with any kind of advanced software encoding. |
In this case it is an Amazon EC2 The |
The current
ffmpeg
build (from this repository) runs with 30fps on a relatively low-powered ARM Linux system, but withultrafast
preset. Any preset belowultrafast
results in much lower fps. How can I find out whether theffmpeg
build indeed uses thearm
processor hardware acceleration and NEON for H.264 re-encoding?Edit: Under
/proc/cpuinfo
asimd
is listed, which should be the same asneon
, just the older name for it.ffmpeg -buildconf
does not list--enable-neon
flag.The text was updated successfully, but these errors were encountered: