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

 Last command works here, make sure you use latest ffmpeg.

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

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

 Sorry, but I can't figure out how to use scale2ref.

 This example from [https://ffmpeg.org/ffmpeg-filters.html#scale2ref here]:
 {{{
 • Scale a subtitle stream to match the main video in size before
 overlaying
 'scale2ref[b][a];[a][b]overlay'
 }}}
 doesn't work.

 I don't understand how to do something like this with scale2ref:

 {{{
 -filter_complex "[0:v][0:s:0]overlay[out]" -map "[out]"
 }}}

 The closest I've done is this:
 {{{
 -filter_complex "[subteees]scale2ref[0:s:0][0:v];[0:v][0:s:0]overlay[out]"
 -map "[out]"
 }}}
 But I don't know why it works with some names like "sub", "subs",
 "subteees", etc, but not with "ein" for example. But video is very
 pixelated, and runs at 1000 fps!!

 or with one example I found like this:

 {{{
 -filter_complex "[0:s:0][0:v]scale2ref[subs][0:v];[0:v][subs]overlay[out]"
 -map "[out]"
 }}}
 But doesn't even 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] #5643(avformat:closed): FFmpeg unable to decode DnxHD 145 in MXF

[FFmpeg]

#5643: FFmpeg unable to decode DnxHD 145 in MXF
+
 Reporter:  steved  |Owner:
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:  fixed
 Keywords:  mxf dnxhd   |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by richardpl):

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


Comment:

 Fixed by Mark Reid in d8d433321796c3eaf47d93e1091a20cbd3c44bda.

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

Re: [FFmpeg-trac] #5579(avcodec:reopened): Random green block artifacts when decoding H264 streams

[FFmpeg]

#5579: Random green block artifacts when decoding H264 streams
+
 Reporter:  anouar  |Owner:
 Type:  defect  |   Status:  reopened
 Priority:  normal  |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  H264|   Blocked By:
 Blocking:  |  Reproduced by developer:  1
Analyzed by developer:  0   |
+

Comment (by anouar):

 Hi Cehoyos,

 I have tried the latest ffmpeg windows build version: 11777eb
 (2016-09-19), and I'm still seeing the same problem. Please, is there any
 update on this ticket? and is it possible to update its priority from
 normal to important since there are many customers using VLC player and
 complaining about those green block artifacts?

 Best regards,
 Anouar

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

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

 Is not the same as canvas_size? I've tried canvas_size and didn't work
 with DVD subs, I think only worked with DVB subs.

 Thanks, I'll try scale2ref.

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

Re: [FFmpeg-trac] #5369(undetermined:open): new audiotoolbox encoder does not support AAC encoding with more than 2 channels

[FFmpeg]

#5369: new audiotoolbox encoder does not support AAC encoding with more than 2
channels
-+-
 Reporter:  julian   |Owner:  11rcombs
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
  audiotoolbox osx   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by richardpl):

 Looking at source code 5.1 is not supported, but 5.1(side) is.

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

Re: [FFmpeg-trac] #5686(avformat:new): Concat Demuxer doesn't work, Concat Protocol does, but too many files!

[FFmpeg]

#5686: Concat Demuxer doesn't work, Concat Protocol does, but too many files!
-+
 Reporter:  EJacobs  |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  concat   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by richardpl):

 Use cat.

--
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|
-+

Comment (by edumj):

 Replying to [comment:9 ubitux]:
 > Replying to [comment:7 edumj]:
 > > ubitux, you mean add it to muxer or demuxer?
 >
 > Muxer since you want to produce srt files with a BOM. Text subtitles
 demuxers already handle them.

 Ok, but I though muxer means join streams, and demuxer means extract them.

--
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|
-+

