September 2012 - FFmpeg-trac - lists.ffmpeg.org

#712(FFmpeg:new): m2v: wrong duration
by FFmpeg 31 Jan '14

31 Jan '14

#712: m2v: wrong duration -------------------------------------+------------------------------------- Reporter: cbsrobot | Type: defect Status: new | Priority: normal Component: FFmpeg | Version: git- Keywords: mpeg2video | master m2v | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- When converting any file to a m2v and checking the resulting file, the duration is not correctly calculated. mplayer shows also wrong duration. Quicktime and Mediainfo show the correct duration. example: ffmpeg -i fate/aletrek-rle.mov -target pal-dvd -f mpeg2video -an aletrek- rle.m2v [...] Duration: 00:00:03.33 ffprobe aletrek-rle.m2v [...] Duration: 00:00:00.76 mediainfo aletrek-rle.m2v [...] Duration : 3s 400ms mplayer -vo null -ao null -frames 0 -identify aletrek-rle.m2v [...] ID_LENGTH=0.77 -- Ticket URL: <http://ffmpeg.org/trac/ffmpeg/ticket/712> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker

1 6

#1087(avcodec:new): support decoding the CineForm codec
by FFmpeg 29 Jan '14

29 Jan '14

#1087: support decoding the CineForm codec -------------------------------------+------------------------------------- Reporter: dericed | Type: Status: new | enhancement Component: avcodec | Priority: normal Keywords: CFHD, | Version: git- CineForm | master Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- I found that ffmpeg can't read CineForm CFHD files. There are some samples available here: http://samples.mplayerhq.hu/V-codecs/CFHD/ I may be able to provide more samples if needed. {{{ ffmpeg -y -i MT_BeartoothHighway_1min_Cineform.avi anything.mp4 ffmpeg version N-34835-g4a9f466 Copyright (c) 2000-2012 the FFmpeg developers built on Mar 4 2012 08:53:39 with gcc 4.2.1 (Apple Inc. build 5666) (dot 3) configuration: --prefix=/usr/local/Cellar/ffmpeg/HEAD --enable-shared --enable-gpl --enable-version3 --enable-nonfree --enable-hardcoded-tables --enable-libfreetype --cc=/usr/bin/gcc-4.2 --enable-libx264 --enable- libfaac --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libopencore-amrnb --enable- libopencore-amrwb --enable-libass libavutil 51. 41.100 / 51. 41.100 libavcodec 54. 7.100 / 54. 7.100 libavformat 54. 2.100 / 54. 2.100 libavdevice 53. 4.100 / 53. 4.100 libavfilter 2. 63.100 / 2. 63.100 libswscale 2. 1.100 / 2. 1.100 libswresample 0. 7.100 / 0. 7.100 libpostproc 52. 0.100 / 52. 0.100 [avi @ 0x7fb4c201ae00] decoding for stream 0 failed [avi @ 0x7fb4c201ae00] Could not find codec parameters (Video: none (CFHD / 0x44484643), 1280x720) Input #0, avi, from 'MT_BeartoothHighway_1min_Cineform.avi': Duration: 00:01:01.96, start: 0.000000, bitrate: 16472 kb/s Stream #0:0: Video: none (CFHD / 0x44484643), 1280x720, 29.97 fps, 29.97 tbr, 29.97 tbn, 29.97 tbc Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 2 channels, s16, 1536 kb/s Video pixel format is unknown, stream cannot be encoded }}} -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1087> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker

1 8

#1636(undetermined:new): FRAPS Video Color Space
by FFmpeg 29 Jan '14

29 Jan '14

#1636: FRAPS Video Color Space -------------------------------------+------------------------------------- Reporter: DJX | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: FRAPS color | Blocked By: space dark white washed out | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- The color space that ffmpeg uses on FRAPS videos seems to be wrong or mishandled. First, running ffplay on a video (color space detected as yuvj420p), the output looks washed out (too white). Second, when transcoding a video to H264 (which keeps the color space as yuvj420p) the output looks too dark. Forcing the color space to yuv420p, the output looks fine. Third, when transcoding a video to MPEG2 (which changes the colorspace to yuv420p), the output looks fine. Here is how ffmpeg detects the original file: {{{ ffmpeg -i "C:\Fraps\Movies\cod2sp_s 2012-08-12 13-39-04-15.avi" ffmpeg version N-43418-g633b90c Copyright (c) 2000-2012 the FFmpeg developers built on Aug 9 2012 23:56:26 with gcc 4.7.1 (GCC) configuration: --enable-gpl --enable-version3 --disable-pthreads --enable-runt ime-cpudetect --enable-avisynth --enable-bzlib --enable-frei0r --enable- libass - -enable-libcelt --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-l ibfreetype --enable-libgsm --enable-libmp3lame --enable-libnut --enable- libopenj peg --enable-librtmp --enable-libschroedinger --enable-libspeex --enable- libtheo ra --enable-libutvideo --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-li bvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --ena ble-zlib libavutil 51. 67.100 / 51. 67.100 libavcodec 54. 51.100 / 54. 51.100 libavformat 54. 22.104 / 54. 22.104 libavdevice 54. 2.100 / 54. 2.100 libavfilter 3. 7.100 / 3. 7.100 libswscale 2. 1.101 / 2. 1.101 libswresample 0. 15.100 / 0. 15.100 libpostproc 52. 0.100 / 52. 0.100 [avi @ 000000000217aa20] non-interleaved AVI Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, avi, from 'C:\Fraps\Movies\orig.avi': Duration: 00:07:26.85, start: 0.000000, bitrate: 530091 kb/s Stream #0:0: Video: fraps (FPS1 / 0x31535046), yuvj420p, 1920x1080, 60 tbr, 60 tbn, 60 tbc Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, stereo, s16 , 1536 kb/s At least one output file must be specified }}} Let me know what other info you need. Thanks. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1636> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker

