On Sun, Apr 17, 2016 at 06:53:58PM +0100, Rostislav Pehlivanov wrote:
> On 17 April 2016 at 03:40, Michael Niedermayer
> wrote:
>
> >
> > is this a spec compliance or a profile compliance issue or something
> > else ?
> >
> > from just the Commit message above it sounds a bit like a profile /
> >
On 17 April 2016 at 03:40, Michael Niedermayer
wrote:
>
> is this a spec compliance or a profile compliance issue or something
> else ?
>
> from just the Commit message above it sounds a bit like a profile /
> hw decoder limitation, in which case this patch with a different
> av_log() message sho
On Wed, Mar 02, 2016 at 01:14:52PM +, Rostislav Pehlivanov wrote:
> This commit is up for discussion.
>
> Requiring the user to reduce the strictness just to encode some random
> file (which decodes fine in all implementations except 1) isn't helping
> the encoder at all. The encoder needs to
This commit is up for discussion.
Requiring the user to reduce the strictness just to encode some random
file (which decodes fine in all implementations except 1) isn't helping
the encoder at all. The encoder needs to be used to get bug reports and
to be improved by multiple people. Only supportin
