On Wed, 4 Oct 2017 23:27:18 +0100
Mark Thompson wrote:
> On 04/10/17 23:16, wm4 wrote:
> > On Wed, 4 Oct 2017 23:01:47 +0100
> > Mark Thompson wrote:
> >>>
> >>> In addition to this, should there be an AVCodec flag that tells the API
> >>> user whether this decoder can do half-transparent soft
On 04/10/17 23:16, wm4 wrote:
> On Wed, 4 Oct 2017 23:01:47 +0100
> Mark Thompson wrote:
>>>
>>> In addition to this, should there be an AVCodec flag that tells the API
>>> user whether this decoder can do half-transparent software fallback?
>>> Half-transparent as in it can call get_format mid-st
On Wed, 4 Oct 2017 23:01:47 +0100
Mark Thompson wrote:
> >
> > In addition to this, should there be an AVCodec flag that tells the API
> > user whether this decoder can do half-transparent software fallback?
> > Half-transparent as in it can call get_format mid-stream to reconfigure
> > it to s
On 04/10/17 09:49, wm4 wrote:
> On Wed, 4 Oct 2017 09:07:10 +0100
> Mark Thompson wrote:
>
>> ---
>> doc/APIchanges | 3 +++
>> libavcodec/avcodec.h | 74
>>
>> libavcodec/utils.c | 11
>> 3 files changed, 88 insertions(+)
On Wed, 4 Oct 2017 09:07:10 +0100
Mark Thompson wrote:
> ---
> doc/APIchanges | 3 +++
> libavcodec/avcodec.h | 74
>
> libavcodec/utils.c | 11
> 3 files changed, 88 insertions(+)
>
> diff --git a/doc/APIchanges b/doc/API
---
doc/APIchanges | 3 +++
libavcodec/avcodec.h | 74
libavcodec/utils.c | 11
3 files changed, 88 insertions(+)
diff --git a/doc/APIchanges b/doc/APIchanges
index fa27007f4..80a8ac1fa 100644
--- a/doc/APIchanges
+++ b/doc/AP