Re: [FFmpeg-trac] #5825(avcodec:closed): Vobsub subtitles won't overlay with some MKV

[FFmpeg]

#5825: Vobsub subtitles won't overlay with some MKV
-+-
 Reporter:  edumj|Owner:
 Type:  defect   |   Status:  closed
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  dvdsub   |   Blocked By:
  regression |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by edumj):

 There's still something wrong with overlaying and colors.

 If I try to overlay subs, I get "[matroska,webm @ 0318c660] Read error"

 ffmpeg:
 {{{
 ffmpeg -palette
 
"ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff"
 -i "%~1" -filter_complex "[0:v][0:s:0]overlay[out]" -map "[out]" -map
 0:a:1 -f avi -c:v libxvid -b:v 1500k -vtag XVID -c:a libmp3lame -b:a 128k
 "%~n1 overlay.avi"
 }}}

 output:
 {{{
 ffmpeg version N-81696-gd38dff8e Copyright (c) 2000-2016 the FFmpeg
 developers
   built with gcc 5.4.0 (GCC)
   configuration: --enable-gpl --enable-version3 --disable-w32threads
 --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-
 bzlib --enable-libebur128 --enable-fontconfig --enable-frei0r --enable-
 gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b
 --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm
 --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-
 libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264
 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-
 libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex
 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-
 amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-
 libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-
 libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
   libavutil  55. 29.100 / 55. 29.100
   libavcodec 57. 57.100 / 57. 57.100
   libavformat57. 49.100 / 57. 49.100
   libavdevice57.  0.102 / 57.  0.102
   libavfilter 6. 62.100 /  6. 62.100
   libswscale  4.  1.100 /  4.  1.100
   libswresample   2.  1.100 /  2.  1.100
   libpostproc54.  0.100 / 54.  0.100
 Input #0, matroska,webm, from 'C:\Users\Edumj\Videos\Pa Probar\DVDRip
 (MKV) con VobSub's\Francis en la Marina (1955)_cut.mkv':
   Metadata:
 encoder : libmkv 0.6.5
   Duration: 01:16:58.18, start: 0.00, bitrate: 4 kb/s
 Chapter #0:0: start 0.00, end 84.897000
 Metadata:
   title   : Chapter 1
 Chapter #0:1: start 84.897000, end 1048.977000
 Metadata:
   title   : Chapter 2
 Chapter #0:2: start 1048.977000, end 1812.817000
 Metadata:
   title   : Chapter 3
 Chapter #0:3: start 1812.817000, end 2423.737000
 Metadata:
   title   : Chapter 4
 Chapter #0:4: start 2423.737000, end 3226.097000
 Metadata:
   title   : Chapter 5
 Chapter #0:5: start 3226.097000, end 3864.937000
 Metadata:
   title   : Chapter 6
 Chapter #0:6: start 3864.937000, end 4618.177000
 Metadata:
   title   : Chapter 7
 Stream #0:0(eng): Video: h264 (Main), yuv420p(tv,
 smpte170m/smpte170m/bt709), 720x384 [SAR 16:15 DAR 2:1], 25 fps, 25 tbr,
 1k tbn, 180k tbc (default)
 Stream #0:1(spa): Audio: aac (LC), 48000 Hz, stereo, fltp (default)
 Stream #0:2(eng): Audio: aac (LC), 48000 Hz, stereo, fltp
 Stream #0:3(spa): Subtitle: dvd_subtitle, 720x576
 [avi @ 04f6ba40] Using AVStream.codec to pass codec parameters to muxers
 is deprecated, use AVStream.codecpar instead.
 Last message repeated 1 times
 [null @ 048eca20] Using AVStream.codec to pass codec parameters to muxers
 is deprecated, use AVStream.codecpar instead.
 Last message repeated 1 times
 Output #0, avi, to
 'E:\MISDOC~1\CONVER~1\_PACON~1\MEDIAI~1\FFD8CF~1\DVDAXS~1\CONFFM~1\\Francis
 en la Marina (1955)_cut overlay.avi':
   Metadata:
 ISFT: Lavf57.49.100
 Chapter #0:0: start 0.00, end 84.897000
 Metadata:
   title   : Chapter 1
 Chapter #0:1: start 84.897000, end 1048.977000
 Metadata:
   title   : Chapter 2
 Chapter #0:2: start 1048.977000, end 1812.817000
 Metadata:
   title   : Chapter 3
 Chapter #0:3: start 1812.817000, end 2423.737000
 Metadata:
   title   : Chapter 4
 Chapter #0:4: start 2423.737000, end 3226.097000
 Metadata:
   title   : Chapter 5
 Chapter #0:5: start 3226.097000, end 3864.937000
 Metadata:
   title   : Chapter 6
 Chapter 

Re: [FFmpeg-trac] #5846(avformat:open): Support writing BOM in SRT muxer

[FFmpeg]

#5846: Support writing BOM in SRT muxer
-+
 Reporter:  edumj|Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  srt  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by edumj):

 I've just tested extracting subs from one DVD with Subrip.exe (with OCR)
 and I can choose between Unicode Little Endian or ANSI (no UTF-8). Even it
 says it must be Unicode because of special characters, but with ANSI it
 seems Ok.

 ubitux, you mean add it to muxer or demuxer?

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

Re: [FFmpeg-trac] #5847(undetermined:closed): Duration estimate and bitrate calculation wrong when file is over 4Gb

[FFmpeg]

#5847: Duration estimate and bitrate calculation wrong when file is over 4Gb
-+-
 Reporter:  petere   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  mpegps   |   Resolution:  duplicate
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by richardpl):

 What command you tried with concat demuxer?

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