Comment (by edumj):

 Replying to [comment:8 cehoyos]:
 > Replying to [comment:7 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.
 >
 > Does Suprip.exe write a BOM or not?

 Subrip.exe doesn't seem to write UTF-8, and AFAIK BOM is only for UTF, so
 the answer is not.

 Anyway, why you ask me about Subrip.exe? It has nothing to do with this
 workflow, since I'm not ripping Dvd subs to text.

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

Re: [FFmpeg-trac] #5856(undetermined:new): filter_complex significantly slower than -vf for the same task.

[FFmpeg]

#5856: filter_complex significantly slower than -vf for the same task.
-+-
 Reporter:  Zibri|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by richardpl):

 Could you try with same encoding parameters, same '''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] #5672(avformat:closed): concat demuxer truncates output duration

[FFmpeg]

#5672: concat demuxer truncates output duration
-+-
 Reporter:  jseeley78|Owner:
 Type:  defect   |   Status:  closed
 Priority:  important|Component:  avformat
  Version:  3.0.2|   Resolution:  fixed
 Keywords:  concat   |   Blocked By:
  regression |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by richardpl):

 * status:  open => closed
 * resolution:   => 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] #5807(avcodec:closed): Add YUV420P10 to vaapi hardware decode

[FFmpeg]

#5807: Add YUV420P10 to vaapi hardware decode
-+---
 Reporter:  lethalwp |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:  invalid
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Changes (by richardpl):

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


Comment:

 This is not bug report, instead ping patch on mailing list.

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

Re: [FFmpeg-trac] #3247(avcodec:open): Transparent subtitle outlines (IDX/SUB) upon conversion to XSUB become solid, and colors become b

[FFmpeg]

#3247: Transparent subtitle outlines (IDX/SUB) upon conversion to XSUB become
solid, and colors become b
-+---
 Reporter:  userid99 |Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  xsub |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---

Comment (by richardpl):

 xsub, with tag DXSB does not support alpha. It knows only about background
 which is always transparent and foreground which is not transparent.
 DXSA on other hand have support for alpha, but xsub encoder does not
 support it.

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

Re: [FFmpeg-trac] #5856(undetermined:new): filter_complex significantly slower than -vf for the same task.

[FFmpeg]

#5856: filter_complex significantly slower than -vf for the same task.
-+-
 Reporter:  Zibri|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by richardpl):

 One command uses preset slow and another one uses preset fast.
 I failed to reproduce using just overlay and movie 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] #5856(undetermined:new): filter_complex significantly slower than -vf for the same task.

[FFmpeg]

#5856: filter_complex significantly slower than -vf for the same task.
-+-
 Reporter:  Zibri|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by Zibri):

 if you read my ticket, you will understand if it is an issue or not. In my
 opinion it is an issue (multiple ones).

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

[FFmpeg-trac] #5856(undetermined:new): filter_complex significantly slower than -vf for the same task.

[FFmpeg]

#5856: filter_complex significantly slower than -vf for the same task.
-+-
 Reporter:  Zibri| Type:  defect
   Status:  new  | Priority:  important
Component:   |  Version:
  undetermined   |  unspecified
 Keywords:   |   Blocked By:
  vf,filter_complex,speed,bitrate|  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
 To record from webcam and microphone and overlay a resized logo, using
 complex_filter I achieve about 20fps (on a fast pc with less than 15% cpu
 load), using the same features but with -vf I get full realtime 30fps...
 I know this is normal because the complex filter has more options and it's
 more flexible, but IMHO this should not happen...

 Example:
 Record live feed from webcam and microphone, overlay a logo and save to
 flv..

 ffmpeg -f dshow -video_size qpal -rtbufsize 1G -copyts -framerate 30 -i
 video="BisonCam, NB Pro" -i "C:\Users\Zibri\Downloads\scdc.png"
 -filter_complex "[1]scale=80x60,[0]overlay=W-w-5:H-h-5" -f dshow -i
 audio="Microphone (Realtek High Definition Audio)"  -codec:v libx264
 -preset fast -b:v 500k -b:a 128k -minrate 500k -maxrate 500k -bufsize
 1500k -f flv test7.flv

 result:

 {{{
 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, dshow, from 'video=BisonCam, NB Pro':
   Duration: N/A, start: 128270.189000, bitrate: N/A
 Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc,
 bt470bg/unknown/unknown), 352x288, 30 fps, 30 tbr, 1k tbn, 1k tbc
 Input #1, png_pipe, from 'C:\Users\Zibri\Downloads\scdc.png':
   Duration: N/A, bitrate: N/A
 Stream #1:0: Video: png, rgba(pc), 244x224 [SAR 5905:5905 DAR 61:56],
 25 tbr, 25 tbn, 25 tbc
 Guessed Channel Layout for Input Stream #2.0 : stereo
 Input #2, dshow, from 'audio=Microphone (Realtek High Definition Audio)':
   Duration: N/A, start: 128270.631000, bitrate: 1411 kb/s
 Stream #2:0: Audio: pcm_s16le, 44100 Hz, 2 channels, s16, 1411 kb/s
 File 'test7.flv' already exists. Overwrite ? [y/N] y
 [swscaler @ 074504a0] deprecated pixel format used, make sure you
 did set range correctly
 No pixel format specified, yuvj420p for H.264 encoding chosen.
 Use -pix_fmt yuv420p for compatibility with outdated media players.
 [libx264 @ 02627c00] using cpu capabilities: MMX2 SSE2Fast SSSE3
 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
 [libx264 @ 02627c00] profile High, level 1.3
 [libx264 @ 02627c00] 264 - core 148 r2705 3f5ed56 - H.264/MPEG-4
 AVC codec - Copyleft 2003-2016 - http://www.videolan.org/x264.html -
 options: cabac=1 ref=2 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=6
 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1
 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=9
 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0
 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=1 keyint=250 keyint_min=25
 scenecut=40 intra_refresh=0 rc_lookahead=30 rc=cbr mbtree=1 bitrate=500
 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 vbv_maxrate=500
 vbv_bufsize=1500 nal_hrd=none filler=0 ip_ratio=1.40 aq=1:1.00
 [flv @ 026ae8e0] Using AVStream.codec to pass codec parameters to
 muxers is deprecated, use AVStream.codecpar instead.
 Last message repeated 1 times
 Output #0, 

Re: [FFmpeg-trac] #5856(undetermined:new): filter_complex significantly slower than -vf for the same task.

[FFmpeg]

#5856: filter_complex significantly slower than -vf for the same task.
-+-
 Reporter:  Zibri|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:  vf,filter_complex,speed,bitrate =>
 * priority:  important => normal
 * version:  unspecified => git-master


Comment:

 Replying to [ticket:5856 Zibri]:
 > Can you explain this behaviour and why the fps is so different while
 recording?

 Do you need support or do you want to report an 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] #4815(avcodec:reopened): DNxHD help output looks broken / is useless wrt framerates

[FFmpeg]

#4815: DNxHD help output looks broken / is useless wrt framerates
+
 Reporter:  cehoyos |Owner:
 Type:  defect  |   Status:  reopened
 Priority:  minor   |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  dnxhd   |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by cehoyos):

 The help output is currently both incomplete and not helpful:
 One solution is to remove the useless part, if you have a better solution,
 that is fine but the issue is not 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] #4815(avcodec:reopened): DNxHD help output looks broken / is useless wrt framerates

[FFmpeg]

#4815: DNxHD help output looks broken / is useless wrt framerates
+
 Reporter:  cehoyos |Owner:
 Type:  defect  |   Status:  reopened
 Priority:  minor   |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  dnxhd   |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by richardpl):

 But that bug is unrelated to this one.

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

Re: [FFmpeg-trac] #4815(avcodec:closed): DNxHD help output looks broken / is useless wrt framerates

[FFmpeg]

#4815: DNxHD help output looks broken / is useless wrt framerates
+---
 Reporter:  cehoyos |Owner:
 Type:  defect  |   Status:  closed
 Priority:  minor   |Component:  avcodec
  Version:  git-master  |   Resolution:  invalid
 Keywords:  dnxhd   |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---
Changes (by richardpl):

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


Comment:

 What is not clear about that specification should be followed?

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

Re: [FFmpeg-trac] #4815(avcodec:reopened): DNxHD help output looks broken / is useless wrt framerates

[FFmpeg]

#4815: DNxHD help output looks broken / is useless wrt framerates
+
 Reporter:  cehoyos |Owner:
 Type:  defect  |   Status:  reopened
 Priority:  minor   |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  dnxhd   |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by cehoyos):

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


Comment:

 If the specification has to be followed, then there is a bug: FFmpeg
 currently accepts all framerates (as does the avid software as users
 reported).

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

Re: [FFmpeg-trac] #4815(avcodec:reopened): DNxHD help output looks broken / is useless wrt framerates

[FFmpeg]

#4815: DNxHD help output looks broken / is useless wrt framerates
+
 Reporter:  cehoyos |Owner:
 Type:  defect  |   Status:  reopened
 Priority:  minor   |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  dnxhd   |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by cehoyos):

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


Comment:

 Please elaborate.

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

Re: [FFmpeg-trac] #3657(swscale:open): float pixel format

[FFmpeg]

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

 We would like to have this too.

 The use case is high bit depth processing in HDR mode where we want to be
 able to have super white/black (i.e. < 0.0 and > 1.0 values) at certain
 stages in the processing. Using floats is simpler to work with than 32bit
 integers with headroom and still has enough precision. We also do some
 advanced image processing which requires conversion to float at some point
 so having the conversion early is beneficial for performance for us.

 As one person noted earlier floats have higher precision around 0.0 than
 1.0,but in the range [0.5, 1.0] you still have 23 bits per component in
 precision which is enough.

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

Re: [FFmpeg-trac] #4815(avcodec:closed): DNxHD help output looks broken / is useless wrt framerates

[FFmpeg]

#4815: DNxHD help output looks broken / is useless wrt framerates
+---
 Reporter:  cehoyos |Owner:
 Type:  defect  |   Status:  closed
 Priority:  minor   |Component:  avcodec
  Version:  git-master  |   Resolution:  invalid
 Keywords:  dnxhd   |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---
Changes (by richardpl):

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


Comment:

 Specification should be followed. Framerates are integral part of
 bitstream.

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

Re: [FFmpeg-trac] #4703(undetermined:new): Audio cut off in screencast

[FFmpeg]

#4703: Audio cut off in screencast
-+-
 Reporter:  hendry   |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):

 Happens also on Fedora 23, as reported by rhn on irc.

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

Re: [FFmpeg-trac] #3023(avformat:new): Information lost when remuxing DTS from MKV to MP4

[FFmpeg]

#3023: Information lost when remuxing DTS from MKV to MP4
+
 Reporter:  Nemesis7|Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:
 Keywords:  mov |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by cehoyos):

 The fact that a channel count of "2" is written to the stsd atom can be
 reproduced with:
 {{{
 $ ffmpeg -i fate-suite/dts/dts.ts -acodec copy out.mp4
 }}}

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

 Replying to [comment:14 RuudKaag]:
 > I don't suppose there's a similar solution for the sample aspect ratio
 en display aspect ratio is there? 0:-)

 For some reason mov muxer does not write sample aspect ratio if nominator
 and denominator are same. So only way to fix this is to patch 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] #5855(avfilter:closed): Feature request: apply same adelay values to all channels

[FFmpeg]

#5855: Feature request: apply same adelay values to all channels
-+
 Reporter:  mulvya   |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avfilter
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  adelay   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by mulvya):

 '''adelay=all=2000''' for 2000ms delay applied to all channels. Thanks.

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

 Replying to [comment:14 RuudKaag]:
 > I don't suppose there's a similar solution for the sample aspect ratio
 en display aspect ratio is there? 0:-)
 Please elaborate (ideally on the user mailing list)!

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

Re: [FFmpeg-trac] #3023(avformat:new): Information lost when remuxing DTS from MKV to MP4

[FFmpeg]

#3023: Information lost when remuxing DTS from MKV to MP4
+
 Reporter:  Nemesis7|Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:
 Keywords:  mov |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by richardpl):

 Samples are gone.

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

Re: [FFmpeg-trac] #5101(avformat:reopened): Variables used uninitialized in libavformat/utils.c

[FFmpeg]

#5101: Variables used uninitialized in libavformat/utils.c
+
 Reporter:  jeremyhu|Owner:
 Type:  defect  |   Status:  reopened
 Priority:  minor   |Component:  avformat
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by cehoyos):

 Isn't the question if the standard allows to pass uninitialized
 parameters?

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

 Thanks richardpl!
 Works like a charm.
 I don't suppose there's a similar solution for the sample aspect ratio en
 display aspect ratio is there? 0:-)

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

Re: [FFmpeg-trac] #5855(avfilter:closed): Feature request: apply same adelay values to all channels

[FFmpeg]

#5855: Feature request: apply same adelay values to all channels
-+
 Reporter:  mulvya   |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avfilter
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  adelay   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by richardpl):

 Please give full command incarnation how it should look like.

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

Re: [FFmpeg-trac] #3841(avcodec:open): support MYUV 10-bit & 8-bit 4:2:2 YUV

[FFmpeg]

#3841: support MYUV 10-bit & 8-bit 4:2:2 YUV
-+---
 Reporter:  ami_stuff|Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---

Comment (by richardpl):

 This is just uyvy422 with fields stored sequentially instead of
 interleaved, and with some padding after each field.

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

Re: [FFmpeg-trac] #5101(avformat:reopened): Variables used uninitialized in libavformat/utils.c

[FFmpeg]

#5101: Variables used uninitialized in libavformat/utils.c
+
 Reporter:  jeremyhu|Owner:
 Type:  defect  |   Status:  reopened
 Priority:  minor   |Component:  avformat
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by heleppkes):

 The compiler seems to complain about passing an uninitialized variable to
 another function, but not actually checking if that function uses it under
 the given conditions.

 Last I checked this code, it did not actually use these variables
 uninitialized, however the design might not be very easy to understand
 since it spans more then one function, and these variables are passed as
 arguments in between.

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

Re: [FFmpeg-trac] #5855(avfilter:closed): Feature request: apply same adelay values to all channels

[FFmpeg]

#5855: Feature request: apply same adelay values to all channels
-+
 Reporter:  mulvya   |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avfilter
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  adelay   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by mulvya):

 You could assign '''all'''

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

Re: [FFmpeg-trac] #5101(avformat:closed): Variables used uninitialized in libavformat/utils.c

[FFmpeg]

#5101: Variables used uninitialized in libavformat/utils.c
+
 Reporter:  jeremyhu|Owner:
 Type:  defect  |   Status:  closed
 Priority:  minor   |Component:  avformat
  Version:  git-master  |   Resolution:  fixed
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by richardpl):

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


Comment:

 They '''are''' accessed if they are uninitialized.

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

Re: [FFmpeg-trac] #5101(avformat:reopened): Variables used uninitialized in libavformat/utils.c

[FFmpeg]

#5101: Variables used uninitialized in libavformat/utils.c
+
 Reporter:  jeremyhu|Owner:
 Type:  defect  |   Status:  reopened
 Priority:  minor   |Component:  avformat
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by richardpl):

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


Comment:

 They '''are''' accessed if they are uninitialized.

--
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|
-+

Comment (by ubitux):

 Replying to [comment:7 edumj]:
 > ubitux, you mean add it to muxer or demuxer?

 Muxer since you want to produce srt files with a BOM. Text subtitles
 demuxers already handle them.

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

Re: [FFmpeg-trac] #5855(avfilter:closed): Feature request: apply same adelay values to all channels

[FFmpeg]

#5855: Feature request: apply same adelay values to all channels
-+
 Reporter:  mulvya   |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avfilter
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  adelay   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by richardpl):

 If you really want this, give option name that will trigger same adelay
 value for all channels.

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

Re: [FFmpeg-trac] #5855(avfilter:closed): Feature request: apply same adelay values to all channels

[FFmpeg]

#5855: Feature request: apply same adelay values to all channels
-+
 Reporter:  mulvya   |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avfilter
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  adelay   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+
Changes (by richardpl):

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


Comment:

 You can use adelay='5|5|5|5|5|5|5|5|5'.. up to very high number.
 Unused entries are ignored.

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

 Workaround is to add '''-movflags +write_colr''' before output.

--
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 figured as much.
 Same goes for video filters like set_sar and set_dar.
 Could it be that the options and filters are just not being passed thru to
 the prores encoder or something?
 I'm not sure what that value is or does, i'm a complete noob in
 programming stuff like this sorry for that.

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

 Problem is that somehow your -color* options are ignored and always
 unspecified, '''2''' value is stored in bitstream.

--
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'm sorry,

 The source file should be there now.

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

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

 '''ftp://ftp.theambassadors.nl/Source/''' is empty 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] #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've put the sample and the ffprobe result of both the source, ffmpeg
 prores and media encoder prores in the following ftp link.

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

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

 Please provide input sample you use.

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

