#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: | Resolution:
Blocking: | Blocked By:
Analyzed by developer: 0 | Reproduced by developer: 0
-------------------------------------+-------------------------------------
Comment (by ramitbhalla):
That's what I said - mjpeg were identified as attachment in the Dec 21st
build and everything was fine.
Now its being identified as video which is causing everything to go nuts.
Don't get me wrong, I love ffmpeg and think you guys are FAB. But I'm
afraid of updating ffmpeg - I need to start testing over because one tiny
change breaks everything.
if mjpeg can't be transcoded into more standard video forms perhaps the
earlier method of identifying it as attachment was the best strategy. This
is just very complicated to figure out. How many conditions can I put to
see what can and can't be converted? Why I loved ffmpeg is that it keep
that stuff internal, I can stick to simple commands like vcodec and map
without having to worry about the intricacies of the interoperability
which ffmpeg takes care of beautifully.
I don't understand why you decided to make mjpeg a video instead of
attachment?
I'm sorry but this is a deal breaker since everything has stopped working
and I don't see any way around it.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2227#comment:6>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
