FFmpeg | 7 Feb 21:29 2016

#5222(undetermined:new): ffmpeg crashing for large “-filter_complex_script” inputs

#5222: ffmpeg crashing for large “-filter_complex_script” inputs
-------------------------------------+-------------------------------------
             Reporter:  jsniff       |                     Type:  defect
               Status:  new          |                 Priority:  important
            Component:               |                  Version:
  undetermined                       |  unspecified
             Keywords:  ffmpeg,      |               Blocked By:
  video, crash                       |  Reproduced by developer:  0
             Blocking:               |
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 We're experiencing an issue where ffmpeg seg faults for very large
 "-filter_complex_script" input files (roughly 3MB). The input file
 consists of a very large number of drawbox filters. The same processing
 pipeline works fine for smaller files, but seems to have an issue as the
 file size increases. Is there a hard limit to how large this file can be?
 If so, is there a "magic number" somewhere that we can increase and re-
 compile from source?

 Does anyone have any other thoughts or advice?

 Thanks in advance!

--
Ticket URL: <https://trac.ffmpeg.org/ticket/5222>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
(Continue reading)

FFmpeg | 6 Feb 22:08 2016

#5221(ffmpeg:new): libx264 drops 2 starting frames

#5221: libx264 drops 2 starting frames
-----------------------------------+---------------------------------------
             Reporter:  renderTom  |                     Type:  defect
               Status:  new        |                 Priority:  critical
            Component:  ffmpeg     |                  Version:  unspecified
             Keywords:             |               Blocked By:
             Blocking:             |  Reproduced by developer:  0