Re: [FFmpeg-trac] #5855(avfilter:new): Feature request: apply same adelay values to all channels

[FFmpeg]

#5855: Feature request: apply same adelay values to all channels
-+
 Reporter:  mulvya   |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avfilter
  Version:  git-master   |   Resolution:
 Keywords:  adelay   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by mulvya):

 Sample: http://samples.ffmpeg.org/mov/weirdedl.mp4

 Command:
 {{{
 ffmpeg -t 10 -i weirdedl.mp4 -c:v copy -af adelay=1000 adelay-1c-test.mp4
 }}}


 Console output:


 {{{
 ffmpeg version N-81692-gef42c1d Copyright (c) 2000-2016 the FFmpeg
 developers
   built with gcc 6.1.0 (Rev1, Built by MSYS2 project)
   configuration:  --enable-avisynth --enable-libmp3lame --enable-libopus
 --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265
 --disable-w32threads --enable-decklink --enable-fontconfig --enable-frei0r
 --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca
 --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm
 --enable-libilbc --enable-libmfx --enable-libmodplug --enable-libopencore-
 amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp
 --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-
 libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc
 --enable-libwavpack --enable-libwebp --enable-libxavs --enable-libxvid
 --enable-libzimg --enable-openssl --enable-libsnappy --enable-gpl
 --enable-opencl --enable-opengl --enable-libcdio --enable-libfdk-aac
 --enable-libkvazaar --enable-librubberband --enable-libssh --enable-
 libtesseract --enable-libzvbi --enable-chromaprint --enable-libebur128
 --enable-libopenh264 --enable-libopenmpt --enable-netcdf --enable-version3
 --enable-nonfree --enable-filter=frei0r --disable-debug
   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, mov,mp4,m4a,3gp,3g2,mj2, from 'weirdedl.mp4':
   Metadata:
 major_brand : isom
 minor_version   : 1
 compatible_brands: isom
 creation_time   : 2009-03-11T17:24:45.00Z
   Duration: 00:24:58.00, start: 0.083438, bitrate: 44 kb/s
 Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p,
 1280x720 [SAR 1:1 DAR 16:9], 1678 kb/s, 23.97 fps, 23.97 tbr, 12567183.00
 tbn, 47.94 tbc (default)
 Metadata:
   creation_time   : 2009-03-11T15:09:43.00Z
   handler_name: Samurai Sentai Shinkenger Act 02
 Stream #0:1(jpn): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz,
 stereo, fltp, 278 kb/s (default)
 Metadata:
   creation_time   : 2009-03-11T17:24:50.00Z
   handler_name: Japanese
 [mp4 @ 001dce20] Using AVStream.codec to pass codec parameters to
 muxers is deprecated, use AVStream.codecpar instead.
 Last message repeated 1 times
 Output #0, mp4, to 'adelay-1c-test.mp4':
   Metadata:
 major_brand : isom
 minor_version   : 1
 compatible_brands: isom
 encoder : Lavf57.49.100
 Stream #0:0(und): Video: h264 (High) ([33][0][0][0] / 0x0021),
 yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 1678 kb/s, 23.97 fps, 23.97
 tbr, 12567183.00 tbn, 12567183.00 tbc (default)
 Metadata:
   creation_time   : 2009-03-11T15:09:43.00Z
   handler_name: Samurai Sentai Shinkenger Act 02
 Stream #0:1(jpn): Audio: aac (LC) ([64][0][0][0] / 0x0040), 48000 Hz,
 stereo, fltp, 128 kb/s (default)
 Metadata:
   creation_time   : 2009-03-11T17:24:50.00Z
   handler_name: Japanese
   encoder : Lavc57.57.100 aac
 Stream mapping:
   Stream #0:0 -> #0:0 (copy)
   Stream #0:1 -> #0:1 (aac (native) -> aac (native))
 Press [q] to stop, [?] for help
 frame=  244 fps=0.0 q=-1.0 Lsize=2287kB time=00:00:13.92
 bitrate=1345.3kbits/s speed=45.5x
 video:2113kB audio:167kB subtitle:0kB other streams:0kB global headers:0kB
 muxing overhead: 0.323739%
 [aac @ 02b0cd20] Qavg: 3905.534
 }}}

 Result attached above.

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

 Nothing different than the regular prores when i look at the log and the
 eventual result.
 I've been trying to fix/get a grip of this issue in prores for over 3
 months now so there's not a lot of options left that i haven't tried.
 My guess is that the issue lies somewhere in the source code of the
 encoder, not recognising the options and filters i'm using in my string.

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

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

 For burning subtitle you first need to scale subtitle stream to size of
 video stream, see scale2ref filter.

 xsub issue is probably related to #3247.

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

