#1341: ffmpeg -async 1 broken for wmv files
------------------------------------+----------------------------------
Reporter: maccara | Owner:
Type: defect | Status: new
Priority: normal | Component: FFmpeg
Version: git-master | Resolution:
Keywords: async | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
------------------------------------+----------------------------------
Comment (by maccara):
For this particular sample async probably is not needed - this specific
sample was just to show the errors generated if -async 1 was used (and
easy accessibility for the file). Whether async needed for this sample is
completely besides the point; it still should not break when async is
used.
The real use case is for batch converting stuff with some audio processing
where it is much simpler to handle remuxing etc if the audio has the added
silence/cut in the beginning. Also, it did no harm even if the file did
not specifically need async in the first place.
So "this particular file is not needing async" is not a solution for when
I have to deal with a file that actually does need it. ;)
Thanks for pointing out the relevant commits. Seems indeed async has been
broken since fc49f22 (at least) and 9d30a96 just exposes the regression by
converting the async parameter to the new filtering method. I did a quick
test by directly invoking -af
aresample=min_comp=0.001:min_hard_comp=0.100000 instead of -async 1 and
the errors are the same. I wonder if aresample has ever worked for wmv
files? (haven't been able to test further yet)
However, current behavior can't be the intended outcome and is a
regression compared to old behavior with async before aresample.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1341#comment:2>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
