On Mon, Mar 09, 2015 at 03:14:50PM +0100, Andreas Cadhalpun wrote:
> On 09.03.2015 13:59, Michael Niedermayer wrote:
> >i was thinking more about limiting the backward seek before resync
> >to the last resync position +1 if there was a previous resync
> >so that resync which moves forward could not
On 09.03.2015 13:59, Michael Niedermayer wrote:
i was thinking more about limiting the backward seek before resync
to the last resync position +1 if there was a previous resync
so that resync which moves forward could not end before. This would
avoid the failure and allow the demuxer to continue,
On Mon, Mar 09, 2015 at 12:17:38PM +0100, Andreas Cadhalpun wrote:
> On 09.03.2015 03:13, Michael Niedermayer wrote:
> >On Mon, Mar 09, 2015 at 12:04:13AM +0100, Andreas Cadhalpun wrote:
> >>Hi,
> >>
> >>some broken files can lead to an endless resync loop, which is
> >>avoided by attached patch.
>
On 09.03.2015 03:13, Michael Niedermayer wrote:
On Mon, Mar 09, 2015 at 12:04:13AM +0100, Andreas Cadhalpun wrote:
Hi,
some broken files can lead to an endless resync loop, which is
avoided by attached patch.
Best regards,
Andreas
ffmdec.c | 10 +-
1 file changed, 9 insertions(
On Mon, Mar 09, 2015 at 12:04:13AM +0100, Andreas Cadhalpun wrote:
> Hi,
>
> some broken files can lead to an endless resync loop, which is
> avoided by attached patch.
>
> Best regards,
> Andreas
> ffmdec.c | 10 +-
> 1 file changed, 9 insertions(+), 1 deletion(-)
> 048852d2d9b0c2515
