Re: [FFmpeg-trac] #4401(ffmpeg:reopened): Past duration too large

[FFmpeg]

#4401: Past duration too large
+
 Reporter:  ghazel  |Owner:
 Type:  defect  |   Status:  reopened
 Priority:  normal  |Component:  ffmpeg
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by rogerdpack):

 I believe I saw it recently, like within the last month or two. So yes
 most likely...

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5603(undetermined:new): wav: support decoding of "16.8 Floating Point (Legacy Audition Format)"

[FFmpeg]

#5603: wav: support decoding of "16.8 Floating Point (Legacy Audition Format)"
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by ami_stuff):

 patch:

 https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2016-September/199813.html

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5602(undetermined:new): wav: support decoding of "24.0 Floating Point (Legacy Audition Format)"

[FFmpeg]

#5602: wav: support decoding of "24.0 Floating Point (Legacy Audition Format)"
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by ami_stuff):

 patch:

 https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2016-September/199813.html

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5890(avformat:closed): DVTel Camera G726 Audio

[FFmpeg]

#5890: DVTel Camera G726 Audio
+
 Reporter:  DJX |Owner:
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:  fixed
 Keywords:  rtp g726|   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by cehoyos):

 Replying to [comment:3 cehoyos]:
 > Should be fixed in 6969bed12c6fc53509aa694aab32d01838318f30, please test
 and report back.
 Ping.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5602(undetermined:open): wav: support decoding of "24.0 Floating Point (Legacy Audition Format)"

[FFmpeg]

#5602: wav: support decoding of "24.0 Floating Point (Legacy Audition Format)"
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  wav  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  1
-+-
Changes (by cehoyos):

 * keywords:   => wav
 * status:  new => open
 * version:  unspecified => git-master
 * reproduced:  0 => 1


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #2966(avcodec:open): ljpeg: support 36bpp rgb

[FFmpeg]

#2966: ljpeg: support 36bpp rgb
-+---
 Reporter:  ami_stuff|Owner:
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  ljpeg mjpeg  |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---

Comment (by ami_stuff):

 I attached also some lossy samples.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5603(undetermined:open): wav: support decoding of "16.8 Floating Point (Legacy Audition Format)"

[FFmpeg]

#5603: wav: support decoding of "16.8 Floating Point (Legacy Audition Format)"
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  wav  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  1
-+-
Changes (by cehoyos):

 * keywords:   => wav
 * status:  new => open
 * version:  unspecified => git-master
 * reproduced:  0 => 1


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #4344(undetermined:new): XSUBs are too low in PAL video, on PS3

[FFmpeg]

#4344: XSUBs are too low in PAL video, on PS3
-+-
 Reporter:  edumj|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  xsub |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by edumj):

 I've tested, and it seems that DivXMux does this:
 1-Crop every bitmap (like SubRip).
 2-Pad them to 640x480 (bottom center aligned).

 VLC captures with a yellow drawbox to see subtitles full size:

 DVD Subtitles extracted to IDX/SUB are 720x576:
 [[Image(http://i47.photobucket.com/albums/f169/edumj/IDX-
 SUB%20720x576.png)]]

 IDX/SUB Subtitles converted to XSUB with DivXMux are 640x480:
 [[Image(http://i47.photobucket.com/albums/f169/edumj/IDX-
 SUB%20to%20DivXMux%20640x480.png)]]

 You can see original upper subs go down with DivXMux because of the
 cropping an padding. They look not well bottom-centered in VLC, but ok in
 TV.

 I don't know if ffmpeg can do this automatic cropping and padding to
 640x480, but at least it could scale them down to 720x480 or better
 640x480.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5921(avformat:open): Can not read mjpeg from IP camera

[FFmpeg]

#5921: Can not read mjpeg from IP camera
-+-
 Reporter:  qqqzhouhk|Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  mpjpeg   |   Blocked By:
  regression |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by qqqzhouhk):

 Replying to [comment:11 cehoyos]:
 > Work-around is to specify {{{-f mjpeg}}}.

 Man, you are awesome!! It works, but how can I achieve it when I am using
 FFMPEG library, as in FFMPEGdemo code? Thank you again, my bro!

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5023(avformat:closed): Can no longer read mjpeg from Mobotix camera

[FFmpeg]