Re: [FFmpeg-trac] #5855(avfilter:new): Feature request: apply same adelay values to all channels

[FFmpeg]

#5855: Feature request: apply same adelay values to all channels
-+
 Reporter:  mulvya   |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avfilter
  Version:  git-master   |   Resolution:
 Keywords:  adelay   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by cehoyos):

 Please provide a command line and complete, uncut console output.

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

Re: [FFmpeg-trac] #5855(avfilter:new): Feature request: apply same adelay values to all channels

[FFmpeg]

#5855: Feature request: apply same adelay values to all channels
-+
 Reporter:  mulvya   |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avfilter
  Version:  git-master   |   Resolution:
 Keywords:  adelay   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+
Changes (by mulvya):

 * type:  defect => enhancement


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

[FFmpeg-trac] #5855(avfilter:new): Feature request: apply same adelay values to all channels

[FFmpeg]

#5855: Feature request: apply same adelay values to all channels
--+--
 Reporter:  mulvya| Type:  defect
   Status:  new   | Priority:  wish
Component:  avfilter  |  Version:  git-master
 Keywords:  adelay|   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+--
 At present ('''N-81692-gef42c1d'''), the adelay filter requires individual
 specification of delay for each audio channel. I request a syntax that
 lets one set a uniform delay for all channels, however many those are.
 This will be very helpful during batch processing of files with varying
 number of channels, so that a single static command can be used.

 Thanks.

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

