[FFmpeg-trac] #7209(undetermined:new): Build error with clang5 on Mac

2018-05-14 Thread FFmpeg
#7209: Build error with clang5 on Mac
-+-
 Reporter:  ponpon   | Type:  defect
   Status:  new  | Priority:  normal
Component:   |  Version:
  undetermined   |  unspecified
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 A build error appears since commit
 293a6e83325a7379c13469193492fa4cb2488785
 {{{
 CC  libavformat/mp3enc.o
 CC  libavformat/mpc.o
 CC  libavformat/mpc8.o
 CC  libavformat/mpeg.o
 CC  libavformat/mpegenc.o
 CC  libavformat/mpegts.o
 CC  libavformat/mpegtsenc.o
 CC  libavformat/mpegvideodec.o
 CC  libavformat/mpjpeg.o
 CC  libavformat/mpjpegdec.o
 CC  libavformat/mpl2dec.o
 CC  libavformat/mpsubdec.o
 CC  libavformat/msf.o
 CC  libavformat/msnwc_tcp.o
 CC  libavformat/mtaf.o
 CC  libavformat/mtv.o
 CC  libavformat/musx.o
 CC  libavformat/mux.o
 CC  libavformat/mvdec.o
 CC  libavformat/mvi.o
 CC  libavformat/mxf.o
 CC  libavformat/mxfdec.o
 CC  libavformat/mxfenc.o
 CC  libavformat/mxg.o
 CC  libavformat/ncdec.o
 libavformat/mxfenc.c:1145:36: error: too many arguments provided to
 function-like macro invocation
 memcpy(ul,
 (UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x01,0x04,0x01,0x01,0x01,0x01,0x...
^
 /usr/include/secure/_string.h:64:9: note: macro 'memcpy' defined here
 #define memcpy(dest, src, len)  \
 ^
 libavformat/mxfenc.c:1145:9: note: parentheses are required around macro
 argument containing braced
   initializer list
   ...memcpy(ul,
 
(UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x01,0x04,0x01,0x01,0x01,0x01,0x01,0x00,0x00},...
  ^
 (
 )
 libavformat/mxfenc.c:1149:36: error: too many arguments provided to
 function-like macro invocation
 memcpy(ul,
 (UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x01,0x04,0x01,0x01,0x01,0x01,0x...
^
 /usr/include/secure/_string.h:64:9: note: macro 'memcpy' defined here
 #define memcpy(dest, src, len)  \
 ^
 libavformat/mxfenc.c:1149:9: note: parentheses are required around macro
 argument containing braced
   initializer list
   ...memcpy(ul,
 
(UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x01,0x04,0x01,0x01,0x01,0x01,0x02,0x00,0x00},...
  ^
 (
 )
 libavformat/mxfenc.c:1152:36: error: too many arguments provided to
 function-like macro invocation
 memcpy(ul,
 (UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x01,0x04,0x01,0x01,0x01,0x01,0x...
^
 /usr/include/secure/_string.h:64:9: note: macro 'memcpy' defined here
 #define memcpy(dest, src, len)  \
 ^
 libavformat/mxfenc.c:1152:9: note: parentheses are required around macro
 argument containing braced
   initializer list
   ...memcpy(ul,
 
(UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x01,0x04,0x01,0x01,0x01,0x01,0x03,0x00,0x00},...
  ^
 (
 )
 libavformat/mxfenc.c:1155:36: error: too many arguments provided to
 function-like macro invocation
 memcpy(ul,
 (UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x06,0x04,0x01,0x01,0x01,0x01,0x...
^
 /usr/include/secure/_string.h:64:9: note: macro 'memcpy' defined here
 #define memcpy(dest, src, len)  \
 ^
 libavformat/mxfenc.c:1155:9: note: parentheses are required around macro
 argument containing braced
   initializer list
   ...memcpy(ul,
 
(UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x06,0x04,0x01,0x01,0x01,0x01,0x05,0x00,0x00},...
  ^
 (
 )
 libavformat/mxfenc.c:1158:36: error: too many arguments provided to
 function-like macro invocation
 memcpy(ul,
 (UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x06,0x04,0x01,0x01,0x01,0x01,0x...
^
 /usr/include/secure/_string.h:64:9: note: macro 'memcpy' defined here
 #define memcpy(dest, src, len)  \
 ^
 libavformat/mxfenc.c:1158:9: note: parentheses are required around macro
 argument containing braced
   initializer list
   ...memcpy(ul,
 
(UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x06,0x04,0x01,0x01,0x01,0x01,0x06,0x00,0x00},...
  ^
 (
 )
 libavformat/mxfenc.c:1161:36: error: too many arguments provided to
 function-like macro invocation
 memcpy(ul,
 (UID){0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x08,0x04,0x01,0x01,0x01,0x01,0x...
^
 /usr/include/secure/_string.h:64:9: note: macro 

Re: [FFmpeg-trac] #7163(avcodec:reopened): 12-bit ProRes not supported

2018-05-14 Thread FFmpeg
#7163: 12-bit ProRes not supported
-+-
 Reporter:   |Owner:
  spookybathtub  |   Status:  reopened
 Type:  enhancement  |Component:  avcodec
 Priority:  wish |   Resolution:
  Version:  unspecified  |   Blocked By:
 Keywords:  prores   |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by spookybathtub):

 Apparently it's impossible to detect the bit depth of a !ProRes file, so
 we should have a command-line option to switch between 10 and 12.  It
 would make sense to default to 10 for 4:2:2 sources and 12 for 4:4:4
 sources, since that is how these formats are commonly used.

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


Re: [FFmpeg-trac] #7200(avcodec:closed): Assertion failure with h264_metadata bsf

2018-05-14 Thread FFmpeg
#7200: Assertion failure with h264_metadata bsf
-+-
 Reporter:  mypopy   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  crash abort  |   Blocked By:
  regression |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by jkqxz):

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


Comment:

 Fixed by 9a09f4c54ab829811c2dd041cfb7196000590b78 (NAL units with no
 content are now dropped during parsing, so they no longer reach the CBS
 layer).

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


Re: [FFmpeg-trac] #7204(avcodec:closed): Integration of Turing Codec (HEVC encoder)

2018-05-14 Thread FFmpeg
#7204: Integration of Turing Codec (HEVC encoder)
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by jkqxz):

 H.265 encoders currently available in ffmpeg:
 * x265 (software via libx265)
 * Kvazaar (software via libkvazaar)
 * Intel (software and hardware encoders via libmfx, or hardware-only via
 VAAPI)
 * AMD (hardware via AMF or VAAPI)
 * Nvidia (hardware via NVENC)

 I think Turing would probably be accepted if there were any particular
 argument to do so, but currently it just looks like a closed research
 project:
 * It's pretty much stated that the API isn't stable, hence the suggested
 patch avoiding any common options and using the string argument stuff to
 push any incompatibility onto users.
 * The open-source project looks like an unsupported wall-throw - e.g.
 
.
 * There was little attempt to show that it's actually good for anything -
 no visible users, no useful benchmarks.

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


Re: [FFmpeg-trac] #7205(avcodec:closed): Rename HEVC to h265

2018-05-14 Thread FFmpeg
#7205: Rename HEVC to h265
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by jamrial):

 Such a change would require renaming user facing modules like decoders,
 encoders, bitstream filters and so on.

 Too much of a hassle for questionable gains.

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


Re: [FFmpeg-trac] #7205(avcodec:closed): Rename HEVC to h265

2018-05-14 Thread FFmpeg
#7205: Rename HEVC to h265
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by jkqxz):

 While I agree that the ITU name should have been used to be consistent,
 this is probably too painful to change now.  The hevc name appears in many
 different places, and all would need to be deprecated with support for
 both names over an extended period - it just isn't worth the trouble.
 (Also, I think it is quite likely that some people would disagree with the
 change - in some contexts the HEVC name has significantly more recognition
 than H.265, sufficiently so that changing it could cause a lot of
 confusion to users.)

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


Re: [FFmpeg-trac] #7208(undetermined:new): Input channel layout '5 channels (FL+FR+FC+LFE+BL)' is not supported

2018-05-14 Thread FFmpeg
#7208: Input channel layout '5 channels (FL+FR+FC+LFE+BL)' is not supported
-+-
 Reporter:  ralambda |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:
  Version:  git-master   |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:  audio mapping, auto_resampler, 5.1 =>
 * priority:  normal => wish
 * component:  ffmpeg => undetermined
 * type:  defect => enhancement


Comment:

 Please provide the input sample and please explain how it was created.

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


[FFmpeg-trac] #7208(ffmpeg:new): Input channel layout '5 channels (FL+FR+FC+LFE+BL)' is not supported

2018-05-14 Thread FFmpeg
#7208: Input channel layout '5 channels (FL+FR+FC+LFE+BL)' is not supported
-+-
 Reporter:  ralambda | Type:  defect
   Status:  new  | Priority:  normal
Component:  ffmpeg   |  Version:  git-
 Keywords:  audio|  master
  mapping, auto_resampler, 5.1   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 '''Summary of the bug'''
 When using input sources with 1 video stream and 1 audio stream that
 contains 5 channels, within a MOV container; FFmpeg assumes the audio
 stream has a 5.1 surround channel layout in the following pattern:
 "FL+FR+FC+LFE+BL".

 This is not a valid 5.1 layout - it is missing channel "BR".

 But in reality it is not a 5.1 layout at all. It's just 5 mono channels
 contained within 1 audio stream.

 '''How to reproduce'''

 {{{
 ffmpeg -i {input}.mov {output}.mp4
 }}}


 '''Input must contain'''
 - mov container
 - video stream
 - video track
 - audio stream
 - audio track (channel 1)
 - audio track (channel 2)
 - audio track (channel 3)
 - audio track (channel 4)
 - audio track (channel 5)

 '''Command and Error'''
 {{{
 ffmpeg -i {input}.mov {output}.mp4

 ffmpeg version N-90584-g37d472a906 Copyright (c) 2000-2018 the FFmpeg
 developers
   built with Apple LLVM version 9.0.0 (clang-900.0.39.2)
   configuration: --prefix=/usr/local --enable-gpl --enable-nonfree
 --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-
 libmp3lame --enable-libtheora --enable-libvorbis --enable-libvpx --enable-
 libx264 --enable-libx265 --enable-libopus --enable-libxvid --samples=fate-
 suite/
   libavutil  56. 12.100 / 56. 12.100
   libavcodec 58. 17.100 / 58. 17.100
   libavformat58. 10.100 / 58. 10.100
   libavdevice58.  2.100 / 58.  2.100
   libavfilter 7. 14.100 /  7. 14.100
   libswscale  5.  0.102 /  5.  0.102
   libswresample   3.  0.101 /  3.  0.101
   libpostproc55.  0.100 / 55.  0.100
 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '{input}':
   Metadata:
 major_brand : qt
 minor_version   : 0
 compatible_brands: qt
 creation_time   : 2018-05-06T21:06:23.00Z
   Duration: 00:00:01.17, start: 0.00, bitrate: 191677 kb/s
 Stream #0:0(und): Video: prores (apch / 0x68637061),
 yuv422p10le(bt709, progressive), 1920x1080, 187821 kb/s, SAR 1:1 DAR 16:9,
 23.98 fps, 23.98 tbr, 24k tbn, 24k tbc (default)
 Metadata:
   creation_time   : 2018-05-06T21:06:23.00Z
   handler_name: Core Media Data Handler
   encoder : Apple ProRes 422 HQ
   timecode: 04:12:44:07
 Stream #0:1(und): Audio: pcm_s16le (lpcm / 0x6D63706C), 48000 Hz, 5
 channels (FL+FR+FC+LFE+BL), s16, 3840 kb/s (default)
 Metadata:
   creation_time   : 2018-05-06T21:06:23.00Z
   handler_name: Core Media Data Handler
 Stream #0:2(und): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
 Metadata:
   creation_time   : 2018-05-06T21:06:23.00Z
   handler_name: Core Media Data Handler
   timecode: 04:12:44:07
 Stream mapping:
   Stream #0:0 -> #0:0 (prores (native) -> h264 (libx264))
   Stream #0:1 -> #0:1 (pcm_s16le (native) -> aac (native))
 Press [q] to stop, [?] for help
 [aac @ 0x7f9aaa025a00] Unsupported channel layout
 Error initializing output stream 0:1 -- Error while opening encoder for
 output stream #0:1 - maybe incorrect parameters such as bit_rate, rate,
 width or height
 Conversion failed!
 }}}


 '''Additional Errors'''

 {{{
 [auto_resampler_0 @ 0x7f7fab404c40] [SWR @ 0x7f7fae004800] Input channel
 layout '5 channels (FL+FR+FC+LFE+BL)' is not supported
 [auto_resampler_0 @ 0x7f7fab404c40] Failed to configure output pad on
 auto_resampler_0
 Error reinitializing filters!
 Failed to inject frame into filter network: Invalid argument
 Error while processing the decoded data for stream #0:1
 }}}

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


Re: [FFmpeg-trac] #7199(undetermined:new): Broken P010 colorspace conversion

2018-05-14 Thread FFmpeg
#7199: Broken P010 colorspace conversion
-+-
 Reporter:  thx4ever |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 cehoyos):

 I can only confirm that the roundtrip yuv420p -> P010 -> yuv420p works
 visually.

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


Re: [FFmpeg-trac] #7196(ffplay:reopened): ffplay crashes on seeking

2018-05-14 Thread FFmpeg
#7196: ffplay crashes on seeking
+
 Reporter:  aleks   |Owner:
 Type:  defect  |   Status:  reopened
 Priority:  normal  |Component:  ffplay
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by aleks):

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


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


Re: [FFmpeg-trac] #7196(ffplay:closed): ffplay crashes on seeking

2018-05-14 Thread FFmpeg
#7196: ffplay crashes on seeking
-+-
 Reporter:  aleks|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  ffplay
  Version:  git-master   |   Resolution:
 Keywords:   |  needs_more_info
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by aleks):

 Here is the output. Is ffplay supposed to create threads this often?

 Btw, does anybody has a version of ffplay that uses sdl1 or directdraw?
 Because sdl2 version doesn't work on one of my computers, no 3d
 acceleration there.

 {{{
 $ gdb --args ffplay_g sm19342901.mp4
 GNU gdb (GDB) 7.11.1
 Copyright (C) 2016 Free Software Foundation, Inc.
 License GPLv3+: GNU GPL version 3 or later
 
 This is free software: you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
 and "show warranty" for details.
 This GDB was configured as "i686-pc-msys".
 Type "show configuration" for configuration details.
 For bug reporting instructions, please see:
 .
 Find the GDB manual and other documentation resources online at:
 .
 For help, type "help".
 Type "apropos word" to search for commands related to "word"...
 Traceback (most recent call last):
   File "", line 3, in 
 ImportError: No module named libstdcxx.v6.printers
 /etc/gdbinit:6: Error in sourced command file:
 Error while executing Python code.
 Reading symbols from ffplay_g...done.
 (gdb) r
 Starting program: /c/_src/ffmpeg_src/__new/FFmpeg/build3-release/ffplay_g
 sm1934
 2901.mp4
 [New Thread 4172.0x1740]
 [New Thread 4172.0xf68]
 [New Thread 4172.0x1714]
 [New Thread 4172.0x70c]
 ffplay version 3.4.git Copyright (c) 2003-2018 the FFmpeg developers
   built with gcc 7.3.0 (GCC)
   configuration: --enable-shared --enable-gpl --enable-version3 --enable-
 nonfree
 --disable-doc
   libavutil  56. 18.100 / 56. 18.100
   libavcodec 58. 19.101 / 58. 19.101
   libavformat58. 13.102 / 58. 13.102
   libavdevice58.  4.100 / 58.  4.100
   libavfilter 7. 21.100 /  7. 21.100
   libswscale  5.  2.100 /  5.  2.100
   libswresample   3.  2.100 /  3.  2.100
   libpostproc55.  2.100 / 55.  2.100
 [New Thread 4172.0x10e0]
 warning: Dll Loaded :-)
 [New Thread 4172.0x11d8]
 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'sm19342901.mp4':0B f=0/0
   Metadata:
 major_brand : isom
 minor_version   : 1
 compatible_brands: isom
 creation_time   : 2012-11-11T14:58:41.00Z
 copyright   :
 copyright-eng   :
   Duration: 00:02:05.81, start: 0.00, bitrate: 1330 kb/s
 Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv,
 smpte1
 70m/unknown/unknown), 864x486, 1199 kb/s, 30 fps, 30 tbr, 30 tbn, 60 tbc
 (defaul   t)
 Metadata:
   creation_time   : 2012-11-12T08:23:33.00Z
   handler_name: Video
 Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz,
 stereo, flt
 p, 127 kb/s (default)
 Metadata:
   creation_time   : 2012-11-11T14:58:41.00Z
   handler_name: GPAC ISO Audio Handler
 [New Thread 4172.0xb70]
 [New Thread 4172.0x176c]
 [New Thread 4172.0x850]
 [New Thread 4172.0x13f8]
 [New Thread 4172.0xea8]
 [New Thread 4172.0x11c0]
 [New Thread 4172.0x1460]
 [New Thread 4172.0x144]
 [New Thread 4172.0x17a0]
 [New Thread 4172.0xabc]
 [New Thread 4172.0x16fc]
 [New Thread 4172.0xffc]
 [New Thread 4172.0x188]
 [New Thread 4172.0x1610]
 [New Thread 4172.0x14b4]
 [New Thread 4172.0x1004]
 [Thread 4172.0x176c exited with code 0]vq=   20KB sq=0B f=0/0
 [Thread 4172.0x13f8 exited with code 0]
 [Thread 4172.0xb70 exited with code 0]
 [Thread 4172.0x850 exited with code 0]
 [New Thread 4172.0x13b0]  0 aq=   20KB vq=  206KB sq=0B f=0/0
 [New Thread 4172.0x1524]
 [New Thread 4172.0xee0]
 [New Thread 4172.0xbf8]
 [New Thread 4172.0x840]   0 aq=   20KB vq=  199KB sq=0B f=0/0
 [New Thread 4172.0x16bc]
 [New Thread 4172.0xa74]
 [New Thread 4172.0x1188]
 [New Thread 4172.0x1568]
 [New Thread 4172.0x16b8]
 Seek to 33% ( 0:00:40) of total duration ( 0:02:05)   B f=0/0
 [Thread 4172.0x1524 exited with code 0]vq=  159KB sq=0B f=0/0
 [Thread 4172.0xbf8 exited with code 0]
 [Thread 4172.0x16bc exited with code 0]
 [Thread 4172.0x1188 exited with code 0]
 [Thread 4172.0xee0 exited with code 0]
 [New Thread 4172.0x278]
 [New Thread 4172.0x8c4]
 [Thread 4172.0xa74 exited with code 0] vq=  156KB sq=0B f=0/0
 [Thread 4172.0x840 exited with code 0]
 [New Thread 

Re: [FFmpeg-trac] #7205(avcodec:closed): Rename HEVC to h265

2018-05-14 Thread FFmpeg
#7205: Rename HEVC to h265
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by fantesy):

 Replying to [comment:1 richardpl]:
 > Not going to happen.

 Sorry but can you explain why 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] #7203(undetermined:closed): Problem with encoding type "Cyrillic (DOS)" with metadata delivery.

2018-05-14 Thread FFmpeg
#7203: Problem with encoding type "Cyrillic (DOS)" with metadata delivery.
-+-
 Reporter:  max79|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  id3v2|   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by llogan):

 Replying to [comment:5 mkver]:
 > I am not an FFmpeg developer, but just an interested visitor to this
 board. I don't know whether I am allowed to close tickets and therefore I
 leave it to the real guys in charge.

 Please go ahead and close tickets if you think they should be closed, and
 provide an explanation why it should be closed (like you did in
 comment:3). If someone disagrees they can always add a comment and/or re-
 open 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] #7206(avcodec:closed): Remove extra nvenc IDs

2018-05-14 Thread FFmpeg
#7206: Remove extra nvenc IDs
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  invalid
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Changes (by fantesy):

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


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


Re: [FFmpeg-trac] #7206(avcodec:new): Remove extra nvenc IDs

2018-05-14 Thread FFmpeg
#7206: Remove extra nvenc IDs
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by fantesy):

 ok sorry for bothering 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] #7204(avcodec:closed): Integration of Turing Codec (HEVC encoder)

2018-05-14 Thread FFmpeg
#7204: Integration of Turing Codec (HEVC encoder)
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Changes (by fantesy):

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


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


Re: [FFmpeg-trac] #7204(avcodec:new): Integration of Turing Codec (HEVC encoder)

2018-05-14 Thread FFmpeg
#7204: Integration of Turing Codec (HEVC encoder)
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by fantesy):

 ok, my apologies I didn't know that it had already been submitted and
 rejected. I wasn't suggesting it based on performance or capabilities,
 more of giving people a different option and it was the only other HEVC
 encoder I was aware of. However if you have your reasons for not including
 it, I can accept that and I will close this ticket.

 And again i would like to apologies, I wasn't aware that they had been
 bugging you guys about integrating it, I don't keep as up to date on the
 mailing list as I would 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] #5874(avcodec:open): tiff LZW compression does not compress enough

2018-05-14 Thread FFmpeg
#5874: tiff LZW compression does not compress enough
-+---
 Reporter:  jsteinkamp   |Owner:
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  tif  |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+---
Changes (by jamrial):

 * priority:  normal => wish
 * type:  defect => enhancement


Comment:

 tiffcp from the libtiff package compresses it even more, from ~716k to
 ~691k. In contrast the output generated by libavcodec is ~884k.

 Our lzw encoder is apparently inefficient, so changing this to an
 enhancement request.

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


Re: [FFmpeg-trac] #2179(avformat:closed): Please add HTTP referer support

2018-05-14 Thread FFmpeg
#2179: Please add HTTP referer support
-+
 Reporter:  gjdfgh   |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:  fixed
 Keywords:  http |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+
Changes (by cehoyos):

 * status:  new => 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] #7202(undetermined:closed): mjpeg compression creates laggy video

2018-05-14 Thread FFmpeg
#7202: mjpeg compression creates laggy video
-+-
 Reporter:  jsteinkamp   |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
-+-

Comment (by cehoyos):

 Replying to [comment:5 jsteinkamp]:
 > {{{
 > set input=tiffs\hibiscus1.%%04d.tif -pix_fmt yuvj444p
 > set codec=-vcodec mjpeg -q:v 8 -f mov
 > ffmpeg -y -framerate 30 -i %input% -frames 200 -vf "setsar=1" %codec%
 hibiscus1_ffmpeg_mjpeg.mov
 > }}}
 For future tickets: Please remember not to use variables in the command
 line, and remove unneeded parts of the command line like in this case
 `setsar=1` for input with `SAR 1:1`-

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


Re: [FFmpeg-trac] #7202(undetermined:closed): mjpeg compression creates laggy video

2018-05-14 Thread FFmpeg
#7202: mjpeg compression creates laggy video
-+-
 Reporter:  jsteinkamp   |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
-+-

Comment (by cehoyos):

 Could you point me to one of those mentions?

 Which players - except for Quicktime - have issues with the sample you
 provided?

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


Re: [FFmpeg-trac] #7196(ffplay:closed): ffplay crashes on seeking

2018-05-14 Thread FFmpeg
#7196: ffplay crashes on seeking
-+-
 Reporter:  aleks|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  ffplay
  Version:  git-master   |   Resolution:
 Keywords:   |  needs_more_info
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

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


Comment:

 Please reopen this ticket if you can provide backtrace, disassembly and
 register dump as requested on https://ffmpeg.org/bugreports.html

 Since you claim the issue is not reproducible with binaries that are - to
 the best of my knowledge - build from sources from git.ffmpeg.org there is
 no reason to assume the issue you see can be fixed in FFmpeg. The Zeranoe
 forum is the right place to discuss Windows compilation issues.

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


Re: [FFmpeg-trac] #7202(undetermined:closed): mjpeg compression creates laggy video

2018-05-14 Thread FFmpeg
#7202: mjpeg compression creates laggy video
-+-
 Reporter:  jsteinkamp   |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
-+-

Comment (by jsteinkamp):

 HI The issue is this, when you make a mjpg movie it does not play very
 well, especially in quicktime. But I have also noticed this in other
 players. If you search the internet you will see many mentions of ffmpeg
 not working well with mjpg. Aftereffects mjpeg movies with the same
 compression work great. The issue becomes very obvious with larger
 resolution movies.

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


Re: [FFmpeg-trac] #7204(avcodec:new): Integration of Turing Codec (HEVC encoder)

2018-05-14 Thread FFmpeg
#7204: Integration of Turing Codec (HEVC encoder)
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by cehoyos):

 Replying to [ticket:7204 fantesy]:
 > At the moment the only software HEVC encoder ffmpeg uses is libx265, and
 i don't know if you want to keep it that way, but in 2016 the BBC Research
 and Development institute release their "Turing Codec" which is a HEVC
 encoder licensed under the GPL v2. Would it be possible to add integration
 to ffmpeg?
 Why do you believe this would be a good idea?
 (Your answer may be able to invalidate the reasons for not accepting the
 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] #7203(undetermined:closed): Problem with encoding type "Cyrillic (DOS)" with metadata delivery.

2018-05-14 Thread FFmpeg
#7203: Problem with encoding type "Cyrillic (DOS)" with metadata delivery.
-+-
 Reporter:  max79|Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  id3v2|   Resolution:  invalid
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

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


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


Re: [FFmpeg-trac] #7202(undetermined:closed): mjpeg compression creates laggy video

2018-05-14 Thread FFmpeg
#7202: mjpeg compression creates laggy video
-+-
 Reporter:  jsteinkamp   |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 cehoyos):

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


Comment:

 Replying to [comment:5 jsteinkamp]:
 > Please don't close, changing the rgba to yuvj444p makes no difference.

 Of course not (it's the chosen pix_fmt anyway), but that is not the
 pix_fmt of the sample video you said is ok.

 Note that you still failed to explain the actual 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] #7202(undetermined:reopened): mjpeg compression creates laggy video

2018-05-14 Thread FFmpeg
#7202: mjpeg compression creates laggy video
-+-
 Reporter:  jsteinkamp   |Owner:
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by jsteinkamp):

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


Comment:

 Please don't close, changing the rgba to yuvj444p makes no difference.

 set input=tiffs\hibiscus1.%%04d.tif -pix_fmt yuvj444p
 set codec=-vcodec mjpeg -q:v 8 -f mov
 ffmpeg -y -framerate 30 -i %input% -frames 200 -vf "setsar=1" %codec%
 hibiscus1_ffmpeg_mjpeg.mov



 ffmpeg version N-91024-g293a6e8332 Copyright (c) 2000-2018 the FFmpeg
 developers

   built with gcc 7.3.0 (GCC)
   configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-
 bzlib --e
 nable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-
 libblur
 ay --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb
 --enable-
 libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine
 --enab
 le-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame
 --enable-li
 bvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-
 libx265 --en
 able-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp
 --enable-
 libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa
 --enabl
 e-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf
 --enabl
 e-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec
 --enab
 le-dxva2 --enable-avisynth
   libavutil  56. 18.100 / 56. 18.100
   libavcodec 58. 19.101 / 58. 19.101
   libavformat58. 13.102 / 58. 13.102
   libavdevice58.  4.100 / 58.  4.100
   libavfilter 7. 21.100 /  7. 21.100
   libswscale  5.  2.100 /  5.  2.100
   libswresample   3.  2.100 /  3.  2.100
   libpostproc55.  2.100 / 55.  2.100
 Input #0, image2, from 'tiffs\hibiscus1.%04d.tif':
   Duration: 00:00:06.67, start: 0.00, bitrate: N/A
 Stream #0:0: Video: tiff, rgba, 1024x768 [SAR 1:1 DAR 4:3], 30 fps, 30
 tbr,
 30 tbn, 30 tbc
 Stream mapping:
   Stream #0:0 -> #0:0 (tiff (native) -> mjpeg (native))
 Press [q] to stop, [?] for help
 [swscaler @ 0291c000] deprecated pixel format used, make sure you
 did se
 t range correctly
 Output #0, mov, to 'hibiscus1_ffmpeg_mjpeg.mov':
   Metadata:
 encoder : Lavf58.13.102
 Stream #0:0: Video: mjpeg (jpeg / 0x6765706A), yuvj444p(pc), 1024x768
 [SAR 1
 :1 DAR 4:3], q=2-31, 200 kb/s, 30 fps, 15360 tbn, 30 tbc
 Metadata:
   encoder : Lavc58.19.101 mjpeg
 Side data:
   cpb: bitrate max/min/avg: 0/0/20 buffer size: 0 vbv_delay: -1
 frame=   75 fps=0.0 q=8.0 size=4096kB time=00:00:02.40
 bitrate=13980.8kbits/
 frame=  159 fps=158 q=8.0 size=8960kB time=00:00:05.20
 bitrate=14115.3kbits/
 frame=  200 fps=160 q=8.0 Lsize=   11530kB time=00:00:06.63
 bitrate=14238.8kbits
 /s speed=5.31x
 video:11528kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB
 muxing
  overhead: 0.014147%

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


Re: [FFmpeg-trac] #7207(avformat:new): FFmpeg segmented output does not work

2018-05-14 Thread FFmpeg
#7207: FFmpeg segmented output does not work
-+-
 Reporter:  monakov  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  mpegts h264  |   Blocked By:
  dts|  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * keywords:  segment pts av_read_frame => mpegts h264 dts
 * 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


Re: [FFmpeg-trac] #5874(avcodec:open): tiff LZW compression does not compress enough

2018-05-14 Thread FFmpeg
#5874: tiff LZW compression does not compress enough
+---
 Reporter:  jsteinkamp  |Owner:
 Type:  defect  |   Status:  open
 Priority:  normal  |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  tif |   Blocked By:
 Blocking:  |  Reproduced by developer:  1
Analyzed by developer:  0   |
+---

Comment (by jsteinkamp):

 Hi I made you a photoshop LZW compressed image at:
 http://jsteinkamp.com/saved_photoshop.zip

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


Re: [FFmpeg-trac] #7202(undetermined:closed): mjpeg compression creates laggy video

2018-05-14 Thread FFmpeg
#7202: mjpeg compression creates laggy video
-+-
 Reporter:  jsteinkamp   |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 cehoyos):

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


Comment:

 Replying to [ticket:7202 jsteinkamp]:
 > {{{
 > Incompatible pixel format 'rgba' for codec 'mjpeg', auto-selecting
 format 'yuvj444p'
 > }}}
 I can only guess that you missed this line.

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


Re: [FFmpeg-trac] #5930(avformat:closed): Nut container doesnʼt support Opus codec

2018-05-14 Thread FFmpeg
#5930: Nut container doesnʼt support Opus codec
-+
 Reporter:  Nekit|Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:  fixed
 Keywords:  nut opus |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by cehoyos):

 Fixed in 744916908167951c8d3590bc8efeac0ffe35c1ee

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


