#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:38 dodgexander]:
> @ cehyos
>
> >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").
>
> Take a look at this ticket[https://ffmpeg.org/trac/ffmpeg/ticket/2220].
It hasn't been fixed.
I am not convinced this ticket is wtv-related (and it does not contradict
my claim that most tickets were fixed).
> >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.
>
> The remaining mpeg2 fails I have are related to this ticket.
Please allow me to repeat: I don't think there is an issue, -map 0 does
not work the way you seem to expect (and it generally cannot work the way
you expect), simply remove it from your command line.
> The h264 fails are mainly due to the ticket listed above.
>
> >>Even if I recode h264 to h264, there are problems with the files.
> >Could you point me to the ticket?
>
> I shall open a ticket with an example.
Please do so.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2227#comment:39>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