Re: [FFmpeg-trac] #4504(undetermined:open): Valgrind on arm fate client

[FFmpeg]

#4504: Valgrind on arm fate client
-+-
 Reporter:  michael  |Owner:
 Type:  task |   Status:  open
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  fateclient   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by MDavis):

 I've found that building and testing on a Raspberry Pi 1B is not
 practical. Would my soon-arriving RPi Model 3 be more suitable?

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

 ffmpeg -analyzeduration 12000 -probesize 100M -i "concat:G:\DVD
 Rip\BATMAN_BEGINS_DISC_1\VIDEO_TS\vts_01_1.vob|G:\DVD
 Rip\BATMAN_BEGINS_DISC_1\VIDEO_TS\vts_01_2.vob|G:\DVD
 Rip\BATMAN_BEGINS_DISC_1\VIDEO_TS\vts_01_3.vob|G:\DVD
 Rip\BATMAN_BEGINS_DISC_1\VIDEO_TS\vts_01_4.vob|G:\DVD
 Rip\BATMAN_BEGINS_DISC_1\VIDEO_TS\vts_01_5.vob|G:\DVD
 Rip\BATMAN_BEGINS_DISC_1\VIDEO_TS\vts_01_6.vob|G:\DVD
 Rip\BATMAN_BEGINS_DISC_1\VIDEO_TS\vts_01_7.vob"

 This gives the correct duration but does not find the 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] #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 cehoyos):

 Replying to [comment:7 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.

 Does Suprip.exe write a BOM or not?

--
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(avcodec: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:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  mxf dnxhd|   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---
Changes (by cehoyos):

 * resolution:  worksforme => fixed
 * version:  unspecified => git-master
 * component:  undetermined => avcodec
 * reproduced:  0 => 1


Comment:

 Fixed in 8395b6eeaa279cff5c1c5d2b2ddfd5be087ca3ee

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