Re: [FFmpeg-trac] #5097(undetermined:new): XDCAM HD422

2018-05-14 Thread FFmpeg
#5097: XDCAM HD422
-+-
 Reporter:   |Owner:
  AxelTechnology |   Status:  new
 Type:  defect   |Component:
 Priority:  normal   |  undetermined
  Version:  unspecified  |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by cehoyos):

 Replying to [comment:10 AxelTechnology]:
 > In the past, we patched the mxfenc file and it worked in SONY Browser.
 Too bad you didn't tell us when I asked in comment:3...

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


Re: [FFmpeg-trac] #5874(avcodec:open): tiff LZW compression does not compress enough

2018-05-14 Thread FFmpeg
#5874: tiff LZW compression does not compress enough
+---
 Reporter:  jsteinkamp  |Owner:
 Type:  defect  |   Status:  open
 Priority:  normal  |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  tif |   Blocked By:
 Blocking:  |  Reproduced by developer:  1
Analyzed by developer:  0   |
+---

Comment (by cehoyos):

 Replying to [comment:5 jsteinkamp]:

 > The LZW compression for TIFF is still larger than photoshop.
 > photoshop file 716 KB

 Where can I find this 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] #7207(avformat:new): FFmpeg segmented output does not work

2018-05-14 Thread FFmpeg
#7207: FFmpeg segmented output does not work
-+-
 Reporter:  monakov  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avformat
  Version:  unspecified  |   Resolution:
 Keywords:  segment pts  |   Blocked By:
  av_read_frame  |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by monakov):

 Test command line (added -re option for confidence):
 {{{
 % ffmpeg -re -i http://bitmovin-a.akamaihd.net/content/playhouse-
 vr/m3u8s/105560_video_1920_900.m3u8 -c copy -f segment -segment_time
 10 part%03d.mp4
 }}}

 Complete ffmpeg output:
 {{{
 ffmpeg version N-91076-g10ed9f2 Copyright (c) 2000-2018 the FFmpeg
 developers
   built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.9) 20160609
   configuration:
   libavutil  56. 18.102 / 56. 18.102
   libavcodec 58. 19.101 / 58. 19.101
   libavformat58. 13.102 / 58. 13.102
   libavdevice58.  4.100 / 58.  4.100
   libavfilter 7. 22.100 /  7. 22.100
   libswscale  5.  2.100 /  5.  2.100
   libswresample   3.  2.100 /  3.  2.100
 [hls,applehttp @ 0x3acc4c0] Opening
 'http://bitmovin-a.akamaihd.net/content/playhouse-
 vr/video/1920_900/hls/segment_0.ts' for reading
 [hls,applehttp @ 0x3acc4c0] Opening
 'http://bitmovin-a.akamaihd.net/content/playhouse-
 vr/video/1920_900/hls/segment_1.ts' for reading
 [http @ 0x3ad71c0] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_2.ts' for reading
 Input #0, hls,applehttp, from 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/m3u8s/105560_video_1920_900.m3u8':
   Duration: 00:02:17.00, start: 0.066733, bitrate: 0 kb/s
   Program 0
 Metadata:
   variant_bitrate : 0
 Stream #0:0: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p,
 3840x1920 [SAR 1:1 DAR 2:1], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
 Metadata:
   variant_bitrate : 0
 [segment @ 0x3b87f80] Opening 'part000.mp4' for writing
 Output #0, segment, to 'part%03d.mp4':
   Metadata:
 encoder : Lavf58.13.102
 Stream #0:0: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p,
 3840x1920 [SAR 1:1 DAR 2:1], q=2-31, 29.97 fps, 29.97 tbr, 11988 tbn,
 29.97 tbc
 Metadata:
   variant_bitrate : 0
 Stream mapping:
   Stream #0:0 -> #0:0 (copy)
 Press [q] to stop, [?] for help
 [segment @ 0x3b87f80] Timestamps are unset in a packet for stream 0. This
 is deprecated and will stop working in the future. Fix your code to set
 the timestamps properly
 [mp4 @ 0x3b2bd40] Timestamps are unset in a packet for stream 0. This is
 deprecated and will stop working in the future. Fix your code to set the
 timestamps properly
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3af1a40] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_3.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3ad71c0] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_4.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3af1a40] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_5.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3ad71c0] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_6.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3af1a40] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_7.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3ad71c0] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_8.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no valueA time=00:00:27.89 bitrate=N/A speed=
 1x
 [http @ 0x3af1a40] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_9.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3ad71c0] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_10.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3af1a40] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_11.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3ad71c0] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_12.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3af1a40] Opening 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/video/1920_900/hls/segment_13.ts' for reading
 [mp4 @ 0x3b2bd40] pts has no value
 [http @ 0x3ad71c0] Opening 

