[FFmpeg-devel] [PATCH 3/5] lavf: replace FFERROR_REDO with AVERROR(EAGAIN)

[Paul B Mahol]

On 11/9/22, Nicolas George <george at nsup.org> wrote:
> Anton Khirnov (12022-11-08):
>> Sure, and that's about it. And as I said before - there is no way to
>> tell when a device will be ready, so this is of very limited usefulness.
>
> This is not true for many devices. Sorry to contradict you once again,
> but you would know it if you had any experience working with devices.
>
>> That is not a meaningful difference. A meaningful difference would be
>> one that has actionable consequences.
>
> Well, it has actionable consequences: if you treat EAGAIN like REDO you
> introduce a busy wait, and if you treat REDO like EAGAIN you introduce a
> significant slowness. Now that you make me mention it, I remember it was
> precisely the reason I introduced REDO: to fix a slowness in resyncs.
>


I'm not interested in REDO / EAGAIN differences.
Can this bug be fixed at all?

> --
>   Nicolas George
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>