Opened 2 months ago

Closed 2 months ago

#10897 closed defect (duplicate)

Assertion best_input >= 0 failed at fftools/ffmpeg_filter.c:1909

Reported by: Andreas Owned by:
Priority: normal Component: undetermined
Version: unspecified Keywords:
Cc: Andreas Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

Summary of the bug:

I use a quite complicated filter expression to extract parts of a video and time-stretch these parts. It works fine with ffmpeg 4.0.2, but no longer in 6: 6.1 release loops forever and a recent build from master throws the above assertion error.

How to reproduce:

Run the commandline found in the log files - it is always the same command. I provide log files for 4.0.2 where it works, for 6.1 where I terminate the infinite loop via Ctrl+C after 10 minutes or so, and master with the assertion error.

The problem is not related to the input video, I tried the same commandline with different videos, the result is always the same. For completeness you find one of the videos here: https://a-voss.de/ffmpeg/

It is also not platform dependent, I tried in Windows and Linux.

Attachments (5)

ffmpeg-4.0.2.log.gz (1.5 MB ) - added by Andreas 2 months ago.
ffmpeg-4.0.2-console.log.gz (7.4 KB ) - added by Andreas 2 months ago.
What was printed to the console
ffmpeg-6.1.log.gz (1003.1 KB ) - added by Andreas 2 months ago.
ffmpeg-6.1-console.log.gz (11.2 KB ) - added by Andreas 2 months ago.
What was printed to the console
ffmpeg-master.log.gz (955.0 KB ) - added by Andreas 2 months ago.

Change History (6)

by Andreas, 2 months ago

Attachment: ffmpeg-4.0.2.log.gz added

by Andreas, 2 months ago

Attachment: ffmpeg-4.0.2-console.log.gz added

What was printed to the console

by Andreas, 2 months ago

Attachment: ffmpeg-6.1.log.gz added

by Andreas, 2 months ago

Attachment: ffmpeg-6.1-console.log.gz added

What was printed to the console

by Andreas, 2 months ago

Attachment: ffmpeg-master.log.gz added

comment:1 by Gyan, 2 months ago

Resolution: duplicate
Status: newclosed

Duplicate of #10795

Note: See TracTickets for help on using tickets.