Recherche avancée

Sur d’autres sites (9802)

• CLI Extract date/time stamp (timestamp) from quicktime or mpeg files

  25 mai 2020, par vy32

  Is there a way to extract a date/time or a timestamp from various multi-media container files with Quicktime or MPEG2/MPEG4 ? I'm looking ideally for a command line tool. I have been able to get timestamps using ffprobe, part of the ffmpeg suite, but I haven't gotten the year, month and date. The camera had a clock so I'm pretty sure that this information was available.

  



  The history of this data file is that it was first shot on miniDV and transferred to a Mac over Firewire 800 using QuicktimePlayer to record the video. I'm told that the miniDV format is motion jpeg. The file command reports that the file is ISO Media, Apple QuickTime movie, Apple QuickTime (.MOV/QT).

  



  % ffprobe -f lavfi -i "movie=filename.mov,fps=fps=25[out0]" -show_frames -show_streams -show_entries frame=pkt_pts_time -of csv=p=0 2>&1 | head -30
ffprobe version 4.2.2 Copyright (c) 2007-2019 the FFmpeg developers
  built with Apple clang version 11.0.0 (clang-1100.0.33.17)
  configuration: --prefix=/opt/local --enable-swscale --enable-avfilter --enable-avresample --enable-libmp3lame --enable-libvorbis --enable-libopus --enable-librsvg --enable-libtheora --enable-libopenjpeg --enable-libmodplug --enable-libvpx --enable-libsoxr --enable-libspeex --enable-libass --enable-libbluray --enable-lzma --enable-gnutls --enable-fontconfig --enable-libfreetype --enable-libfribidi --disable-libjack --disable-libopencore-amrnb --disable-libopencore-amrwb --disable-libxcb --disable-libxcb-shm --disable-libxcb-xfixes --disable-indev=jack --enable-opencl --disable-outdev=xv --enable-audiotoolbox --enable-videotoolbox --enable-sdl2 --disable-securetransport --mandir=/opt/local/share/man --enable-shared --enable-pthreads --cc=/usr/bin/clang --arch=x86_64 --enable-x86asm --enable-libx265 --enable-gpl --enable-postproc --enable-libx264 --enable-libxvid --enable-nonfree --enable-libfdk-aac
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Input #0, lavfi, from 'movie=/Volumes/SanDiskSSD/Movies/Italy22.mov,fps=fps=25[out0]':
  Duration: N/A, start: 0.000000, bitrate: N/A
    Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 640x480 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc
0.000000
0.040000
0.080000
0.120000
0.160000
0.200000
0.240000
0.280000
0.320000
0.360000
0.400000
0.440000
0.480000
0.520000
0.560000
%


  



  I want output showing the year, month and date that this was shot.

  


• xface : Fix encoder crashes due to too small on-stack array.

  22 novembre 2014, par Reimar Döffinger

  xface : Fix encoder crashes due to too small on-stack array.
  Also add a FATE test.
  Signed-off-by : Reimar Döffinger <Reimar.Doeffinger@gmx.de>
  

  • [DH] libavcodec/xface.h
  • [DH] libavcodec/xfaceenc.c
  • [DH] libavformat/nut.c
  • [DH] tests/fate/vcodec.mak
  • [DH] tests/ref/vsynth/vsynth1-xface
  • [DH] tests/ref/vsynth/vsynth2-xface
  • [DH] tests/ref/vsynth/vsynth3-xface

• FFmpeg camera encode h264 mp4 muxing atom avcC is too small

  18 mai 2016, par alijandro

  I tried to encode Android camera preview frame to h264, and mux to mp4 container.

  I can created mp4 file successfully. But the mp4 format seems corrupted.

  Use the ffprobe, I got the following error.

  $ ffprobe o.mp4
  
  [h264 @ 0x209fe50] non-existing PPS 0 referenced
  
  [h264 @ 0x209fe50] decode_slice_header error
  
  [h264 @ 0x209fe50] no frame!
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x209ea60] decoding for stream 0 failed
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x209ea60] Could not find codec parameters for stream 0 (Video: h264 (avc1 / 0x31637661), none, 568x320, 505 kb/s): unspecified pixel format

  Then I use mp4info tool to see if the information is correct. I found this.

  $ mp4info o.mp4 
  
  mp4info version 2.0.0
  
  o.mp4:
  
  ReadProperties: atom 'avcC' is too small; overrun at property: configurationVersion (src/mp4atom.cpp,386)
  
  mp4info: can't open o.mp4

  By hexdump the content of file, I got this

  $ xxd o.mp4 |grep -A 5 -B 5 avcC
  
  0039170: 6331 0000 0000 0000 0001 0000 0000 0000  c1..............
  
  0039180: 0000 0000 0000 0000 0000 0238 0140 0048  ...........8.@.H
  
  0039190: 0000 0048 0000 0000 0000 0001 0000 0000  ...H............
  
  00391a0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
  
  00391b0: 0000 0000 0000 0000 0000 0000 0018 ffff  ................
  
  00391c0: 0000 0008 6176 6343 0000 0020 7374 7473  ....avcC... stts
  
  00391d0: 0000 0000 0000 0002 0000 004f 0000 0ea6  ...........O....
  
  00391e0: 0000 0001 0000 0000 0000 0058 7374 7373  ...........Xstss
  
  00391f0: 0000 0000 0000 0012 0000 0001 0000 0005  ................
  
  0039200: 0000 000a 0000 000f 0000 0014 0000 0019  ................
  
  0039210: 0000 001e 0000 0023 0000 0028 0000 0029  .......#...(...)

  If I didn’t add global header to AVCodecContext,

  if (ofmt_ctx->oformat->flags & AVFMT_GLOBALHEADER) {
  
      // oc_ctx->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
  
  }

  ffprobe can detect the format without error, also ffplay can play it. But the avcC atom still not correct. Other player cannot play it.

  Why the muxer didn’t write the correct avcC atom ?

  How can I solve it ?