Re: [FFmpeg-trac] #7203(undetermined:new): Problem with encoding type "Cyrillic (DOS)" with metadata delivery.

2018-05-14 Thread FFmpeg
#7203: Problem with encoding type "Cyrillic (DOS)" with metadata delivery.
-+-
 Reporter:  max79|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 mkver):

 I am not an FFmpeg developer, but just an interested visitor to this
 board. I don't know whether I am allowed to close tickets and therefore I
 leave it to the real guys in charge.

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


Re: [FFmpeg-trac] #7205(avcodec:closed): Rename HEVC to h265

2018-05-14 Thread FFmpeg
#7205: Rename HEVC to h265
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Changes (by richardpl):

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


Comment:

 Not going to happen.

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


Re: [FFmpeg-trac] #7207(avformat:new): FFmpeg segmented output does not work

2018-05-14 Thread FFmpeg
#7207: FFmpeg segmented output does not work
-+-
 Reporter:  monakov  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avformat
  Version:  unspecified  |   Resolution:
 Keywords:  segment pts  |   Blocked By:
  av_read_frame  |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by cehoyos):

 Please test current FFmpeg git head and provide the command line you
 tested together with the complete, uncut console output to make this a
 valid ticket.

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


Re: [FFmpeg-trac] #7204(avcodec:new): Integration of Turing Codec (HEVC encoder)