#5023: Can no longer read mjpeg from Mobotix camera
-+-
 Reporter:  hackeron |Owner:
 Type:  defect   |   Status:  closed
 Priority:  important|Component:  avformat
  Version:  git-master   |   Resolution:  fixed
 Keywords:  mjpeg|   Blocked By:
  mpjpeg regression  |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by qqqzhouhk):

 Replying to [comment:30 w3sip]:
 > Have you ran it with -f mjpeg?
 >
 > As to the facts:
 > - this camera produces an mpjpeg stream
 > - this stream was previously detected as mjpeg, and that worked, albeit
 generating a ton of warnings (for the envelope multipart data)
 > - for some reason, ffmpeg, even with the most recent changes, doesn't
 like this mpjpeg stream (though, as I've personally and hackeron have
 tested, it's just fine with the wget's output)
 > - to resolve this I suggest either providing us with a packet capture
 (full tcpdump/wireshark output, containing both the request and the
 response), *or* making this camera available for us to test against


 sorry, but what is mpjpeg stream? Do you mean mjpeg? I can't find any
 thing about mpjpeg. Hope for your reply, thank you.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #5929(avcodec:new): Warnings shown for likely invalid real-life H.264 stream

[FFmpeg]

#5929: Warnings shown for likely invalid real-life H.264 stream
--+-
   Reporter:  cehoyos |  Owner:
   Type:  defect  | Status:  new
   Priority:  minor   |  Component:  avcodec
Version:  git-master  |   Keywords:  h264
 Blocked By:  |   Blocking:
Reproduced by developer:  0   |  Analyzed by developer:  0
--+-
 http://ffmpeg.org/pipermail/ffmpeg-user/2016-November/034184.html
 Pelco ES5230 cameras send a stream via rtsp that shows many errors when
 decoded with FFmpeg.
 {{{
 $ ffmpeg -i PelcoES5230.h264
 ffmpeg version N-82235-g222f59a Copyright (c) 2000-2016 the FFmpeg
 developers
   built with gcc 4.7 (SUSE Linux)
   configuration: --enable-gpl --enable-gnutls
   libavutil  55. 35.100 / 55. 35.100
   libavcodec 57. 66.101 / 57. 66.101
   libavformat57. 57.100 / 57. 57.100
   libavdevice57.  2.100 / 57.  2.100
   libavfilter 6. 66.100 /  6. 66.100
   libswscale  4.  3.100 /  4.  3.100
   libswresample   2.  4.100 /  2.  4.100
   libpostproc54.  2.100 / 54.  2.100
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 160
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 159
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 160
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 159
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 160
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 159
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 160
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 159
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 160
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 159
 [h264 @ 0x2ca1ac0] SEI type 5 size 352 truncated at 160
 [h264 @ 0x2ca1ac0] SEI type 5 size 352 truncated at 159
 [h264 @ 0x2ca1ac0] SEI type 5 size 352 truncated at 160
 [h264 @ 0x2ca1ac0] SEI type 5 size 352 truncated at 159
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 160
 Last message repeated 27 times
 [h264 @ 0x2ca1ac0] SEI type 5 size 352 truncated at 160
 Last message repeated 1 times
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 160
 Last message repeated 27 times
 [h264 @ 0x2ca1ac0] SEI type 5 size 352 truncated at 160
 Last message repeated 1 times
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 160
 Last message repeated 12 times
 [h264 @ 0x2ca1ac0] SEI type 5 size 368 truncated at 160
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 160
 Last message repeated 13 times
 [h264 @ 0x2ca1ac0] SEI type 5 size 352 truncated at 160
 Last message repeated 1 times
 [h264 @ 0x2ca1ac0] SEI type 5 size 360 truncated at 160
 Last message repeated 17 times
 Input #0, h264, from 'PelcoES5230.h264':
   Duration: N/A, bitrate: N/A
 Stream #0:0: Video: h264 (High), yuv420p(progressive), 1920x1080 [SAR
 1:1 DAR 16:9], 30 fps, 30 tbr, 1200k tbn, 60 tbc
 At least one output file must be specified
 }}}

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5891(undetermined:closed): "-t" not applied to streams when using channelsplit filter

[FFmpeg]

#5891: "-t" not applied to streams when using channelsplit filter
-+-
 Reporter:  MReedAustin  |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * status:  new => closed
 * resolution:   => invalid


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #4861(avcodec:open): E-AC3 audio glitch : exponent out-of-range

[FFmpeg]

#4861: E-AC3 audio glitch : exponent out-of-range
+---
 Reporter:  Guillaume   |Owner:
 Type:  defect  |   Status:  open
 Priority:  normal  |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  eac3|   Blocked By:
 Blocking:  |  Reproduced by developer:  1
Analyzed by developer:  0   |
+---

Comment (by tesla_):

 Hi some news. I've try to make a statistic approch of the problem.
 I've analyse the amount begin header of each frame and each block , the
 amount of consumption of data for each block and frame for 20/30
 consequently and like i think it's very linear. With this approach i
 sucessfull find the function that sucks and doesn't consumme enough data.
 The data pointer is completely shifted for the seconde blk of the frame
 and  the error is detect only when it's possible to detect.. AKA in
 decode_exponents and with a very lucky way...
 Now next step why decode_transform_coeffs doesn't consumme the data she
 could :)

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac