Re: [FFmpeg-devel] [PATCHv2 2/3] ffplay: convert to new decode API

2017-03-22 Thread Philip Langdale
On Tue, 21 Mar 2017 07:34:32 -0700 Philip Langdale wrote: > On Mon, 20 Mar 2017 21:51:49 +0100 > Marton Balint wrote: > > > Since subtitles are not yet supported with the new API, > > CODEC_CAP_DELAY subtitle codecs (only libzvbi so far) may loose the > > last few buffered frames in the end of

Re: [FFmpeg-devel] [PATCHv2 2/3] ffplay: convert to new decode API

2017-03-21 Thread wm4
On Tue, 21 Mar 2017 07:34:32 -0700 Philip Langdale wrote: > On Mon, 20 Mar 2017 21:51:49 +0100 > Marton Balint wrote: > > > Since subtitles are not yet supported with the new API, > > CODEC_CAP_DELAY subtitle codecs (only libzvbi so far) may loose the > > last few buffered frames in the end of

Re: [FFmpeg-devel] [PATCHv2 2/3] ffplay: convert to new decode API

2017-03-21 Thread Philip Langdale
On Mon, 20 Mar 2017 21:51:49 +0100 Marton Balint wrote: > Since subtitles are not yet supported with the new API, > CODEC_CAP_DELAY subtitle codecs (only libzvbi so far) may loose the > last few buffered frames in the end of the stream. > > The impact of this is so limited, it seemded better to

[FFmpeg-devel] [PATCHv2 2/3] ffplay: convert to new decode API

2017-03-20 Thread Marton Balint
Since subtitles are not yet supported with the new API, CODEC_CAP_DELAY subtitle codecs (only libzvbi so far) may loose the last few buffered frames in the end of the stream. The impact of this is so limited, it seemded better to accept it than losing the simplification benefits of the new API. S