2018-05-14 Thread FFmpeg
#7204: Integration of Turing Codec (HEVC encoder)
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by Gyan):

 That encoder was submitted and rejected. See
 http://www.ffmpeg.org/pipermail/ffmpeg-devel/2017-December/222341.html

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


Re: [FFmpeg-trac] #7196(ffplay:reopened): ffplay crashes on seeking

2018-05-14 Thread FFmpeg
#7196: ffplay crashes on seeking
+
 Reporter:  aleks   |Owner:
 Type:  defect  |   Status:  reopened
 Priority:  normal  |Component:  ffplay
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+

Comment (by aleks):

 Just tell me what can I do with this stackdump file? It probably requires
 working in command line with gdb? I have some experience with codeblocks,
 can I use it somehow here? I mostly work with visual studio 2005 right
 now, I installed msys2 just to compile ffplay.

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


Re: [FFmpeg-trac] #7201(avformat:closed): using ffmpeg request http was considered downloading

2018-05-14 Thread FFmpeg
#7201: using ffmpeg request http was considered downloading
-+-
 Reporter:  yunhai2009   |Owner:
 Type:  sponsoring   |   Status:  closed
  request|Component:  avformat
 Priority:  normal   |   Resolution:  fixed
  Version:  3.2.4|   Blocked By:
 Keywords:  m3u8 |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by yunhai2009):

 * status:  new => 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] #7206(avcodec:new): Remove extra nvenc IDs

