[FFmpeg-user] segfault in ffmpeg when including yadif in chain
Nicolas George
nicolas.george at normalesup.org
Tue Aug 7 12:17:24 CEST 2012
Le primidi 21 thermidor, an CCXX, Misha Penkov a écrit :
> Hi,
>
> I'm trying to deinterlace a 1440x1080 interlaced video.
> Unfortunately, the ffmpeg executable segfaults:
>
> $ ~/git-ext/ffmpeg/ffmpeg -i 1440x1080i.avi -vf yadif -y output.avi
> ffmpeg version N-43291-gcf753d5 Copyright (c) 2000-2012 the FFmpeg developers
> built on Aug 7 2012 19:06:29 with gcc 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1)
> configuration: --enable-gpl --enable-libfaac --enable-libmp3lame
> --enable-libopencore-amrnb --enable-libopencore-amrwb
> --enable-libtheora --enable-libvorbis --enable-libx264
> --enable-nonfree --enable-postproc --enable-version3 --enable-x11grab
> --enable-libvpx --enable-shared --enable-pic --enable-libopencv
> libavutil 51. 66.101 / 51. 65.100
> libavcodec 54. 50.100 / 54. 44.100
> libavformat 54. 22.101 / 54. 19.100
> libavdevice 54. 2.100 / 54. 2.100
> libavfilter 3. 5.102 / 3. 3.100
> libswscale 2. 1.101 / 2. 1.100
> libswresample 0. 15.100 / 0. 15.100
> libpostproc 52. 0.100 / 52. 0.100
> Input #0, avi, from '1440x1080i.avi':
> Metadata:
> encoder : Lavf54.19.100
> Duration: 00:00:09.99, start: 0.000000, bitrate: 13775 kb/s
> Stream #0:0: Video: mpeg2video (Main) (mpg2 / 0x3267706D),
> yuv420p, 1440x1080 [SAR 4:3 DAR 16:9], 24000 kb/s, 59.94 fps, 29.97
> tbr, 59.94 tbn, 59.94 tbc
> Output #0, avi, to 'output.avi':
> Metadata:
> ISFT : Lavf54.19.100
> Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1440x1080
> [SAR 4:3 DAR 16:9], q=2-31, 200 kb/s, 29.97 tbn, 29.97 tbc
> Stream mapping:
> Stream #0:0 -> #0:0 (mpeg2video -> mpeg4)
> Press [q] to stop, [?] for help
> Segmentation fault
>
> What could be the problem?
Unfortunately, more or less anything. Does it segfault too with "-f null -"
instead of "output.avi"? Can you produce a valgrind dump (using ffmpeg_g
rather than ffmpeg), and/or a gdb backtrace?
> The video is approx. 17MB, so I can provide it if required.
Unless you manage to reproduce the segfault with readily available material
or purely internal features, that would be nice. The simplest way is
probably to see if you can reproduce the problem with only the first few
megabytes of the file, and attach it to a trac ticket.
Regards,
--
Nicolas George
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-user/attachments/20120807/0f62d25c/attachment.asc>
More information about the ffmpeg-user
mailing list