#6408: Support Cisco Mediasense mov files with two h.264 streams
-------------------------------------+------------------------------------
Reporter: Gozde | Owner:
Type: enhancement | Status: reopened
Priority: wish | Component: avformat
Version: git-master | Resolution:
Keywords: mov h264 | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+------------------------------------
Comment (by cehoyos):
Replying to [comment:20 llogan]:
> I didn't investigate this, but I'm going to assume here that the file is
at fault.
Why do you think so?
(Especially without investigating.)
Or do you mean that whenever FFmpeg does not support a specific sample of
a supported file (or codec) format, the file is ''at fault''? I guess this
could be said but since we like samples, this is not a particular useful
approach if we want to improve FFmpeg.
> It is not possible to (and we shouldn't) support every broken format
from every broken encoder.
This is what we do (for more than a decade) and I believe there are
indications that we are very successful with this approach, despite the
''maintenance burden, code curn, log/mailing list/bug tracker noise''
(that I do not agree with).
I agree that the possible security issues were less important in the past
(and are more important now) but imo, that shouldn't stop us from trying
to fix issues and implement new features without introducing new security
issues.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/6408#comment:21>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