2018-05-14 Thread FFmpeg
#7206: Remove extra nvenc IDs
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

Comment (by heleppkes):

 The redundant names are already marked as deprecated and will be removed
 after the typical deprecation period.

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


Re: [FFmpeg-trac] #7203(undetermined:new): Problem with encoding type "Cyrillic (DOS)" with metadata delivery.

2018-05-14 Thread FFmpeg
#7203: Problem with encoding type "Cyrillic (DOS)" with metadata delivery.
-+-
 Reporter:  max79|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 max79):

 Thank you for clarification. But if it's not ffmpeg bug why you didn't
 close this ticket?

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


Re: [FFmpeg-trac] #7207(avformat:new): FFmpeg segmented output does not work

2018-05-14 Thread FFmpeg
#7207: FFmpeg segmented output does not work
-+-
 Reporter:  monakov  |Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avformat
  Version:  unspecified  |   Resolution:
 Keywords:  segment pts  |   Blocked By:
  av_read_frame  |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by monakov):

 * component:  undetermined => avformat


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


[FFmpeg-trac] #7207(undetermined:new): FFmpeg segmented output does not work

2018-05-14 Thread FFmpeg
#7207: FFmpeg segmented output does not work
-+-
 Reporter:  monakov  | Type:  defect
   Status:  new  | Priority:  normal