1 24

#420(undetermined:new): Sound fragments after seeking
by FFmpeg 20 Jan '14

20 Jan '14

#420: Sound fragments after seeking --------------------------+-------------------------- Reporter: kaptnole | Type: defect Status: new | Priority: important Component: undetermined | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced: 1 Analyzed: 1 | --------------------------+-------------------------- While trying to use FFmpeg libs as a developer I found the following: When decoding sound from some compressed audio formats and doing a seek, the first decoded packet after seeking is buggy. I had this with some mp4 files with aac audio codec and some wmv files with wma audio codec. Looks like some leftovers from internal buffers - but I am using 'avcodec_flush_buffers'! That of course leads to nasty sound noise/clicks. See attached sourcecode. Basically it shows the first few bytes of the first decoded sound packet then seeks back and shows the first packets decoding again. If you use it with some wmv or mp4 file with sound you should see see effect that both outputs at 0 are different but should be equal. Just make sure the sound is not only silence at the first 10 packets. Or am I missing some other flush...whatever function here? I am developing under windows using the actual ffmpeg git version. Confirmed for 32 and 64 bit version, self compiled and downloaded autobuilds. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/420> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker

1 16

#353(build system:new): Failed compiling FFmpeg in OS X 10.6.8
by FFmpeg 16 Jan '14

16 Jan '14

#353: Failed compiling FFmpeg in OS X 10.6.8 --------------------------+--------------------- Reporter: joao | Type: defect Status: new | Priority: normal Component: build system | Version: 0.8 Keywords: compile | Blocked By: Blocking: | Reproduced: 0 Analyzed: 0 | --------------------------+--------------------- Hi guys, Over at the Homebrew project (OS X package manager) we're running into issues compiling and installing FFmpeg on OS X. You can see our ticket here: https://github.com/mxcl/homebrew/issues/6278 The compilation error is seen here: https://gist.github.com/1059859 Someone managed to make it fail a bit later by doing this: https://gist.github.com/1072836 Can you provide us any help in getting this to compile? Thanks. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/353> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker

1 16

#1567(build system:new): make install fails with relative path for prefix dir
by FFmpeg 16 Jan '14

16 Jan '14

#1567: make install fails with relative path for prefix dir -------------------------------------+------------------------------------- Reporter: | Type: defect MacGyverismo | Priority: normal Status: new | Version: Component: build | unspecified system | Blocked By: Keywords: relative | Reproduced by developer: 0 path configure | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: install fails because the working directory is changed twice in a single make-command. How to reproduce: {{{ download (latest) source run configure with relative path for --prefix. ie. --prefix=install result: INSTALL libavdevice/libavdevice.so STRIP install-libavdevice-shared cd: 1: can't cd to install/lib }}} this seems to be because the command which is executed actually changes from working dir to install/lib ( which is good ) and then another cd command is executed ( also to install/lib ) but this fails because the working dir was already set to this directory. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1567> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker

1 2

#1010(undetermined:new): rtsp dump fails and yields non playable video (invalid droping)
by FFmpeg 15 Jan '14

15 Jan '14

#1010: rtsp dump fails and yields non playable video (invalid droping) -------------------------------------+------------------------------------- Reporter: lost1 | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: rtsp | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Hi, I'm using the following command line parameters to dump a live rtsp stream: {{{ ffmpeg -loglevel debug -i "rtsp://server.com/my_stream.sdp" -s 720x576 -vcodec copy -acodec copy -y output.mov }}} After a while the process stops with something like this: {{{ DTS 8975954, next:99748378 st:1 invalid droping [mov @ 0000000004FAF2C0] pts < dts in stream 0 av_interleaved_write_frame(): Invalid argument }}} I'm using Windows 7 x64. ffmpeg version N-37915-g6cb2085 -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1010> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker

1 3

#1452(undetermined:new): image2 to support %t
by FFmpeg 08 Jan '14

08 Jan '14

#1452: image2 to support %t -------------------------------------+------------------------------------- Reporter: burek | Type: Status: new | enhancement Component: | Priority: wish undetermined | Version: Keywords: | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Parameter %t in the output file name (just like %d) could be used to store the time stamp info of the current frame being written in the file. It could follow the same syntax like %d for formatting. It also might be used as an input parameter, but the list of matching input files would have to be sorted first, I guess, to have a correct sequence of input files. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1452> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker

1 4

#1535(undetermined:new): Unclear error message
by FFmpeg 03 Jan '14

03 Jan '14

#1535: Unclear error message -------------------------------------+------------------------------------- Reporter: burek | Type: Status: new | enhancement Component: | Priority: minor undetermined | Version: Keywords: | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- This FAQ item explains it the best: http://ffmpeg.org/faq.html #g_t_002dprofile-option-fails-when-encoding-H_002e264-video-with-AAC-audio It might be good to fix the error message to be a little bit more clear or descriptive. Simple "profile 'baseline' not recognized as a valid profile for AAC encoder, try using -profile:v instead" would be better since it would provide end users some clue what went wrong. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1535> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker

1 9

#1769(undetermined:new): Make ffmpeg build string available in avutil.h
by FFmpeg 02 Jan '14

02 Jan '14

#1769: Make ffmpeg build string available in avutil.h -------------------------------------+------------------------------------- Reporter: DonMoir | Type: Status: new | enhancement Component: | Priority: normal undetermined | Version: Keywords: | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Would be good if this was generally available rather than specifically as it is now in version.h. Also I think a version.h that has the proper build string in it may not be readily available in a general download of the source code. Could be a #define in avutil.h or function call. It's better than any lib_version function for tracking user installations etc. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1769> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker

1 7