Re: [FFmpeg-trac] #5847(undetermined:closed): Duration estimate and bitrate calculation wrong when file is over 4Gb

[FFmpeg]

#5847: Duration estimate and bitrate calculation wrong when file is over 4Gb
-+-
 Reporter:  petere   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  mpegps   |   Resolution:  duplicate
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by petere):

 I tried concat demuxer but it does not support analyzeduration so it does
 not find the subtitle streams when burning subtitles with complex filter

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

Re: [FFmpeg-trac] #5852(avcodec:new): ProRes Color range tags not working

[FFmpeg]

#5852: ProRes Color range tags not working
-+-
 Reporter:  RuudKaag |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  prores,  |   Blocked By:
  color range|  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by richardpl):

 What happens if you use -c:v prores_ks  as '''encoder''' ?

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

Re: [FFmpeg-trac] #5847(undetermined:closed): Duration estimate and bitrate calculation wrong when file is over 4Gb

[FFmpeg]

#5847: Duration estimate and bitrate calculation wrong when file is over 4Gb
-+-
 Reporter:  petere   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  mpegps   |   Resolution:  duplicate
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by richardpl):

 Why not try concat demuxer instead?

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

Re: [FFmpeg-trac] #4353(undetermined:closed): DNxHD 444 from Blackmagic Resolve decodes first frame only

[FFmpeg]

#4353: DNxHD 444 from Blackmagic Resolve decodes first frame only
-+-
 Reporter:  simonburley  |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  mxf dnxhd|   Resolution:
 Blocking:   |  worksforme
Analyzed by developer:  0|   Blocked By:
 |  Reproduced by developer:  0
-+-
Changes (by richardpl):

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


Comment:

 Can not reproduce, command works fine here.

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

Re: [FFmpeg-trac] #5847(undetermined:closed): Duration estimate and bitrate calculation wrong when file is over 4Gb

[FFmpeg]

#5847: Duration estimate and bitrate calculation wrong when file is over 4Gb
-+-
 Reporter:  petere   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  mpegps   |   Resolution:  duplicate
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by petere):

 Yes I tested with analyzeduration and it took a long time but still did
 not get the correct duration or bitrate.  Upon further investigation it
 looks like the timestamps reset in vob 5 so the duration is correct in
 vobs 1, 2, 3, and 4 but 5 starts at 0 again.  So if ffmpeg reads the
 timestamps from the end of the file they will be less than the start and
 the duration and bitrate will be incorrect.

 I tried using the separate vobs and the concat: input but this does not
 use analyzeduration so it does not find all the subtitles when I use
 filter complex to burn subtitles.

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

Re: [FFmpeg-trac] #3163(avformat:closed): Broadcast Wave Metadata not carried over with -codec:a copy

[FFmpeg]

#3163: Broadcast Wave Metadata not carried over with -codec:a copy
+--
 Reporter:  rexbron |Owner:
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:  worksforme
 Keywords:  wav |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+--
Changes (by richardpl):

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


Comment:

 Feel free to reopen if above command does not work.

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

Re: [FFmpeg-trac] #4569(undetermined:closed): DNxHD as Input produce wrong color/gamma in output

[FFmpeg]

#4569: DNxHD as Input produce wrong color/gamma in output
-+-
 Reporter:  jb_alvarado  |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |  needs_more_info
