FFmpeg | 5 Sep 11:43 2015

Re: #2690(avcodec:open): Red Cinema r3d files not supported

#2690: Red Cinema r3d files not supported
-------------------------------------+-----------------------------------
             Reporter:  MilosL       |                    Owner:
                 Type:  enhancement  |                   Status:  open
             Priority:  wish         |                Component:  avcodec
              Version:  git-master   |               Resolution:
             Keywords:  r3d j2k      |               Blocked By:
             Blocking:               |  Reproduced by developer:  1
Analyzed by developer:  0            |
-------------------------------------+-----------------------------------

Comment (by cehoyos):

 Replying to [comment:21 compn]:
 > bayer colorspace support was added a few months ago.

 FFmpeg supports bayer formats with 8 bit per pixel and 16 bit per pixel,
 the r3d formats have 12 bit per component (48 bit per pixel).

--
Ticket URL: <https://trac.ffmpeg.org/ticket/2690#comment:22>
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 Sep 00:25 2015

#4829(swscale:new): Overflows (?) in xyz -> rgb conversion

#4829: Overflows (?) in xyz -> rgb conversion
--------------------------------------+---------------------------------
               Reporter:  cehoyos     |                  Owner:
                   Type:  defect      |                 Status:  new
               Priority:  normal      |              Component:  swscale
                Version:  git-master  |               Keywords:  xyz
             Blocked By:              |               Blocking:
