Rainer Hochecker online.de> writes:
> I don't know why nobody cared about this so far.
A possible explanation is that not all new hardware
supports vda at all...
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mail
Hendrik Leppkes gmail.com> writes:
>
> On Wed, Apr 1, 2015 at 12:40 PM, Rainer Hochecker
> online.de>
wrote:
> > vda wants the entire buffer with all info. it has no other means to deliver
> > picture parameters.
> > according to documentation start_frame can pass the entire buffer
>
> This
On Wed, Apr 1, 2015 at 10:10 PM, Hendrik Leppkes
wrote:
> On Wed, Apr 1, 2015 at 12:40 PM, Rainer Hochecker
> wrote:
> > vda wants the entire buffer with all info. it has no other means to
> deliver
> > picture parameters.
> > according to documentation start_frame can pass the entire buffer
>
>
Hendrik Leppkes gmail.com> writes:
> On Wed, Apr 1, 2015 at 12:40 PM, Rainer Hochecker wrote:
> > vda wants the entire buffer with all info. it has no
> > other means to deliver picture parameters.
> > according to documentation start_frame can pass the
> > entire buffer
>
> This doesn't make
On Wed, Apr 1, 2015 at 12:40 PM, Rainer Hochecker wrote:
> vda wants the entire buffer with all info. it has no other means to deliver
> picture parameters.
> according to documentation start_frame can pass the entire buffer
This doesn't make much sense. If I follow that argument, then vda
would
vda wants the entire buffer with all info. it has no other means to deliver
picture parameters.
according to documentation start_frame can pass the entire buffer
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmp
