[FFmpeg-trac] #7672(avfilter:new): “cover_rect” filter, add the RGB support to the cover image

2019-01-11 Thread FFmpeg
#7672: “cover_rect” filter, add the RGB support to the cover image
--+---
 Reporter:  Kdmeizk   | Type:  enhancement
   Status:  new   | Priority:  normal
Component:  avfilter  |  Version:  unspecified
 Keywords:|   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+---
 Currently, only [https://ffmpeg.org/ffmpeg-filters.html#cover_005frect
 yuv420] is handled.

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


[FFmpeg-trac] #7671(avfilter:new): Filters, add the RGB version of “chromahold”

2019-01-11 Thread FFmpeg
#7671: Filters, add the RGB version of “chromahold”
--+---
 Reporter:  Kdmeizk   | Type:  enhancement
   Status:  new   | Priority:  normal
Component:  avfilter  |  Version:  unspecified
 Keywords:|   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+---
 An example related to “[https://ffmpeg.org/ffmpeg-filters.html#chromahold
 chromahold]”:
 The RGB version of “[https://ffmpeg.org/ffmpeg-filters.html#chromakey
 chromakey]” is “[https://ffmpeg.org/ffmpeg-filters.html#colorkey
 colorkey]”.

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


Re: [FFmpeg-trac] #6521(avformat:open): HEIF support

2019-01-11 Thread FFmpeg
#6521: HEIF support
-+-
 Reporter:  mateo|Owner:  mateo
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  mov heif |   Blocked By:
  bounty |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by iamcarbon):

 * keywords:  mov heif => mov heif bounty


Comment:

 I put up a $300 bounty on this.

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


Re: [FFmpeg-trac] #7649(avutil:new): FFmpeg QSV initialization fails on KBL HadesCanyon (= both Intel & AMD GPUs) when DISPLAY is set

2019-01-11 Thread FFmpeg
#7649: FFmpeg QSV initialization fails on KBL HadesCanyon (= both Intel & AMD
GPUs) when DISPLAY is set
+--
 Reporter:  eero-t  |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  avutil
  Version:  git-master  |   Resolution:
 Keywords:  qsv |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+--

Comment (by eero-t):

 Specifying qsv_device makes it work, as does unsetting $DISPLAY.

 As I need to specify device already for VA-API to work, it's fine for me
 to do that also for QSV.

 Before fixing the render node selection in code, please document
 "qsv_device" usage (for multi-card use-cases) in FFmpeg QSV examples:
 https://trac.ffmpeg.org/wiki/Hardware/QuickSync

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


Re: [FFmpeg-trac] #7670(undetermined:closed): Unsupported Vorbis in .wav

2019-01-11 Thread FFmpeg
#7670: Unsupported Vorbis in .wav
-+-
 Reporter:  bagdenisov   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:  duplicate
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

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


Comment:

 See ticket #1690.

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


[FFmpeg-trac] #7670(undetermined:new): Unsupported Vorbis in .wav

2019-01-11 Thread FFmpeg
#7670: Unsupported Vorbis in .wav
-+-
 Reporter:  bagdenisov   | Type:  defect
   Status:  new  | Priority:  normal
