On Wed, 25 Jun 2025, Michael Niedermayer wrote:
On Tue, Jun 24, 2025 at 09:23:10PM +0200, Marton Balint wrote:
It was never reliable to detect if a filtergraph have sources, because a filter
can act as a source only after some time, for example the loop filter.
So it is better to remove the source detection entirely and always give the
scheduler an oppurtunity to stop processing.
Fixes ticket #11604.
Signed-off-by: Marton Balint <c...@passwd.hu>
---
fftools/ffmpeg_filter.c | 25 ++++---------------------
1 file changed, 4 insertions(+), 21 deletions(-)
breaks: (infinite loop)
./ffmpeg -y -i tickets//507/avdesync_cut.avi -bitexact -af
aresample=first_pts=-50000 -r 24000/1001 -t 145 out.avi
sample seems attached to the ticket: https://trac.ffmpeg.org/ticket/507
Seems like an issue already present before the patch series if "sources"
were used, because this hangs for me even without the patch series:
ffmpeg -threads 16 -i avdesync_cut.avi -bitexact -af
aresample=first_pts=100,apad=pad_len=1000 -f null none
I have no better idea than to drop this patch until this is figured out,
because this issue would become more common if all filters are going to be
treated as sources...
Regards,
Marton
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
