Recherche avancée

Sur d’autres sites (9747)

• Call ffmpeg in c++ with system() function fails

  2 septembre 2014, par zhen lee

  I write a c++ program which needs to convert some(say:10) mp4 videos to flv videos.
  I use ffmpeg in my program for each video like this :

  system("ffmpeg -i video -filter:v yadif -ar 44100 -sameq -y -f flv temp.flv")

  however,it turns out :only first video will be converted successfully,the others will fail.
  it means :
  when i change the input order of which video to convert and re-execution the program,it behave the same:only the first video(will be different each time as i changed the input video order) will be converted successfully.

  The error message like :

  [h264 @ 0xaee0740] concealing 45 DC, 45 AC, 45 MV errors
  [h264 @ 0xaee0ce0] AVC : nal size 305665
  Last message repeated 1 times
  [h264 @ 0xaee0ce0] no frame !
  [h264 @ 0xaee1280] AVC : nal size 572993
  Last message repeated 1 times
  [h264 @ 0xaee1280] no frame !
  [aac @ 0xad9ccc0] channel element 0.13 is not allocated
  Error while decoding stream #0:1
  [aac @ 0xad9ccc0] channel element 0.13 is not allocated
  Error while decoding stream #0:1
  [aac @ 0xad9ccc0] channel element 0.13 is not allocated
  Error while decoding stream #0:1
  ......
  The most strange thing is :when i run ffmpeg command in bash shell,all video will be converted successfully .

  After google it,I have try these(certainly failed) :

  1. remove -sameq option,the result is same ;

  2. write ffmpeg commod in a shell script ConvertToFlv.sh like :

     /usr/local/bin/ffmpeg -i "$dir/$1" -filter:v yadif -ar 44100 -sameq -y -f flv "$dir/temp.fiv"

     then call this script in program like

     system("ConvertToFlv.sh"+video)

     or

     system("sh ConvertToFlv.sh"+video)

     The result is same.

  The ffmpeg configure is :

    ffmpeg version 0.9.1.git Copyright (c) 2000-2012 the FFmpeg developers
  
    built on Dec 17 2012 16:17:30 with gcc 4.1.2 20080704 (Red Hat 4.1.2-48)
  
    configuration: --enable-gpl --enable-postproc --enable-nonfree --enable-postproc --enable-swscale --enable-avfilter --enable-pthreads --enable-libxvid --enable-libx264 --enable-libmp3lame --enable-libfaac --disable-ffserver --disable-ffplay
  
    libavutil      51. 41.100 / 51. 41.100
  
    libavcodec     54.  4.100 / 54.  4.100
  
    libavformat    54.  1.100 / 54.  1.100
  
    libavdevice    53.  4.100 / 53.  4.100
  
    libavfilter     2. 62.101 /  2. 62.101
  
    libswscale      2.  1.100 /  2.  1.100
  
    libswresample   0.  7.100 /  0.  7.100
  
    libpostproc    52.  0.100 / 52.  0.100

  and my machine envirment is :

  Linux master 2.6.18-194.el5 #1 SMP Fri Apr 2 14:58:14 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

  I’m irritable now,I hope someone can give me some advice,really appreciate it.

• What Every Programmer Should Know

  24 décembre 2012, par Multimedia Mike — General

  During my recent effort to force myself to understand Unicode and modern text encoding/processing, I was reminded that this is something that “every programmer should just know”, an idea that comes up every so often, usually in relation to a subject in which the speaker is already an expert. One of the most absurd examples I ever witnessed was a blog post along the lines of “What every working programmer ought to know about [some very specific niche of enterprise-level Java programming]“. I remember reading through the article and recognizing that I had almost no knowledge of the material. Disturbing, since I am demonstrably a “working programmer”.

  For fun, I queried the googles on the matter of what ever programmer ought to know.

  Specific Topics
  Here is what every programmer should know about : Unicode, time, memory (simple), memory (extremely in-depth), regular expressions, search engine optimization, floating point, security, basic number theory, race conditions, managed C++, VIM commands, distributed systems, object-oriented design, latency numbers, rate monotonic algorithm, merging branches in Mercurial, classes of algorithms, and human names.

  Broader Topics
  20 subjects every programmer should know, 97 things every programmer should know, 12 things every programmer should know, things every programmer should know (27 items), 10 papers every programmer should read at least twice, 10 things every programmer should know for their first job.

  Meanwhile, I remain fond of this xkcd comic whose mouseover text describes all that a person genuinely needs to know. Still, the new year is upon us, a time when people often make commitments to bettering themselves, and it couldn’t hurt (much) to at least skim some of the lists and find out what you never knew that you never knew.

  What About Multimedia ?
  Reading the foregoing (or the titles of the foregoing pieces), I naturally wonder if I should write something about what every programmer should know about multimedia. I think it would look something like a multimedia programming FAQ. These are some items that I can think of :

  1. YUV : The other colorspace (since most programmers are only familiar with RGB and have no idea what to make of the YUV that comes out of most video decoding APIs)
  2. Why you can’t easily seek randomly to any specific frame in a video file (keyframe/interframe discussion and their implications)
  3. Understand your platform before endeavoring to implement multimedia software (modern platforms, particularly mobile platforms, probably provide everything you need in the native APIs and there is likely little reason to compile libavcodec for the platform)
  4. Difference between containers and codecs (longstanding item, but I would argue it’s less relevant these days due to standardization on the MPEG — MP4/H.264/AAC — stack)
  5. What counts as a multimedia standard in this day and age (comparing the foregoing MPEG stack with the WebM/VP8/Vorbis stack)
  6. Trade-offs to consider when engineering a multimedia solution
  7. Optimization doesn’t always work the way you think it does (not everything touted as a massive speed-up in the world of computing — whether it be multithreaded CPUs, GPGPUs, new SIMD instruction sets — will necessarily be applicable to multimedia processing)
  8. A practical guide to legal issues would not be amiss
  9.  ???

  What other items count as “something multimedia-related that every programmer should know” ?

• Convert RTP packets to WAV or AU using ffmpeg

  14 octobre 2014, par Jonas Kongslund

  I have a file containing a sequence of RTP packets wrapped in UDP/IP packets. I want to convert this file to a WAV or AU file and was told that ffmpeg may be able to do the job. However the tool does not behave as I would expect. For some reason it is expecting an SDP file but I do not have such a file and I am wondering why it is needed since the RTP packets seem to contain enough information in order to do the conversion. Also it is reporting the wrong payload type.

  Any ideas ? Below is what I have tried. The RTP packets in the input file alaw.rtp only have payload types 8 (A-law) and 72 (RTCP related) so I do not know where payload type 105 is coming from.

  $ ffmpeg -f rtp -i alaw.rtp alaw.au
  
  ...
  
  [rtp @ 0x9dbdfe0] Unsupported RTP version packet received
  
      Last message repeated 89 times
  
  [rtp @ 0x9dbdfe0] Unable to receive RTP payload type 105 without an SDP file describing it
  
  [rtp @ 0x9dbdfe0] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, rtp, from 'alaw.rtp':
  
    Duration: N/A, bitrate: N/A
  
  File 'alaw.au' already exists. Overwrite ? [y/N] y
  
  Output #0, au, to 'alaw.au':
  
  Output file #0 does not contain any stream

  This is the version of ffmpeg that I have used

  ffmpeg version 0.10.6-6:0.10.6-0ubuntu0jon1~lucid2
  
  built on Nov 12 2012 15:20:22 with gcc 4.4.3