#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 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. Around 30% of my mpeg2 and h264 recordings fail copy remuxing
with ffmpeg. Even if I recode h264 to h264, there are problems with the
files. Yes I use MCEBuddy, but these problems are only related too ffmpeg.
>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. Ramit himself has posted that he is unsure whether MCEBuddy can
continue because of these changes. What ramit says about ffmpeg being
flexible is true, but as is also what he says about updating versions of
ffmpeg and certain changes causing new problems to arise.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2227#comment:31>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
