[FFmpeg-trac] #5041(undetermined:closed): ffmpeg hangs up during analyzing flv stream
FFmpeg
trac at avcodec.org
Fri Nov 27 12:22:34 CET 2015
#5041: ffmpeg hangs up during analyzing flv stream
-------------------------------------+-------------------------------------
Reporter: maxvgi | Owner:
Type: defect | Status: closed
Priority: normal | Component:
Version: git-master | undetermined
Keywords: http flv | Resolution:
Blocking: | worksforme
Analyzed by developer: 0 | Blocked By:
| Reproduced by developer: 0
-------------------------------------+-------------------------------------
Comment (by maxvgi):
Replying to [comment:6 cehoyos]:
> {{{
> $ ffmpeg -i http://admin:123890@91.202.204.9:89/h264.flv -probesize 1000
-analyzeduration 1 -vcodec copy 1.mp4
> }}}
Yes, I got that it works if you ommit option {{{-an}}}.
But I have several dozens of different multimedia sources. Some of them
have audio stream inside, others do not.
Is there any possibility to save just VIDEO stream from each of them using
the same command line for them all, or it is nessessary to check several
argument sets for ffmpeg each time multimedia source is created?
In the {{{ffmpeg N-73635-gfd4c87f}}} I used the following command line:
{{{
$ ffmpeg -i <URI> -vcodec copy -an 1.mp4
}}}
And all video streams were muxed to mp4, audio streams were ignored.
Then I tried to update ffmpeg to {{{N-76851-ga330430}}}. Everything works
fine, but the only one stream
{{{http://admin:123890@91.202.204.9:89/h264.flv}}} hangs up if the option
{{{-an}}} is present in command line.
As you understand, I cannot ommit the option {{{-an}}} from this command
line because I need to save only video from all other sources.
(Furthermore, I cannot save some audio codecs to mp4 and have not enough
CPU to transcode). Yes, it is possible to make several attempts to
download each stream using with different command lines, but it is rather
difficult to realize.
Is that a bug or feature? And the behaviour of which version of ffmpeg is
correct?
Should I continue using old {{{N-73635-gfd4c87f}}} or ask you to fix the
problem in the current version?
--
Ticket URL: <https://trac.ffmpeg.org/ticket/5041#comment:7>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list