Analyzed by developer:  0          |
-----------------------------------+---------------------------------------
 Transcoding from mp4 (and proRes) 24fps file to h264 mov file.
 Resulting video drops 2 starting frames, as if original video started from
 frame 2.

 Summary of the bug:
 How to reproduce:
 {{{
 % ffmpeg -i INPUT -an -sn -vcodec libx264 -crf 18 -pix_fmt yuv420p
 OUTPUT.MOV
 ffmpeg version N-78512-g4c573f8-tessus
 tested on MacOSX 10.10.5
 }}}
 Patches should be submitted to the ffmpeg-devel mailing list and not this
 bug tracker.

 Here's a log
 {{{
 Tomass-iMac:~ renderTom$ /ffmpeg -i /Volumes/renderTom\
 HD/\!_Projects/Other\ projects/\!_Prior/17\ Misconduct/1\
 Incoming/Video/Misconduct_trailer_23_976_HD_FilmBridge_ProRes.mov -an -sn
 -vcodec libx264 -crf 18 -pix_fmt yuv420p /Volumes/renderTom\
(Continue reading)

FFmpeg | 6 Feb 20:57 2016

Re: #3657(swscale:open): float pixel format

#3657: float pixel format
-------------------------------------+-----------------------------------
             Reporter:  sun          |                    Owner:
                 Type:  enhancement  |                   Status:  open
             Priority:  wish         |                Component:  swscale
              Version:  git-master   |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-----------------------------------

Comment (by gjdfgh):

 Certainly more usage than "important" formats like MONOWHITE.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3657#comment:12>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
FFmpeg | 6 Feb 20:48 2016

Re: #3657(swscale:open): float pixel format

#3657: float pixel format
-------------------------------------+-----------------------------------
             Reporter:  sun          |                    Owner:
                 Type:  enhancement  |                   Status:  open
             Priority:  wish         |                Component:  swscale
              Version:  git-master   |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-----------------------------------

Comment (by richardpl):

 To amuse people. like you.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3657#comment:11>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
FFmpeg | 6 Feb 20:41 2016

Re: #3657(swscale:open): float pixel format

#3657: float pixel format
-------------------------------------+-----------------------------------
             Reporter:  sun          |                    Owner:
                 Type:  enhancement  |                   Status:  open
             Priority:  wish         |                Component:  swscale
              Version:  git-master   |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-----------------------------------

Comment (by cehoyos):

 Replying to [comment:9 omerjerk]:
 > Replying to [comment:8 cehoyos]:
 > > Replying to [comment:7 omerjerk]:
 > > > I'd love to start with this.
 > > How would you use the pix_fmt after adding it to libavutil?
 >
 > I went through some of the code present in utils.c file in libswscale.
 > I'm not really sure how difficult this feature is.
 Allow me to repeat my question:
 Once you have mastered all difficulties and added the new pixel format to
 libavutil and libswscale, what usage would the new pix_fmt have within
 FFmpeg?

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3657#comment:10>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
(Continue reading)

FFmpeg | 6 Feb 19:39 2016

Re: #3657(swscale:open): float pixel format

#3657: float pixel format
-------------------------------------+-----------------------------------
             Reporter:  sun          |                    Owner:
                 Type:  enhancement  |                   Status:  open
             Priority:  wish         |                Component:  swscale
              Version:  git-master   |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-----------------------------------

Comment (by omerjerk):

 Replying to [comment:8 cehoyos]:
 > Replying to [comment:7 omerjerk]:
 > > I'd love to start with this.
 > How would you use the pix_fmt after adding it to libavutil?

 I went through some of the code present in utils.c file in libswscale.
 I'm not really sure how difficult this feature is.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3657#comment:9>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
(Continue reading)

FFmpeg | 6 Feb 10:11 2016

Re: #1102(avformat:open): mxf separate fields in interlaced j2k

#1102: mxf separate fields in interlaced j2k
------------------------------------+------------------------------------
             Reporter:  zhukov      |                    Owner:  mateo
                 Type:  defect      |                   Status:  open
             Priority:  normal      |                Component:  avformat
              Version:  git-master  |               Resolution:
             Keywords:  mxf j2k     |               Blocked By:
             Blocking:              |  Reproduced by developer:  1
Analyzed by developer:  1           |
------------------------------------+------------------------------------

Comment (by cehoyos):

 I believe that the following sample has the same issue:
 http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket2817/warehouse.mxf

--
Ticket URL: <https://trac.ffmpeg.org/ticket/1102#comment:11>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
FFmpeg | 6 Feb 01:40 2016

Re: #2337(avformat:closed): Frame duplicated for AVCHD sample

#2337: Frame duplicated for AVCHD sample
-------------------------------------+------------------------------------
             Reporter:  rmk          |                    Owner:
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:  avformat
              Version:  git-master   |               Resolution:  fixed
             Keywords:  h264 mpegts  |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+------------------------------------
Changes (by cehoyos):

 * keywords:   => h264 mpegts
 * resolution:   => fixed
 * status:  new => closed
 * component:  undetermined => avformat
 * version:  unspecified => git-master

Comment:

 This was fixed by Michael in 1e5271a9fd6ddcceb083f2185a4bbd8d44c9a813 -
 see ticket #2143.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/2337#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
(Continue reading)

FFmpeg | 5 Feb 20:26 2016

#5220(ffplay:new): ffplay lag with some resolutions when using i915 and SNA acceleration method

#5220: ffplay lag with some resolutions when using i915 and SNA acceleration
method
-------------------------------------+-------------------------------------
             Reporter:  VittGam      |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:  ffplay       |                  Version:  git-
             Keywords:  i915, sna,   |  master
  uxa                                |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 Hello,

 When using `SNA` acceleration on an Intel GMA915 video card (IBM !ThinkPad
 X41, screen is 1024x768), I'm having some problems with these resolutions
 in ffplay:

 - 1018x576 through 1037x576

 The problems are: increased IO-Wait and general lag of the mouse and
 screen, and frame drop in ffplay.

 Width values smaller than 1018 or bigger than 1037 work fine instead. Even
 1280x576 works perfectly.

 The same problem is reproduced with other height values, such as 480.

 A simple test case for this is:

 {{{
(Continue reading)

FFmpeg | 5 Feb 11:33 2016

#5219(undetermined:new): When I copy streams from mts video with pcm_bluray audio I lose audio

#5219: When I copy streams from mts video with pcm_bluray audio I lose audio
-------------------------------------+-------------------------------------
             Reporter:  malcev       |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:
  undetermined                       |  unspecified
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 My code is:
 ffmpeg -i 1.mts -c copy 2.mts
 cmd output is:
 http://pastebin.com/5nSpGK1m
 mts file link:
 http://www.datafilehost.com/d/c85446fa

--
Ticket URL: <https://trac.ffmpeg.org/ticket/5219>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
FFmpeg | 5 Feb 11:19 2016

Re: #3317(avfilter:open): Drawtext+Alphamerge results in incorrect alpha value

#3317: Drawtext+Alphamerge results in incorrect alpha value
------------------------------------+------------------------------------
             Reporter:  jnvsor      |                    Owner:
                 Type:  defect      |                   Status:  open
             Priority:  normal      |                Component:  avfilter
              Version:  git-master  |               Resolution:
             Keywords:              |               Blocked By:
             Blocking:              |  Reproduced by developer:  1
Analyzed by developer:  0           |
------------------------------------+------------------------------------
Changes (by richardpl):

 * status:  new => open
 * component:  undetermined => avfilter
 * reproduced:  0 => 1

Comment:

 Forcing rgba as format after drawtext filter fixes issue.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3317#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Gmane