On Fri, 25 Sep 2015 14:43:37 +0200
Alexis Ballier wrote:
> On Fri, 25 Sep 2015 12:22:51 +0200
> Clément Bœsch wrote:
>
> > Hi,
> >
> > With the increasing number of hardware accelerated API, the need for a
> > proper M:N asynchronous API is growing. We've observed that with MMAL
> > and VideoT
Le quartidi 4 vendémiaire, an CCXXIV, Alexis Ballier a écrit :
> - Why not merging AVPacket into AVFrame ? This would restore the
> symmetry between encoding and decoding. This is actually what V4L
> does.
I would gladly support that.
> - This could go one step further with a lavfi wrapper: d
On Fri, 25 Sep 2015 12:22:51 +0200
Clément Bœsch wrote:
> Hi,
>
> With the increasing number of hardware accelerated API, the need for a
> proper M:N asynchronous API is growing. We've observed that with MMAL
> and VideoToolBox accelerations typically. Similarly, the incoming
> MediaCodec hwacce
Hi,
On Fri, Sep 25, 2015 at 6:22 AM, Clément Bœsch wrote:
> Hi,
>
> With the increasing number of hardware accelerated API, the need for a
> proper M:N asynchronous API is growing. We've observed that with MMAL and
> VideoToolBox accelerations typically. Similarly, the incoming MediaCodec
> hwac
Hi,
With the increasing number of hardware accelerated API, the need for a
proper M:N asynchronous API is growing. We've observed that with MMAL and
VideoToolBox accelerations typically. Similarly, the incoming MediaCodec
hwaccel is going to suffer from the same limitations.
Some Libav developers
