#2227: ffmpeg incorrectly identifying mjpeg as video stream instead of
attachment
-------------------------------------+-------------------------------------
Reporter: ramitbhalla | Owner:
Type: defect | Status: new
Priority: normal | Component:
Version: unspecified | undetermined
Keywords: wtv | Resolution:
Blocking: | Blocked By:
Analyzed by developer: 0 | Reproduced by developer: 0
-------------------------------------+-------------------------------------
Comment (by cehoyos):
Replying to [comment:31 dodgexander]:
> >Which recordings are unsupported?Please remember that this bug tracker
is only meant for FFmpeg reports (not for third-party programs).
>
> Take a look at some of the cases related to .wtv files that ramitbhalla
has created.
Most of them were fixed iirc (one is the reason for this "ticket").
> Around 30% of my mpeg2 and h264 recordings fail copy remuxing with
ffmpeg.
This is not unexpected (and not wtv-related) for h264, in any case, these
are not regressions.
> Even if I recode h264 to h264, there are problems with the files.
Could you point me to the ticket?
> >Could you elaborate? I don't think support for any files was ever
dropped from FFmpeg.
>
> The changes explained in this thread by ramit explain why there is a
problem.
Please understand that -map 0 simply cannot work the way you want it (see
also #1952): Generally, you have to use specific map options depending on
the input file (and in this case, it should be trivial to provide them
with a simple script). I would also expect that in many cases, one video
and one audio track will already be what the users want.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2227#comment:32>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