Component:   |  Version:
  undetermined   |  unspecified
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 How to reproduce:
 {{{
 % ffmpeg -i "707 Crash.wav" -codec pcm_s16le "707 Crash_pcm.wav"
 ffmpeg version N-92944-g395e8a53fa Copyright (c) 2000-2019 the FFmpeg
 developers
   built with gcc 8.2.1 (GCC) 20181201
   configuration: --disable-static --enable-shared --enable-gpl --enable-
 version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv
 --enable-libass --enable-libbluray --enable-libfreetype --enable-
 libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-
 libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy
 --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx
 --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265
 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp
 --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-
 libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-
 libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va
 --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-
 libopenmpt
   libavutil  56. 25.100 / 56. 25.100
   libavcodec 58. 43.100 / 58. 43.100
   libavformat58. 25.100 / 58. 25.100
   libavdevice58.  6.101 / 58.  6.101
   libavfilter 7. 47.100 /  7. 47.100
   libswscale  5.  4.100 /  5.  4.100
   libswresample   3.  4.100 /  3.  4.100
   libpostproc55.  4.100 / 55.  4.100
 [wav @ 016fe4d32940] Could not find codec parameters for stream 0
 (Audio: none (Og[0][0] / 0x674F), 44100 Hz, 1 channels, 112 kb/s): unknown
 codec
 Consider increasing the value for the 'analyzeduration' and 'probesize'
 options
 Guessed Channel Layout for Input Stream #0.0 : mono
 Input #0, wav, from '707 Crash.wav':
   Metadata:
 encoder : Edison
   Duration: 00:00:01.28, bitrate: 131 kb/s
 Stream #0:0: Audio: none (Og[0][0] / 0x674F), 44100 Hz, mono, 112 kb/s
 Stream mapping:
   Stream #0:0 -> #0:0 (? (?) -> pcm_s16le (native))
 Decoder (codec none) not found for input stream #0:0
 }}}

 {{{
 % ffprobe "707 Crash.wav"
 ffprobe version N-92944-g395e8a53fa Copyright (c) 2007-2019 the FFmpeg
 developers
   built with gcc 8.2.1 (GCC) 20181201
   configuration: --disable-static --enable-shared --enable-gpl --enable-
 version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv
 --enable-libass --enable-libbluray --enable-libfreetype --enable-
 libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-
 libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy
 --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx
 --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265
 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp
 --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-
 libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-
 libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va
 --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-
 libopenmpt
   libavutil  56. 25.100 / 56. 25.100
   libavcodec 58. 43.100 / 58. 43.100
   libavformat58. 25.100 / 58. 25.100
   libavdevice58.  6.101 / 58.  6.101
   libavfilter 7. 47.100 /  7. 47.100
   libswscale  5.  4.100 /  5.  4.100
   libswresample   3.  4.100 /  3.  4.100
   libpostproc55.  4.100 / 55.  4.100
 [wav @ 01d325cf5e00] Could not find codec parameters for stream 0
 (Audio: none (Og[0][0] / 0x674F), 44100 Hz, 1 channels, 112 kb/s): unknown
 codec
 Consider increasing the value for the 'analyzeduration' and 'probesize'
 options
 Input #0, wav, from '707 Crash.wav':
   Metadata:
 encoder : Edison
   Duration: 00:00:01.28, bitrate: 131 kb/s
 Stream #0:0: Audio: none (Og[0][0] / 0x674F), 44100 Hz, 1 channels,
 112 kb/s
 Unsupported codec with id 0 for input stream 0
 }}}

 {{{
 ffplay "707 Crash.wav"
 ffplay version N-92944-g395e8a53fa Copyright (c) 2003-2019 the FFmpeg
 developers
   built with gcc 8.2.1 (GCC) 20181201
   configuration: --disable-static --enable-shared --enable-gpl --enable-
 version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv
 --enable-libass --enable-libbluray --enable-libfreetype --enable-
 libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-
 

Re: [FFmpeg-trac] #7369(avformat:new): dash livestream cannot be read without -re

2019-01-11 Thread FFmpeg
#7369: dash livestream cannot be read without -re
+
 Reporter:  cehoyos |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:
 Keywords:  dash|   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by cehoyos):

 Replying to [comment:14 stevenliu]:
 > Replying to [comment:13 cehoyos]:
 > > With the patch attached, FFplay:
 > > * Takes very long to start
 > > * Shows no timing information on the console
 > > * Heats one cpu
 > > So I suspect this is not the right approach.
 >
 > https://patchwork.ffmpeg.org/patch/11702/

 Playback with ffplay is broken / choppy with this patch.

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


Re: [FFmpeg-trac] #7663(avcodec:open): ffmpeg-qsv: it will overflow when set maxrate more than 65535 Kbps

2019-01-11 Thread FFmpeg
#7663: ffmpeg-qsv: it will overflow when set maxrate more than 65535 Kbps
-+---
 Reporter:  wangzj0601   |Owner:
 Type:  defect   |   Status:  open
 Priority:  minor|Component:  avcodec
  Version:  unspecified  |   Resolution:
 Keywords:  qsv  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by lizhong1008):

 https://patchwork.ffmpeg.org/patch/11707/ has been sent to fix this 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] #7669(avformat:new): avformat/mov.c : constant increase of memory usage when demuxing live fmp4

2019-01-11 Thread FFmpeg
#7669: avformat/mov.c : constant increase of memory usage when demuxing live 
fmp4
+
 Reporter:  Natus   |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  avformat
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  1
Analyzed by developer:  0   |
+
Changes (by Natus):

 * version:  unspecified => git-master
 * component:  undetermined => avformat
 * reproduced:  0 => 1


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


[FFmpeg-trac] #7669(undetermined:new): avformat/mov.c : constant increase of memory usage when demuxing live fmp4

2019-01-11 Thread FFmpeg
#7669: avformat/mov.c : constant increase of memory usage when demuxing live 
fmp4
-+-
 Reporter:  Natus| Type:  defect
   Status:  new  | Priority:  normal
Component:   |  Version:
  undetermined   |  unspecified
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 When demuxing live fmp4, indexing of all fragments is done.
 It causes an infinite linearly increase in memory.
 For live streamn, those index are useless.
 We should have an option to skip the indexing as already implemented for
 fmp5 demuxer : https://patchwork.libav.org/patch/61014/

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