Analyzed by developer:  0|   Blocked By:
 |  Reproduced by developer:  0
-+-
Changes (by richardpl):

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


Comment:

 No samples, can not reproduce

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

Re: [FFmpeg-trac] #2665(undetermined:closed): AV_PICTURE_TYPE_NONE is returned for multiple slice H264 frames

[FFmpeg]

#2665: AV_PICTURE_TYPE_NONE is returned for multiple slice H264 frames
-+-
 Reporter:  Gibraltar|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  1.1.5|  undetermined
 Keywords:  h264 |   Resolution:
 Blocking:   |  needs_more_info
Analyzed by developer:  0|   Blocked By:
 |  Reproduced by developer:  0
-+-
Changes (by richardpl):

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


Comment:

 Unclear bug report.

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

 32bit int was hidden under "4-byte PCM":

 http://www.megafileupload.com/oluO/32bit_int.wav

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

Re: [FFmpeg-trac] #5854(undetermined:closed): H.264 encoding - veryfast preset produces smaller file than faster preset

[FFmpeg]

#5854: H.264 encoding - veryfast preset produces smaller file than faster preset
-+-
 Reporter:  mimac|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:  H.264 preset =>


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

 Here is 16bit int, 32bit float and again 32bit 24.0 float:

 http://www.megafileupload.com/k9lz/coole_32.7z

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

Re: [FFmpeg-trac] #5854(undetermined:closed): H.264 encoding - veryfast preset produces smaller file than faster preset

[FFmpeg]

#5854: H.264 encoding - veryfast preset produces smaller file than faster preset
-+-
 Reporter:  mimac|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  H.264|   Resolution:  invalid
  preset |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by mimac):

 I will direct the question to libx264 project, sorry for misunderstanding.
 For the size guarantees, I made tests with constant quality settings and
 thought that results would comply with what
 [https://trac.ffmpeg.org/wiki/Encode/H.264 page about encoding] states:
 ''Similarly, for constant quality encoding, you will simply save bitrate
 by choosing a slower preset.''

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

Re: [FFmpeg-trac] #5854(undetermined:closed): H.264 encoding - veryfast preset produces smaller file than faster preset

[FFmpeg]

#5854: H.264 encoding - veryfast preset produces smaller file than faster preset
-+-
 Reporter:  mimac|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  H.264|   Resolution:  invalid
  preset |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by heleppkes):

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


Comment:

 First and foremost, these are libx264 presets and not something FFmpeg
 manages. As such, any questions to how libx264 compression works should be
 directed to that project.

 To the issue at hand, there are no size guarantees for any of the presets,
 only speed/quality tradeoffs. It is very well possible that faster presets
 produce smaller files, albeit at a lower quality.

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

Re: [FFmpeg-trac] #5854(undetermined:new): H.264 encoding - veryfast preset produces smaller file than faster preset

[FFmpeg]

#5854: H.264 encoding - veryfast preset produces smaller file than faster preset
-+-
 Reporter:  mimac|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  H.264|   Resolution:
  preset |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by mimac):

 * version:  unspecified => git-master


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

[FFmpeg-trac] #5854(undetermined:new): H.264 encoding - veryfast preset produces smaller file than faster preset

[FFmpeg]

#5854: H.264 encoding - veryfast preset produces smaller file than faster preset
-+-
 Reporter:  mimac| Type:  defect
   Status:  new  | Priority:  normal
