[FFmpeg-trac] #4243(ffmpeg:new): Some streams are being closed without a reason in latest ffmpeg
FFmpeg
trac at avcodec.org
Sat Jan 10 19:43:40 CET 2015
#4243: Some streams are being closed without a reason in latest ffmpeg
------------------------------------+----------------------------------
Reporter: BlackDream | Owner:
Type: defect | Status: new
Priority: normal | Component: ffmpeg
Version: git-master | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
------------------------------------+----------------------------------
Comment (by BlackDream):
I have no idea how to use bitsect currently so i have to find someone else
to do that for me.
MPEGS/HLS the same happens it's not muxer related.
Yes i can make it work without -re it's not a problem for me. But since in
the ffmpeg v2.4.x that wasn't exists i guess it could be a bug so i posted
here to be fixed.
The problem is i can't provide sample because with a "static file" that
doesn't happen. It only happens remotely.
For example if i take the TESTED stream above using wget (since it comes
from HTTP protocol) and save it into a file, then if i use ffmpeg to
remuxing into mpegts i don't get any error.
'''So the problem should be using the -re and when the host is remote.'''
I also tried using FFmpeg 2.5.0 and same happens, so i guess it must be
something that changed regarding this v2.4.5 and v2.5.0.
I will try to find someone to bitsect it for me
Thank you
--
Ticket URL: <https://trac.ffmpeg.org/ticket/4243#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list