On 14.06.2015 18:48, Luca Barbato wrote:
> On 14/06/15 17:31, Andreas Cadhalpun wrote:
>> On 14.06.2015 16:46, Luca Barbato wrote:
>>> Sadly some codecs such as vdpau (thanks to wm4 for spotting) would
>>> possibly break if those parameters aren't set to the current decoding
>>> decoding set, so setting avctx->{those} to the last outputted frame
>>> could probably cause more problems.
>>
>> That'd be unfortunate. What issues could it cause for vdpau?
>
> They coded dimension seem to be used for allocation so I guess would be
> quite problematic.
So if I understood that correctly the API user has to allocate a buffer
for the vdpau decoder based on coded_with/coded_height. So the values have
to be for the next frame and can't be for the last, if there is any
difference between these two.
That unfortunately makes completely fixing the problem in libavcodec
rather impossible...
Best regards,
Andreas
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
