Recherche avancée

Sur d’autres sites (6168)

• ffmpeg audio + image to video conversion not working

  19 avril 2017, par mdnba50

  Can’t get this to work. I have an image file(jpg) an audio file(mp3) and i want the output to be a video(mp4).

  I located where ffmpeg is installed with exec("whereis ffmpeg") and what is returned is /usr/include/ffmpeg.

  $mp3 = $_SERVER['DOCUMENT_ROOT']."/wp-content/channels/major.mp3";
  
  $image = $_SERVER['DOCUMENT_ROOT']."/wp-content/channels/thumbnails/default-2.jpg"; 
  
  
  
  $new = $_SERVER['DOCUMENT_ROOT']."/wp-content/channels/foo.mp4";
  
  
  
  
  
  exec("/usr/include/ffmpeg -i $mp3 -f image2 -loop 1 -i $image
  
  -r 15 -s 640x480 \
  
  -c:v libx264 -crf 18 -tune stillimage -preset medium \
  
  -shortest $new",$return,$output);
  
  
  
  var_dump($return);
  
  var_dump($output);

  Only thing returned is array(0) int(127).

  I check phpinfo() and ffmpeg is installed but ffmpeg-php gd support  disabled.

  How do i solve ? I’m familiar with PHP not command line.

• Creating an Init file from existing non-fragmented, segmented MP4 files

  20 novembre 2018, par slhck

  I am performing chunked encodes of longer video files, where I’ve split the original file into individual sequences that I have encoded separately. These sequences are files of different length, depending on where the scene cuts appear—they may be between 2 and 5 seconds long. They all start with an I-frame and are standalone.

  My encoded sequences are all MP4s, e.g. :

  test_0000.mp4
  
  test_0001.mp4
  
  test_0002.mp4
  
  test_0003.mp4
  
  test_0004.mp4

  They all have common properties :

  $ mp4info test_0000.mp4
  
  
  
  File:
  
    major brand:      isom
  
    minor version:    200
  
    compatible brand: isom
  
    compatible brand: iso2
  
    compatible brand: mp41
  
    fast start:       no
  
  
  
  Movie:
  
    duration:   2016 ms
  
    time scale: 1000
  
    fragments:  no
  
  
  
  ...

  Now, in order to play those with a DASH player, I have to create an initialization segment and individual fragmented MP4s.

  I could generate the fragmented MP4s via mp4fragment which I run on each standalone MP4 file :

  $ mp4info test_0000.m4s
  
  File:
  
    major brand:      isom
  
    minor version:    200
  
    compatible brand: isom
  
    compatible brand: iso2
  
    compatible brand: mp41
  
    compatible brand: iso5
  
    fast start:       yes
  
  
  
  Movie:
  
    duration:   2016 ms
  
    time scale: 1000
  
    fragments:  yes
  
  
  
  ...

  But obviously, these are now not according to spec, and all contain a moov atom :

  

  What I’d need is individual media segments with only one moof and mdat box, which then require an initialization segment with only a moov box.

  How can I generate that from the existing, already encoded segments ?

  I know this appears like an XY problem. In principle, I could already segment my original file directly after encoding, and run those encodes at the same time, e.g. using ffmpeg’s dash muxer, or MP4Box, however :

  • There is almost no control over the resulting segment sizes, with respect to minimum and maximum duration
  • This approach does not parallelize

  I have also checked Bento4 ; it does not seem to offer this functionality. Neither does FFmpeg. MP4Box behaves similarly. They all assume you have one long file to start with.

  ---

  I see I could splice off the ftyp and moov boxes from these “fake fragments” in order to create an initialization segment. But I would end up with segments containing multiple moof and mdat boxes, which is not according to the specification – it only allows one fragment and media data box :

  4. Media Segments

  […] one optional Segment Type Box (styp) followed by a single Movie Fragment Box (moof) followed by one or more Media Data Boxes (mdat).

  I guess I can live with this the styp not being present.

• Proper reading of MP3 file disrupted by ID3 tags

  3 septembre 2016, par PookyFan

  My semestral project is due this Thursday and I have major problem with reading MP3 file (the project is about sound analysis, don’t ask my what exactly is it about and why I’m doing it so late).

  First, I read first 10 bytes to check for ID3 tags. If they’re present, I’ll just skip to the first MP3 header - or at least that’s the big idea. Here is how I count ID3 tag size :

  if (inbuf[0] == 'I' && inbuf[1] == 'D' && inbuf[2] == '3') //inbuf contains first 10 bytes from file
  
  {
  
      int size = inbuf[3] * 2097152 + inbuf[4] * 16384 + inbuf[5] * 128 + inbuf[6]; //Will change to binary shifts later
  
      //Do something else with it - skip rest of ID3 tags etc
  
  }

  It works ok for files without ID3 tags and for some files with them, but for some other files ffmpeg (which I use for decoding) returns "no header" error, which means it didn’t catch MP3 header correctly. I know that since if I remove ID3 from that .mp3 file (with Winamp for example), no errors occur. The conclusion is that size count algorithm isn’t always valid.

  So the question is : how do I get to know how big exactly is entire ID3 part of the .mp3 file (all possible tags, album picture and whatever) ? I’m looking for it everywhere but I just keep finding this algorithm I posted above. Sometimes also something about some 10 bytes footer I need to take into account, but it seems it frequently gets more than 10 bytes for it to eventually catch proper MP3 frame.