ffmpeg: Don't trigger url_interrupt_cb on the first signal
authorMartin Storsjö <martin@martin.st>
Sun, 22 May 2011 11:40:33 +0000 (14:40 +0300)
committerMartin Storsjö <martin@martin.st>
Sun, 22 May 2011 19:06:20 +0000 (22:06 +0300)
commita121754852a69b4879a39ba78863404c13c54f61
tree2bd8ad6642ff5913630ea02e4e0ca823326e2e93
parent8089b7fa8c5b5a48cc7101daa4be891d0ead5a5e
ffmpeg: Don't trigger url_interrupt_cb on the first signal

Currently, the url_interrupt_cb callback will abort all IO
after the first received signal. This makes the output files
from e.g. the mov muxer to be unreadable if the transcode is
aborted with ctrl+c.

After this patch, the first signal cleanly breaks out of
the transcoding loop, but won't forcibly abort all IO.
After the second signal is received, the url_interrupt_cb
callback will abort all IO.

Signed-off-by: Martin Storsjö <martin@martin.st>
ffmpeg.c