[FFmpeg-trac] #4057(ffprobe:new): ffprobe top_field_first shows zero on tff content

FFmpeg trac at avcodec.org
Sun Oct 26 17:43:55 CET 2014


#4057: ffprobe top_field_first shows zero on tff content
------------------------------------+-----------------------------------
             Reporter:  dericed     |                    Owner:
                 Type:  defect      |                   Status:  new
             Priority:  normal      |                Component:  ffprobe
              Version:  git-master  |               Resolution:
             Keywords:              |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+-----------------------------------

Comment (by dericed):

 Ah, you're right:

 {{{
 ffprobe tff.mov -show_entries frame=top_field_first,interlaced_frame
 ffprobe version git-2014-10-25-80b29c2 Copyright (c) 2007-2014 the FFmpeg
 developers
   built on Oct 25 2014 11:44:58 with Apple LLVM version 6.0
 (clang-600.0.54) (based on LLVM 3.5svn)
   configuration: --prefix=/usr/local/Cellar/ffmpeg/HEAD --enable-shared
 --enable-pthreads --enable-gpl --enable-version3 --enable-nonfree
 --enable-hardcoded-tables --enable-avresample --enable-vda --cc=clang
 --host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-
 libmp3lame --enable-libxvid --enable-libfreetype --enable-libass --enable-
 ffplay --enable-libopenjpeg --disable-decoder=jpeg2000 --extra-
 cflags='-I/usr/local/Cellar/openjpeg/1.5.1_1/include/openjpeg-1.5 '
   libavutil      54. 11.100 / 54. 11.100
   libavcodec     56.  9.100 / 56.  9.100
   libavformat    56. 10.100 / 56. 10.100
   libavdevice    56.  1.100 / 56.  1.100
   libavfilter     5.  2.100 /  5.  2.100
   libavresample   2.  1.  0 /  2.  1.  0
   libswscale      3.  1.101 /  3.  1.101
   libswresample   1.  1.100 /  1.  1.100
   libpostproc    53.  3.100 / 53.  3.100
 [dv @ 0x7f8a0b80da00] Estimating duration from bitrate, this may be
 inaccurate
 Input #0, dv, from 'tff.mov':
   Metadata:
     timecode        : 00:00:00:00
   Duration: 00:00:00.50, start: 0.000000, bitrate: 28771 kb/s
     Stream #0:0: Video: dvvideo, yuv411p, 720x480 [SAR 8:9 DAR 4:3], 28771
 kb/s, 29.97 fps, 29.97 tbr, 29.97 tbn, 29.97 tbc
 [FRAME]
 interlaced_frame=1
 top_field_first=1
 [/FRAME]
 [FRAME]
 interlaced_frame=1
 top_field_first=1
 [/FRAME]
 }}}

 So perhaps this means that the interlacement metadata is not passing
 through the movie filter. The reason I was using the movie filter is that
 I was hoping to generate one command to gather both info from idet about
 interlacement as well as info about what the codec/container says about
 interlacement to identify conflicts.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/4057#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list