Recherche avancée

Sur d’autres sites (10077)

• ffmpeg - Input link in1:v0 parameters (size 640x640, SAR 16:9) do not match the corresponding output link in0:v0 parameters (640x640, SAR 427:240)

  19 mai 2016, par fobus

  I’m trying to concat 4 mp4 files. I’m using the command below but not able to concat

  ffmpeg -i new1.mp4 -i new2.mp4 -i new3.mp4 -i new4.mp4 -filter_complex concat=n=4:v=1:a=1 output.mp4

  Getting this error :

  Input link in1:v0 parameters (size 640x640, SAR 16:9) do not match the corresponding output link in0:v0 parameters (640x640, SAR 427:240)

  All four vides has the same codec and same size (640x640) and the same bitrate (30)

  What I am doing wrong ?

• Unable to link against FFmpeg libaries

  28 octobre 2015, par Cody

  I tried to build this, but always got link-time error.

  #include <libavutil></libavutil>log.h>    
  
  int main(int argc, char *argv[])
  
  {
  
      ::av_log_set_flags(AV_LOG_SKIP_REPEATED);
  
      return 0;
  
  }

  My distro is Debian GNU/Linux 8 (jessie). The FFmpeg was built by myself, and the configure command was...

  $ ./configure --prefix=/usr/local --disable-static --enable-shared \
  
  > --extra-ldflags='-Wl,-rpath=/usr/local/lib'

  The link-error is as follows.

  $ g++ foo.cpp -D__STDC_CONSTANT_MACROS -Wall \
  
  > -Wl,-rpath=/usr/local/lib \
  
  > $(pkg-config --cflags --libs libavutil)
  
  /tmp/ccKzgEFb.o: In function `main':
  
  foo.cpp:(.text+0x17): undefined reference to `av_log_set_flags(int)'
  
  collect2: error: ld returned 1 exit status

  where the output of pkg-config is...

  $ pkg-config --cflags --libs libavutil
  
  -I/usr/local/include -L/usr/local/lib -lavutil

  The objdump shows that the shared object libavutil.so does have av_log_set_flogs inside.

  $ objdump --dynamic-syms /usr/local/lib/libavutil.so | grep 'av_log_set_flags'
  
  000260f0 g    DF .text  0000000a  LIBAVUTIL_54 av_log_set_flags

  Please note that the g++ command used to build the above application had a linker option -Wl,-rpath=/usr/local/lib, though it still doesn’t work. Also, I’ve tried to monitor with inotifywait if the other version provided by the distro were called. They were not, and the one being opened during execution of g++ was /usr/local/lib/libavutil.so.

  Summary :

  1. /usr/local/lib/libavutil.so does have the symbol.

  2. -rpath was used to force to link against the shared library.

  3. Why link-time error ? T_T

  Any suggestion or information would be highly appreciated ! Thanks !

  REEDIT : ffplay works fine and ldd shows it use /usr/local/lib/libavutil.so. So, the libraries seems not broken, and the problem becomes how to build my own codes to use the libraries.

• h264 decoding rtsp link error

  13 août 2015, par Yasin SOYASLAN

  I am receiving RTSP stream with live555 library and decode them with ffmpeg.
  At first, i couldnt decode data’s that come from live555. After a little search i learned that I needed to include the sequence (SPS) and picture parameter sets (PPS) for my frame data before sending frame to the FFmpeg.

  header : 00 00 00 01 67 4d 00 14 95 b8 58 25 90 00 00 00 01 68 ee 3c 80 00 00 00 01

  FFmpeg can’t decode H264 stream/frame data

  Now i can take frame but a tiny problem comes out. [![enter image description here][1]][1]

  3 packets still have problem. FFmpeg cant decode them i am suggesting they are special command. Because they are so small 9,4 and 5 byte come.

  Here they are

  [h264 @ 0x137c00] no frame !
  00 00 00 01 67 4d 00 14 95 b8 58 25 90 00 00 00 01 68 ee 3c 80 00 00 00 01 67 4d 00 14 95 b8 58 25 90
  [h264 @ 0x137c00] no frame !
  00 00 00 01 67 4d 00 14 95 b8 58 25 90 00 00 00 01 68 ee 3c 80 00 00 00 01 68 ee 3c 80
  [h264 @ 0x137c00] no frame !
  00 00 00 01 67 4d 00 14 95 b8 58 25 90 00 00 00 01 68 ee 3c 80 00 00 00 01 06 e5 01 ec 80
  [h264 @ 0x137c00] no frame !

  any suggestion ?