Reproduced by developer:  0           |  Analyzed by developer:  0
--------------------------------------+---------------------------------
 ‚Äčhttp://thread.gmane.org/gmane.comp.video.ffmpeg.user/58666
 The sample attached to ticket #4827 is in fact decoded fine (at least
 visually) by the native jpeg 2000 decoder but the colourspace conversion
 shows posterization artefacts.
 This is also reproducible with the libopenjpeg decoder.
 {{{
 $ ffmpeg -i frm_000127.j2c out.png
 ffmpeg version N-74866-g0cdba4a Copyright (c) 2000-2015 the FFmpeg
 developers
   built with gcc 4.7 (SUSE Linux)
   configuration: --enable-gpl
   libavutil      54. 31.100 / 54. 31.100
   libavcodec     56. 60.100 / 56. 60.100
   libavformat    56. 40.101 / 56. 40.101
   libavdevice    56.  4.100 / 56.  4.100
   libavfilter     5. 40.101 /  5. 40.101
   libswscale      3.  1.101 /  3.  1.101
   libswresample   1.  2.101 /  1.  2.101
   libpostproc    53.  3.100 / 53.  3.100
 [jpeg2000  <at>  0x33bd940] End mismatch 1
     Last message repeated 4 times
(Continue reading)

FFmpeg | 4 Sep 12:39 2015

#4828(avcodec:new): use Core Audio AAC-encoder and AC3-decoder to avoid patent concerns

#4828: use Core Audio AAC-encoder and AC3-decoder to avoid patent concerns
---------------------------------+---------------------------------------
             Reporter:  julian   |                     Type:  enhancement
               Status:  new      |                 Priority:  wish
            Component:  avcodec  |                  Version:  unspecified
             Keywords:           |               Blocked By:
             Blocking:           |  Reproduced by developer:  0
Analyzed by developer:  0        |
---------------------------------+---------------------------------------
 it would be great if ffmpeg would be able to use the system provided Core
 Audio AAC-encoder and AC3-decoder under Mac OS X because Apple has payed
 the patent fees for these en/decoders for all uses. this would enable
 people to use ffmpeg to encode AAC & decode AC3 without patent concerns.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/4828>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
FFmpeg | 4 Sep 10:33 2015

#4827(avcodec:new): Many warnings shown when decoding j2k

#4827: Many warnings shown when decoding j2k
--------------------------------------+---------------------------------
               Reporter:  cehoyos     |                  Owner:
                   Type:  defect      |                 Status:  new
               Priority:  minor       |              Component:  avcodec
                Version:  git-master  |               Keywords:  j2k
             Blocked By:              |               Blocking:
Reproduced by developer:  0           |  Analyzed by developer:  0
--------------------------------------+---------------------------------
 http://thread.gmane.org/gmane.comp.video.ffmpeg.user/58666
 A user uploaded a j2k sequence that decodes fine with current FFmpeg
 afaict, but many warnings are shown for every frame.
 {{{
 $ ffmpeg -i frm_000127.j2c out.png
 ffmpeg version N-74835-gbd6610c Copyright (c) 2000-2015 the FFmpeg
 developers
   built with gcc 4.7 (SUSE Linux)
   configuration: --enable-gpl
   libavutil      54. 31.100 / 54. 31.100
   libavcodec     56. 60.100 / 56. 60.100
   libavformat    56. 40.101 / 56. 40.101
   libavdevice    56.  4.100 / 56.  4.100
   libavfilter     5. 40.101 /  5. 40.101
   libswscale      3.  1.101 /  3.  1.101
   libswresample   1.  2.101 /  1.  2.101
   libpostproc    53.  3.100 / 53.  3.100
 [jpeg2000  <at>  0x26de900] End mismatch 1
     Last message repeated 4 times
 [jpeg2000  <at>  0x26de900] End mismatch 2
     Last message repeated 1 times
(Continue reading)

FFmpeg | 3 Sep 14:54 2015

Re: #2227(ffmpeg:closed): ffmpeg incorrectly identifying mjpeg as video stream instead of attachment

#2227: ffmpeg incorrectly identifying mjpeg as video stream instead of attachment
-------------------------------------+----------------------------------
             Reporter:  ramitbhalla  |                    Owner:
                 Type:  enhancement  |                   Status:  closed
             Priority:  wish         |                Component:  ffmpeg
              Version:  git-master   |               Resolution:  fixed
             Keywords:  wtv          |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+----------------------------------
Changes (by cehoyos):

 * status:  new => closed
 * type:  defect => enhancement
 * component:  undetermined => ffmpeg
 * priority:  normal => wish
 * version:  unspecified => git-master
 * resolution:   => fixed

Comment:

 This may have been fixed by Marton Balint in
 26a0cd1b4b093f3f6e4f15d28a282ec45b87bb98

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

FFmpeg | 3 Sep 13:30 2015

#4826(avcodec:new): Sample request "Subtitles with data type ..." is extremely spammy

#4826: Sample request "Subtitles with data type ..." is extremely spammy
-------------------------------------+-------------------------------------
             Reporter:  barsnick     |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:  avcodec      |                  Version:  git-
             Keywords:               |  master
  avpriv_request_sample              |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 Summary of the bug:

 When decoding/remuxing an MPEG-TS (captured from DVB-S2 with a PVR), the
 message:

 {{{
 [NULL  <at>  0xb8cbbe0] Subtitles with data type 0x06 is not implemented.
 Update your FFmpeg version to the newest one from Git. If the problem
 still occurs, it means that your file has a feature which has not been
 implemented.
 [NULL  <at>  0xb8cbbe0] If you want to help, upload a sample of this file to
 ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing
 list. (ffmpeg-devel <at> ffmpeg.org)
 }}}

 is spamming the console and making it useless for reading any other
 information.

 This message was introduced in commit
 f9ab4fe1f7c1e9d410ca5ee2c9ff8d2892aad068 (with a subsequent edit in commit
(Continue reading)

FFmpeg | 3 Sep 13:30 2015

#4825(ffmpeg:new): implement an equivalent for mplayer -dumpstream

#4825: implement an equivalent for mplayer -dumpstream
---------------------------------------+--------------------------------
               Reporter:  cehoyos      |                  Owner:
                   Type:  enhancement  |                 Status:  new
               Priority:  wish         |              Component:  ffmpeg
                Version:  git-master   |               Keywords:
             Blocked By:               |               Blocking:
Reproduced by developer:  0            |  Analyzed by developer:  0
---------------------------------------+--------------------------------
 Users often report that remuxing network (or other) streams fails because
 of timestamp discontinuities or similar issues while mplayer -dumpstream
 works fine.
 Ideally, FFmpeg would have an equivalent function.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/4825>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
FFmpeg | 3 Sep 11:24 2015

#4824(undetermined:new): Rtmp Lip-sync trouble

#4824: Rtmp Lip-sync trouble
-------------------------------------+-------------------------------------
             Reporter:  laurfb       |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:
  undetermined                       |  unspecified
             Keywords:  lip-sync     |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 Summary of the bug:

 Hi. I've have some trouble trying to save or play an rtmp stream with
 ffmpeg (lip-sync trouble).
 The same stream plays without any trouble with ffplay!
 Seems that ffmpeg connot manage very well (although ffplay can!) any DTS
 errors (see attached ffprobe report)

 The ffmpeg package is build from the master ffmpeg git (N-74786-g50f2f7a).
 The live stream can be viewed at rtmp://82.208.148.204:1935/live/tvriasi

 I try variour -vsync/async option without any luck.
 Any help will be appreciated.

 best regards,
 laurb

 How to reproduce:
 {{{
 % ffmpeg -i rtmp://82.208.148.204:1935/live/tvriasi -c copy -f flv
(Continue reading)

FFmpeg | 2 Sep 18:12 2015

#4823(undetermined:new): Conversion from DTS/DTS-MA to AC3 results in 2 channels instead of 6

#4823: Conversion from DTS/DTS-MA to AC3 results in 2 channels instead of 6
-------------------------------------+-------------------------------------
             Reporter:  JohnGalt     |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:  git-
  undetermined                       |  master
             Keywords:  ac3 dts      |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 How to reproduce:
 ffmpeg -c:a:0 ac3 -ac 6 -ab 448k -ar48000
 Where a:0 = DTS or a DTS MA Track
 9/1/2015

 It appears to ignore the 6 in the -ac 6 and just down mixes to 2 tracks.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/4823>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac <at> avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
FFmpeg | 2 Sep 17:31 2015

#4822(undetermined:new): [png <at> 0x15e183e00] inflate returned error -3

#4822: [png  <at>  0x15e183e00] inflate returned error -3
-------------------------------------+-------------------------------------
             Reporter:  wangniancai  |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:
  undetermined                       |  unspecified
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 Summary of the bug: when I try to add watermark with png , I find this
 error on ios ,but the same libs work fine on android. ffmpeg 2.7
 How to reproduce:
 {{{
 command    ffmpeg i input -vf "movie=% <at>  [wm];[in][wm]overlay=0:0[out]"
 ffmpeg version 2.7
 built on ...
 I find the fix for Ticket2903 in my source code pngdec.c
 }}}
 Patches should be submitted to the ffmpeg-devel mailing list and not this
 bug tracker.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/4822>
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 | 2 Sep 14:33 2015

Re: #1057(undetermined:closed): support ffmpeg -targets

#1057: support ffmpeg -targets
-------------------------------------+-------------------------------------
             Reporter:  dericed      |                    Owner:
                 Type:  enhancement  |                   Status:  closed
             Priority:  wish         |                Component:
              Version:  git-master   |  undetermined
             Keywords:  target       |               Resolution:  fixed
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by cehoyos):

 Remaining issue hould be fixed in a4188c9cd29a5bdea599e4c563eec6f6df496703

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

Gmane