[FFmpeg-trac] #6408(avformat:reopened): Support Cisco Mediasense mov files with two h.264 streams

FFmpeg trac at avcodec.org
Fri Jun 30 20:17:09 EEST 2017


#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 llogan):

 This is the current state. I'll quote another developer, wm4:

 > FFmpeg is a project by volunteers and open source enthusiasts (with some
 people being paid for implementing specific features or fixing specific
 bugs), so there is no planning, no roadmaps, no project management, no
 predictable behavior, no guarantees, and no official responses of any
 kind.

 I didn't investigate this, but I'm going to assume here that the file is
 at fault. It is not possible to (and we shouldn't) support every broken
 format from every broken encoder. Supporting each encountered oddball
 proprietary variant increases the maintenance burden, code churn,
 log/mailing list/bug tracker noise, possible security issues, wastes
 developers' time, and puts the expectation on FFmpeg to always decode
 absolutely everything instead of users demanding that manufacturers
 provide usable, standard outputs.

 Since contacting Cisco is likely a waste of time your best bet may be to
 provide a patch that fixes your issue, but I know that this is not a
 realistic suggestion for the average user.

 Offering a financial bounty may increase the chances of this getting
 someone's attention who may find it interesting enough to implement a
 workaround, but it is not guaranteed.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/6408#comment:20>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list