On Friday, 9 January 2015 22:09:20 UTC+5:30, Aubin REBILLAT wrote:
> Hi Kenz,
>
>
> I managed to make my VideoDecodeAccelerator work correctly so for now i will not attempt another method.
> Nevertheless, this is really interresting and i will take a closer look at it in the near future.
>
>
> Thank you for your help.
>
>
> On Thu, Jan 8, 2015 at 7:33 PM, kenz kiran <
kira...@gmail.com> wrote:
>
>
>
> Aubin,
>
> I found the best way to move from FFMPEG (software video decoding) to HW Accelerated Video decoding (Software doesn't create, manipulate video frames) was using StreamTextures. Check out how Android Renders HTML Video.
>
>
> Basically, if you have a GPU that supports EGLImageExternal extension (
https://www.khronos.org/registry/gles/extensions/OES/OES_EGL_image_external.txt). and a VPU splitting out any YUV format, then you would get a zero-copy video rendering.
>
>
> Chrome already has the necessary fragment shaders for video textures provided in NV12 format. (if I remember correctly).
>
>
> If it is of any help, here is a diagram for chrome android html5 video (albeit old by an year, things could have changed).
>
>
>
>
>
I am trying to hardware accelerate video decoding for chromium browser. As far I know there are three components in Chromium for Video rendering,
1. Pipeline
2. ffmpeg
3. Webkit
For hardware acceleration, I am contemplating to change ffmpeg to use VPU. Can you please let me know what are steps that you carried out for hardware acceleration? Does ffmpeg expects standard APIs from underlying decoder?