Component:   |  Version:
  undetermined   |  unspecified
 Keywords:  H.264|   Blocked By:
  preset |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
 '''Summary of the bug:'''
 According to [https://trac.ffmpeg.org/wiki/Encode/H.264], for constant
 quality encoding, faster preset should be slower and produce smaller file
 than veryfast preset. However, by my testing, faster preset produced
 always bigger file than veryfast preset.

 '''How to reproduce:'''
 {{{
 ffmpeg version N-81696-gd38dff8e-static http://johnvansickle.com/ffmpeg/
 Copyright (c) 2000-2016 the FFmpeg developers
   built with gcc 5.4.1 (Debian 5.4.1-2) 20160904
   configuration: --enable-gpl --enable-version3 --enable-static --disable-
 debug --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-
 libwebp --enable-libspeex --enable-libvorbis --enable-libvpx --enable-
 libfreetype --enable-fontconfig --enable-libxvid --enable-libopencore-
 amrnb --enable-libopencore-amrwb --enable-libtheora --enable-libvo-
 amrwbenc --enable-gray --enable-libopenjpeg --enable-libopus --enable-
 libass --enable-gnutls --enable-libvidstab --enable-libsoxr --enable-
 frei0r --enable-libfribidi --disable-indev=sndio --disable-outdev=sndio
 --enable-librtmp --enable-libmfx --enable-libzimg --cc=gcc-5
   libavutil  55. 29.100 / 55. 29.100
   libavcodec 57. 57.100 / 57. 57.100
   libavformat57. 49.100 / 57. 49.100
   libavdevice57.  0.102 / 57.  0.102
   libavfilter 6. 62.100 /  6. 62.100
   libswscale  4.  1.100 /  4.  1.100
   libswresample   2.  1.100 /  2.  1.100
   libpostproc54.  0.100 / 54.  0.100


 % ffmpeg  -i newmobcal1920_12mbps.ts  -c:v libx264 -profile:v high -level
 4.0 -preset faster result-faster.mkv
 % ffmpeg  -i newmobcal1920_12mbps.ts  -c:v libx264 -profile:v high -level
 4.0 -preset veryfast result-veryfast.mkv
 % ll *.mkv
 -rw-rw-r-- 1 user user 84785654 Sep 19 21:28 result-faster.mkv
 -rw-rw-r-- 1 user user 77822551 Sep 19 21:15 result-veryfast.mkv
 }}}
 Input video is from [http://www.w6rz.net]
 ([http://www.w6rz.net/newmobcal1920_12mbps.ts]). Reports are attached.

 I was able to reproduce this behavior on Ubuntu as well as Windows, with
 three different input files (H.264, MPEG2, MJPEG), also with CFR values
 18, 23 and 28. Veryfast preset always produced smaller file than faster
 and fast preset, in most cases also smaller than medium preset.

--
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 richardpl):

 I don't think this is supported by libsndfile at all.

 Could you upload normal 16 bit int and 32 bit int and 32 bit float sample
 as produced by same software?

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

Re: [FFmpeg-trac] #5297(avcodec:open): mpeg-4 als: "predictor order too large"

[FFmpeg]

#5297: mpeg-4 als: "predictor order too large"
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |  thilo.borgmann
 Priority:  important|   Status:  open
  Version:  git-master   |Component:  avcodec
 Keywords:  als  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+-
Changes (by thilo.borgmann):

 * cc: thilo.borgmann (removed)


Comment:

 I'm already receiving mails for this ticket for being assigned to it.

 Found the sample, thanks!

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

[FFmpeg-trac] #5853(undetermined:new): M3U8 seeking is off or frame count is off

[FFmpeg]

#5853: M3U8 seeking is off or frame count is off
-+-
 Reporter:  lletourn | Type:  defect
   Status:  new  | Priority:  normal
Component:   |  Version:
  undetermined   |  unspecified
 Keywords:  m3u8 |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:
 There are 2 mutually exclusive (but seem to be related) bugs

 1- When seeking, the position seeked to is off by many frames.
 2- When counting frames with ffprobe the number given is higher than
 expected

 How to reproduce:
 From master/HEAD:
 {{{
 % rm -f dude.png ; ./ffmpeg -y -ss 0 -vsync 0 -i
 https://s3.amazonaws.com/slffmpegdebug/seekProb/seekProb.m3u8 -f image2
 -q:v 1 -vframes 1  dude.png ; feh dude.png
 ffmpeg version N-81699-g590f025 Copyright (c) 2000-2016 the FFmpeg
 developers
   built with gcc 5.2.1 (Ubuntu 5.2.1-22ubuntu2) 20151010
   configuration: --enable-gpl --enable-libx264 --enable-nonfree --enable-
 libfdk-aac --enable-openssl --enable-static
   libavutil  55. 29.100 / 55. 29.100
   libavcodec 57. 57.100 / 57. 57.100
   libavformat57. 49.100 / 57. 49.100
   libavdevice57.  0.102 / 57.  0.102
   libavfilter 6. 62.100 /  6. 62.100
   libswscale  4.  1.100 /  4.  1.100
   libswresample   2.  1.100 /  2.  1.100
   libpostproc54.  0.100 / 54.  0.100
 https://s3.amazonaws.com/slffmpegdebug/seekProb/seekProb.m3u8: could not
 seek to position 1.400
 Input #0, hls,applehttp, from
 'https://s3.amazonaws.com/slffmpegdebug/seekProb/seekProb.m3u8':
   Duration: 00:01:05.07, start: 1.40, bitrate: 0 kb/s
   Program 0
 Metadata:
   variant_bitrate : 0
 Stream #0:0: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p,
 1280x720 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
 Metadata:
   variant_bitrate : 0
 Stream #0:1: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz,
 stereo, fltp
 Metadata:
   variant_bitrate : 0
 [image2 @ 0x26f12a0] Using AVStream.codec to pass codec parameters to
 muxers is deprecated, use AVStream.codecpar instead.
 Output #0, image2, to 'dude.png':
   Metadata:
 encoder : Lavf57.49.100
 Stream #0:0: Video: png, rgb24, 1280x720 [SAR 1:1 DAR 16:9], q=2-31,
 200 kb/s, 29.97 fps, 29.97 tbn, 29.97 tbc
 Metadata:
   variant_bitrate : 0
   encoder : Lavc57.57.100 png
 Stream mapping:
   Stream #0:0 -> #0:0 (h264 (native) -> png (native))
 Press [q] to stop, [?] for help
 frame=1 fps=0.0 q=-0.0 Lsize=N/A time=00:00:05.07 bitrate=N/A speed=
 11x
 video:570kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB
 muxing overhead: unknown

 }}}

 I did notice the message {{{could not seek to position 1.400}}} although I
 asked 0.

 In any case it doesn't give the same image as
 (notice the absence of -ss 0)

 {{{
 % rm -f dude.png ; ./ffmpeg -y -vsync 0 -i
 https://s3.amazonaws.com/slffmpegdebug/seekProb/seekProb.m3u8 -f image2
 -q:v 1 -vframes 1  dude.png ; feh dude.png
 ffmpeg version N-81699-g590f025 Copyright (c) 2000-2016 the FFmpeg
 developers
   built with gcc 5.2.1 (Ubuntu 5.2.1-22ubuntu2) 20151010
   configuration: --enable-gpl --enable-libx264 --enable-nonfree --enable-
 libfdk-aac --enable-openssl --enable-static
   libavutil  55. 29.100 / 55. 29.100
   libavcodec 57. 57.100 / 57. 57.100
   libavformat57. 49.100 / 57. 49.100
   libavdevice57.  0.102 / 57.  0.102
   libavfilter 6. 62.100 /  6. 62.100
   libswscale  4.  1.100 /  4.  1.100
   libswresample   2.  1.100 /  2.  1.100
   libpostproc54.  0.100 / 54.  0.100
 Input #0, hls,applehttp, from
 'https://s3.amazonaws.com/slffmpegdebug/seekProb/seekProb.m3u8':
   Duration: 00:01:05.07, start: 1.40, bitrate: 0 kb/s
   Program 0
 Metadata:
   variant_bitrate : 0
 Stream #0:0: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p,
 1280x720 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
 Metadata:
   variant_bitrate : 0
 Stream #0:1: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz,
 stereo, fltp
 Metadata:
   variant_bitrate : 0
 [image2 @ 0x27d9800] Using AVStream.codec to pass codec parameters to
 muxers is deprecated, use AVStream.codecpar instead.
 Output #0, image2, to 'dude.png':
   Metadata:
 encoder : Lavf57.49.100
 Stream #0:0: Video: png, rgb24, 1280x720 [SAR 1:1 DAR 16:9], q=2-31,
 200 kb/s, 29.97 fps, 29.97 tbn, 29.97 tbc
 Metadata:
   variant_bitrate : 0
   encoder : Lavc57.57.100 png
 Stream mapping:
   Stream #0:0 -> #0:0 (h264 (native) -> png (native))
 Press [q] to stop, [?] for help
 frame=1 fps=0.0 q=-0.0 Lsize=N/A 

Re: [FFmpeg-trac] #5611(avcodec:closed): rscc: support 8bpp

[FFmpeg]

#5611: rscc: support 8bpp
-+---
 Reporter:  ami_stuff|Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  rscc |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---

Comment (by ami_stuff):

 http://www.megafileupload.com/fX92/screen.png

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

Re: [FFmpeg-trac] #5519(avcodec:open): support matrox uncompressed alpha sd & hd (m103 & m104)

[FFmpeg]

#5519: support matrox uncompressed alpha sd & hd (m103 & m104)
-+---
 Reporter:  ami_stuff|Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  matrox   |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---

Comment (by cehoyos):

 Replying to [comment:2 richardpl]:
 > Files are gone and http://samples.ffmpeg.org/ffmpeg-
 bugs/trac/ticket5519/ is empty.
 Should be fixed, thank you!

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

Re: [FFmpeg-trac] #5611(avcodec:closed): rscc: support 8bpp

[FFmpeg]

#5611: rscc: support 8bpp
-+---
 Reporter:  ami_stuff|Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  rscc |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---

Comment (by richardpl):

 Provide video screenshoot.

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

 Yes, it's autodetected by Cool Edit Pro.

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

Re: [FFmpeg-trac] #5611(avcodec:closed): rscc: support 8bpp

[FFmpeg]

#5611: rscc: support 8bpp
-+---
 Reporter:  ami_stuff|Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  rscc |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---

Comment (by ami_stuff):

 Thanks, but it looks like I forgot to mention in the first message that
 this vid should decode in color. Is this possible to implement that way?

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

Re: [FFmpeg-trac] #5519(avcodec:open): support matrox uncompressed alpha sd & hd (m103 & m104)

[FFmpeg]

#5519: support matrox uncompressed alpha sd & hd (m103 & m104)
-+---
 Reporter:  ami_stuff|Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  matrox   |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---

Comment (by richardpl):

 Files are gone and http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket5519/
 is empty.

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

Re: [FFmpeg-trac] #5611(avcodec:closed): rscc: support 8bpp

[FFmpeg]

#5611: rscc: support 8bpp
-+---
 Reporter:  ami_stuff|Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  rscc |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---
Changes (by richardpl):

 * status:  open => closed
 * resolution:   => fixed


Comment:

 Fixed in 590f025b3dc078a6be58b36c67d87499f62b521c.

--
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 richardpl):

 Is this format auto detected by programs that support such files?

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

Re: [FFmpeg-trac] #4437(avdevice:open): AVFoundation recording has consistent intermittent frame drops

[FFmpeg]

#4437: AVFoundation recording has consistent intermittent frame drops
-+-
 Reporter:  LordHDL  |Owner:  mateo
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avdevice
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
  avfoundation bounty|  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by LordHDL):

 All right so I have yet ''more'' information that might be helpful.  I
 have these 2 videos recorded via Syphon Recorder (couldn't use PixelToy
 because it didn't work with Syphon Inject):

 (Ignore registration prompt and download directly.)

 https://www.dropbox.com/s/2wg1hwydxomdgaa/60.mkv?dl=0
 https://www.dropbox.com/s/l56iuma9hrz9uum/AFAP.mkv?dl=0

 The first one is very similar to the videos I get when recording using
 ffmpeg.  The second is perfectly smooth.  The difference is in choosing a
 number frame rate versus "As Fast As Possible" in the preferences.  Here
 are their average rates respectively:

 [[Image(https://puu.sh/rgumQ/57d2f5abed.png)]]
 [[Image(https://puu.sh/rgumk/7e86c11bd3.png)]]

 The source in question does not run higher than 60 FPS anyway, so choosing
 "As Fast As Possible" nets every possible frame it can deliver, resulting
 in a perfect video.

 Is there a way to set ffmpeg to record "as fast as possible" with
 AVFoundation screen capture?  I think that may be a good workaround for
 this issue for the time being.

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

Re: [FFmpeg-trac] #5852(avcodec:new): ProRes Color range tags not working

[FFmpeg]

#5852: ProRes Color range tags not working
-+-
 Reporter:  RuudKaag |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  prores,  |   Blocked By:
  color range|  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by RuudKaag):

 I Just ran the string with prores_ks, unfortunately the result is exactly
 the same as the regular prores decoder.

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

Re: [FFmpeg-trac] #5852(avcodec:new): ProRes Color range tags not working

[FFmpeg]

#5852: ProRes Color range tags not working
-+-
 Reporter:  RuudKaag |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  prores,  |   Blocked By:
  color range|  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by cehoyos):

 Does it work better with {{{-c:v prores_ks}}}?

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

Re: [FFmpeg-trac] #5852(avcodec:new): ProRes Color range tags not working

[FFmpeg]

#5852: ProRes Color range tags not working
-+-
 Reporter:  RuudKaag |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  prores,  |   Blocked By:
  color range|  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by RuudKaag):

 Hi cehoyos,

 Sorry, i'm not sure.
 As far as i can tell the source file is read properly and when i create a
 H264 mp4 from the source file with the color tags it works just fine.
 So i'm guessing its the Encoder.

 This is my first time posting so apologies for my lack of knowledge and
 poor description on the issue.

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

Re: [FFmpeg-trac] #5852(avcodec:new): ProRes Color range tags not working

[FFmpeg]

#5852: ProRes Color range tags not working
-+-
 Reporter:  RuudKaag |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  prores,  |   Blocked By:
  color range|  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * component:  ffmpeg => avcodec


Comment:

 Is this an issue with the decoder or the encoder?

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

[FFmpeg-trac] #5852(ffmpeg:new): ProRes Color range tags not working

[FFmpeg]

#5852: ProRes Color range tags not working
-+-
 Reporter:  RuudKaag | Type:  defect
   Status:  new  | Priority:  normal
Component:  ffmpeg   |  Version:  git-
 Keywords:  prores,  |  master
  color range|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Hi guys,

 I've run in to some problems while trying to convert ProRes XQ to any
 form ProRes 422.

 Summary of the bug:

 The ProRes XQ files i get from Autodesk Flame contains bt709 color
 space, color transfer and color primaries tags.
 When i encode it to any ProRes 422 format those values are specified as
 unknown and N/A
 (Similar issue goes for sample aspect ratio and display aspect ratio in
 the video filter by the way
 But not my immediate concern)

 The issue is that our Source ProRes contains data levels.
 I want to get my ProRes 422 to display legal range as the encoded file is
 scaled to legal.
 But for some reason the ProRes 422 produced with ffmpeg seems to display
 as data levels.
 I've encoded the file using Adobe Media encoder as well and the waveforms
 of both ProRes 422's are identical but display different colors in
 Quicktime 7, 10 and Telestream Switch.

 (I know some people will say that i should not rely on Quicktime but the
 thing is most (if not all) of our clients are.)

 Plus the ProRes 422 encoded in Media Encoder displays the image just fine
 in all players mentioned above.
 I'm guessing this has to do with the color tags not coming thru.

 Perhaps i'm just looking in the wrong direction to fix this issue but if
 anyone has anything on the matter please let me know.

 I've attached the Source file, ffmpeg log and the ffprobe logs of both
 source and encoded ffmpeg and Media Encoder ProRes422 on the following
 link:

 ftp://ffmpeg:c684!t...@ftp.theambassadors.nl

 How to reproduce:
 {{{
 % ffmpeg -i input -y -c:v prores -profile:v 1 -pix_fmt yuv422p10le -vf
 scale=1920x1080,setsar=1/1,setdar=16/9 -colorspace bt709 -color_primaries
 bt709 -color_trc bt709 output
 ffmpeg version 3.1.3
 }}}

 If there are any questions or if i left some specific details out, please
 let me know.

 Thanks in advance,

 Ruud Kaag
 Media Manager
 Ambassadors Studio

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

Re: [FFmpeg-trac] #5437(avcodec:open): mpeg-4 als: support 32bit floating point

[FFmpeg]

#5437: mpeg-4 als: support 32bit floating point
-+-
 Reporter:  ami_stuff|Owner:
 Type:  enhancement  |  thilo.borgmann
 Priority:  wish |   Status:  open
  Version:  git-master   |Component:  avcodec
 Keywords:  als  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  1|  Reproduced by developer:  1
-+-

Comment (by ami_stuff):

 Replying to [comment:5 thilo.borgmann]:
 > What encoder did produce this sample?
 >
 > Also this sample is not available anymore on datafilehost...


 just do:

 C:\>C:\mp4alsRM23win\mp4alsRM23.exe -MP4 C:\mp4als_out.wav

 and try decoding output mp4 file with ffmpeg

 http://www.megafileupload.com/k9am/mp4als_out.wav

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

Re: [FFmpeg-trac] #5846(avformat:open): Support writing BOM in SRT muxer

[FFmpeg]

#5846: Support writing BOM in SRT muxer
-+
 Reporter:  edumj|Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  srt  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+
Changes (by cehoyos):

 * keywords:   => srt
 * priority:  normal => wish
 * version:  unspecified => git-master
 * status:  reopened => open


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

Re: [FFmpeg-trac] #5297(avcodec:open): mpeg-4 als: "predictor order too large"

[FFmpeg]

#5297: mpeg-4 als: "predictor order too large"
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |  thilo.borgmann
 Priority:  important|   Status:  open
  Version:  git-master   |Component:  avcodec
 Keywords:  als  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+-

Comment (by cehoyos):

 Should be fixed.

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

Re: [FFmpeg-trac] #5297(avcodec:open): mpeg-4 als: "predictor order too large"

[FFmpeg]

#5297: mpeg-4 als: "predictor order too large"
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |  thilo.borgmann
 Priority:  important|   Status:  open
  Version:  git-master   |Component:  avcodec
 Keywords:  als  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+-

Comment (by cehoyos):

 I'll try to fix the permissions later today, sorry!

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

Re: [FFmpeg-trac] #5297(avcodec:open): mpeg-4 als: "predictor order too large"

[FFmpeg]

#5297: mpeg-4 als: "predictor order too large"
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |  thilo.borgmann
 Priority:  important|   Status:  open
  Version:  git-master   |Component:  avcodec
 Keywords:  als  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * cc: thilo.borgmann (added)


Comment:

 Please search hard in http://samples.ffmpeg.org/ffmpeg-bugs/trac/

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

Re: [FFmpeg-trac] #5437(avcodec:open): mpeg-4 als: support 32bit floating point

[FFmpeg]

#5437: mpeg-4 als: support 32bit floating point
-+-
 Reporter:  ami_stuff|Owner:
 Type:  enhancement  |  thilo.borgmann
 Priority:  wish |   Status:  open
  Version:  git-master   |Component:  avcodec
 Keywords:  als  |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  1|  Reproduced by developer:  1
-+-

Comment (by thilo.borgmann):

 What encoder did produce this sample?

 Also this sample is not available anymore on datafilehost...

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

Re: [FFmpeg-trac] #5297(avcodec:open): mpeg-4 als: "predictor order too large"

[FFmpeg]

#5297: mpeg-4 als: "predictor order too large"
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |  thilo.borgmann
 Priority:  important|   Status:  open
  Version:  git-master   |Component:  avcodec
 Keywords:  als  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+-

Comment (by thilo.borgmann):

 I cannot download it from datafilehost anymore.
 Please attach it to the ticket or send me a private mail with the sample.

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

Re: [FFmpeg-trac] #5846(avformat:reopened): Support writing BOM in SRT muxer (was: Extract text subtitles in UTF-8 with BOM)

[FFmpeg]

#5846: Support writing BOM in SRT muxer
-+
 Reporter:  edumj|Owner:
 Type:  enhancement  |   Status:  reopened
 Priority:  normal   |Component:  avformat
  Version:  unspecified  |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+
Changes (by ubitux):

 * status:  closed => reopened
 * resolution:  needs_more_info =>
 * component:  undetermined => avformat


Comment:

 I think it makes sense to add an option to do that in the muxer.

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

Re: [FFmpeg-trac] #5744(undetermined:closed): Error when converting mov to mp4 "ratecontrol_init: can't open stats file" , "Error while opening encoder for output stream #0:0 - maybe incorrect paramet

[FFmpeg]

#5744: Error when converting mov to mp4 "ratecontrol_init: can't open stats 
file"
, "Error while opening encoder for output stream #0:0 - maybe incorrect
parameters such as bit_rate, rate, width or height"
-+-
 Reporter:  LaravelDude  |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  libx264  |   Resolution:
 Blocking:   |  needs_more_info
Analyzed by developer:  0|   Blocked By:
 |  Reproduced by developer:  0
-+-
Changes (by cehoyos):

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


Comment:

 Please reopen this ticket if you can provide more information.

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

Re: [FFmpeg-trac] #5799(undetermined:new): Memory psudo-leak when FF_API_CODED_FRAME enabled

[FFmpeg]

#5799: Memory psudo-leak when FF_API_CODED_FRAME enabled
-+-
 Reporter:  DeHackEd |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:  cc   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:   => cc


Comment:

 Is this also reproducible if the input stream does not contain Closed
 Captions?

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

Re: [FFmpeg-trac] #5846(undetermined:closed): Extract text subtitles in UTF-8 with BOM

[FFmpeg]

#5846: Extract text subtitles in UTF-8 with BOM
-+-
 Reporter:  edumj|Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |  needs_more_info
Analyzed by developer:  0|   Blocked By:
 |  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 Did you at any point test the original !SupRip executable to verify if it
 puts a BOM in front of text files?

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

Re: [FFmpeg-trac] #5847(undetermined:closed): Duration estimate and bitrate calculation wrong when file is over 4Gb

[FFmpeg]

#5847: Duration estimate and bitrate calculation wrong when file is over 4Gb
-+-
 Reporter:  petere   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  mpegps   |   Resolution:  duplicate
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by cehoyos):

 Did you test with analyzeduration?

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