Hardware accelerated decoding issue

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Hardware accelerated decoding issue

Chih-Wei Huang
Hello,
I'm trying to use ffmpeg as a stagefright plugin of android-x86
to enable the hardware accelerated decoding via libva.
I'm using ffmpeg 3.1 and the latest libva and vaapi
from the master branch of Intel's repo.

Refer to the WIP branches:
https://github.com/meijjaa/android_external_ffmpeg/tree/cm-14.1-x86-n3.1.5
https://github.com/meijjaa/android_external_stagefright-plugins/tree/cm-14.1-x86_n3.1

https://github.com/cwhuang/libva
https://github.com/cwhuang/intel-vaapi-driver


Basically speaking, it works.
The video playback becomes smooth and
cpu load is lower as expected.
However, it's not stable enough.
Playback may suddenly stop.

I notice one strange log comes from ffmpeg:

04-09 21:47:13.832  1414  2860 I FFMPEG  : [h264 @ 0xb3e04400]
Hardware accelerated decoding with frame threading is known to be
unstable and its use is discouraged.


What does it mean and how to avoid that?


--
Chih-Wei
Android-x86 project
http://www.android-x86.org
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Hardware accelerated decoding issue

Moritz Barsnick
On Tue, Apr 11, 2017 at 11:08:52 +0800, Chih-Wei Huang wrote:
> I'm using ffmpeg 3.1 [...]

May I ask why?

> I notice one strange log comes from ffmpeg:
>
> 04-09 21:47:13.832  1414  2860 I FFMPEG  : [h264 @ 0xb3e04400]
> Hardware accelerated decoding with frame threading is known to be
> unstable and its use is discouraged.
>
> What does it mean and how to avoid that?

It means exactly that. You obviously avoid it by not using frame
threading.

Actually, that warning was removed quite recently, in commit
66963d4b8d302611553e7928063c1cb2ff0efdff, probably due to the changes
done quite some time before, perhaps up to commit
e0cd598bc4684654d63942e9ff4872c0b48a7dc2. I don't see either of these
commits in any release branch of ffmpeg. So, to profit from these
improvements, you may want to use ffmpeg git master HEAD instead of
your (quite old) release.

Moritz
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Loading...