Component:   |  Version:
  undetermined   |  unspecified
 Keywords:  segment pts  |   Blocked By:
  av_read_frame  |  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
 Summary of the bug:

 Segment format outputs only single file.
 Ticket is filled after this thread in libav-user mailing list:
 http://ffmpeg.org/pipermail/libav-user/2018-May/011143.html

 The problem is somehow related to av_read_frame returning invalid PTS/DTS
 on every received key frame (see FFmpeg output).

 How to reproduce:
 {{{
 % ffmpeg -i http://bitmovin-a.akamaihd.net/content/playhouse-
 vr/m3u8s/105560_video_1920_900.m3u8 -c copy -f segment -segment_time
 10 part%03d.mp4
 }}}

 FFmpeg version:
 {{{
 ffmpeg version 4.0 Copyright (c) 2000-2018 the FFmpeg developers
 built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.9) 20160609
 configuration: --enable-pic --enable-shared --disable-static --disable-doc
 --disable-debug --disable-outdevs --enable-runtime-cpudetect
 }}}
 Same problem with older versions (3.3.2, 2.8.14).

 FFmpeg output:
 {{{
 [http @ 0xf75b00] No trailing CRLF found in HTTP header.
 Input #0, hls,applehttp, from 'http://bitmovin-a.akamaihd.net/content
 /playhouse-vr/m3u8s/105560_video_1920_900.m3u8':
   Duration: 00:02:17.00, start: 0.066733, bitrate: 0 kb/s
   Program 0
 Metadata:
   variant_bitrate : 0
 Stream #0:0: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p,
 3840x1920 [SAR 1:1 DAR 2:1], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
 [segment @ 0x107ee40] Codec for stream 0 does not use global headers but
 container format requires global headers
 [mp4 @ 0x1016900] Codec for stream 0 does not use global headers but
 container format requires global headers
 Output #0, segment, to 'part%03d.mp4':
   Metadata:
 encoder : Lavf56.40.101
 Stream #0:0: Video: h264 ([27][0][0][0] / 0x001B), yuv420p, 3840x1920
 [SAR 1:1 DAR 2:1], q=2-31, 29.97 fps, 29.97 tbr, 11988 tbn, 29.97 tbc
 Stream mapping:
   Stream #0:0 -> #0:0 (copy)
 Press [q] to stop, [?] for help
 [http @ 0x107fb80] No trailing CRLF found in HTTP header.
 [mp4 @ 0x1016900] pts has no value
 [http @ 0x10200c0] No trailing CRLF found in HTTP header.ate=N/A
 [mp4 @ 0x1016900] pts has no value
 [http @ 0x107fb80] No trailing CRLF found in HTTP header.ate=N/A
 [mp4 @ 0x1016900] pts has no value
 [http @ 0x107f9c0] No trailing CRLF found in HTTP header.ate=N/A
 [mp4 @ 0x1016900] pts has no value
 [http @ 0x107fb80] No trailing CRLF found in HTTP header.ate=N/A
 ...
 }}}

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


