On Tue, May 14, 2019 at 10:31:00PM +0200, Marton Balint wrote:
>
>
> On Wed, 8 May 2019, Michael Niedermayer wrote:
>
> >On Tue, May 07, 2019 at 02:03:22AM +0200, Marton Balint wrote:
> >>
> >>
> >>On Tue, 7 May 2019, Michael Niedermayer wrote:
> >>
> >>>On Sun, May 05, 2019 at 08:51:08PM +0200,
On Wed, 8 May 2019, Michael Niedermayer wrote:
On Tue, May 07, 2019 at 02:03:22AM +0200, Marton Balint wrote:
On Tue, 7 May 2019, Michael Niedermayer wrote:
On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote:
This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6.
I don
>
> if you dont return 3 fields you break the normative specification. This
> speaks
> about the "output of the decoding process" not how to interpret the output.
>
> I bring MPEG2 up here because we dont do what the normative spec says
> because it doesnt make sense for us. It does make sense if y
On Tue, May 07, 2019 at 01:39:44AM +0200, Hendrik Leppkes wrote:
> On Tue, May 7, 2019 at 12:34 AM Michael Niedermayer
> wrote:
> >
> > On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote:
> > > This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6.
> > >
> > > I don't think it is
On Tue, May 07, 2019 at 02:03:22AM +0200, Marton Balint wrote:
>
>
> On Tue, 7 May 2019, Michael Niedermayer wrote:
>
> >On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote:
> >>This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6.
> >>
> >>I don't think it is a good idea to dr
On Tue, 7 May 2019, Michael Niedermayer wrote:
On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote:
This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6.
I don't think it is a good idea to drop frames from CFR input just because they
are duplicated, that can cause issues fo
On Tue, May 7, 2019 at 1:39 AM Hendrik Leppkes wrote:
>
> On Tue, May 7, 2019 at 12:34 AM Michael Niedermayer
> wrote:
> >
> > On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote:
> > > This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6.
> > >
> > > I don't think it is a good
On Tue, May 7, 2019 at 12:34 AM Michael Niedermayer
wrote:
>
> On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote:
> > This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6.
> >
> > I don't think it is a good idea to drop frames from CFR input just because
> > they
> > are dupli
On Sun, May 05, 2019 at 08:51:08PM +0200, Marton Balint wrote:
> This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6.
>
> I don't think it is a good idea to drop frames from CFR input just because
> they
> are duplicated, that can cause issues for API users expecting CFR input. Also
> it
On Sun, May 5, 2019 at 8:51 PM Marton Balint wrote:
>
> This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6.
>
> I don't think it is a good idea to drop frames from CFR input just because
> they
> are duplicated, that can cause issues for API users expecting CFR input. Also
> it can caus
Am So., 5. Mai 2019 um 20:51 Uhr schrieb Marton Balint :
>
> This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6.
>
> I don't think it is a good idea to drop frames from CFR input just because
> they
> are duplicated, that can cause issues for API users expecting CFR input. Also
> it can
This reverts commit a9dacdeea6168787a142209bd19fdd74aefc9dd6.
I don't think it is a good idea to drop frames from CFR input just because they
are duplicated, that can cause issues for API users expecting CFR input. Also
it can cause issues at the end of file, if the last frame is a duplicated
fram
12 matches
Mail list logo