Re: [FFmpeg-trac] #7204(avcodec:new): Integration of Turing Codec (HEVC encoder) (was: Add Turing Codec (HEVC encoder))

2018-05-14 Thread FFmpeg
#7204: Integration of Turing Codec (HEVC encoder)
-+---
 Reporter:  fantesy  |Owner:
 Type:  enhancement  |   Status:  new
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---

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


[FFmpeg-trac] #7206(avcodec:new): Remove extra nvenc IDs

2018-05-14 Thread FFmpeg
#7206: Remove extra nvenc IDs
-+---
 Reporter:  fantesy  | Type:  enhancement
   Status:  new  | Priority:  wish
Component:  avcodec  |  Version:  git-master
 Keywords:  nvenc|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
 Currently h264 has 3 nvenc based encoders (h264_nvenc, nvenc  and
 nvenc_h264), "nvenc" and "nvenc_h264" should probably be removed to reduce
 confusion, leaving "h264_nvenc" which is consistent with the counterparts
 from amd and intel. If the three all provide unique functionality then one
 should be chosen as the default and the rest available through additional
 flags.

 The same thing is true about HEVC which has 2 nvenc based encoders
 (nvenc_hevc and hevc_nvenc), "nvenc_hevc" should be removed (again for
 consistency).

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


[FFmpeg-trac] #7205(avcodec:new): Rename HEVC to h265

2018-05-14 Thread FFmpeg
#7205: Rename HEVC to h265
-+---
 Reporter:  fantesy  | Type:  enhancement
   Status:  new  | Priority:  wish
Component:  avcodec  |  Version:  git-master
 Keywords:  HEVC |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
 At the moment ffmpeg uses HEVC as the generic name, however the rest of
 the mpeg codecs use the h26x format for consistency it would a good idea
 to rename HEVC to h265 ( the -codecs list uses HEVC so it should be
 renamed). Also if it is at all possible at the same time could you make
 ffmpeg recognize HEVC as h265 (and AVC as h264) as some people use those
 and that way people wouldn't need to rename any bash/batch scripts.

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