Recherche avancée

Sur d’autres sites (8550)

• php and ffmpeg from command line in windows - not working, nothing returns

  24 août 2015, par user3725395

  I’m trying to execute ffmpeg within a website and it never output’s a file, nothing return’s, I have tried it with parameters -version and that works fine.
  I can copy and paste the main command into dos and it also works fine.

  I’m stuck, I have tried many things including shell_exec but to no avail, nothing comes back other than array(0) int(0). help ?

   //$cmd = 'C:\ffmpeg.exe ffmpeg -version';
  
   $cmd = "C:\ffmpeg.exe -i C:\1.mp3 -i C:\2.mp3 -filter_complex amerge -c:a libmp3lame -q:a 4 C:\out.mp3";
  
   echo exec($cmd, $o, $v);
  
   var_dump($o);
  
   var_dump($v);

• mergeToFile returns null

  4 avril 2020, par Andrew Roberts

  I am trying to use fluent ffmpeg to merge a bunch of audio files into a single file, yet I keep recieving an error that the output is null/ doesn't exist.
My code :

  



       var ffmpeg = require("fluent-ffmpeg");
     var command = ffmpeg();
     for (var inputPath of filePaths) {
        command.addInput(inputPath);
        console.log("Added path:" + inputPath);
    }
    command
        .on('error', (err) => {
            console.log('An error occurred: ' + err.message);
        })
        .on('end', () => {
            console.log('Merging finished !');
        })
        .mergeToFile(path.join(os.tmpdir(), "result.mp3"), os.tmpdir());


  



  Error code :

  



  


  Read Error : Error : ENOENT : no such file or directory, open '/tmp/result.mp3'

  


  


• Revision 704028d435 : Experimental rate control change. When the codec in VBR (or cq) mode hits its m

  7 octobre 2013, par Paul Wilkins

  Changed Paths :
   Modify /vp9/encoder/vp9_onyx_if.c

  
  
  Experimental rate control change.

  When the codec in VBR (or cq) mode hits its max q limits and is
  struggling to hit a target bandwidth, the bit target per frame collapses.

  In the first instance normal frames cap out at the maximum allowed
  Q and then the ARF and GFs do the same. This latter behavior is not
  generally desirable as GFs and ARFs are only effective from a quality
  and data rate perspective if they have at lease some level of -Q delta
  compared to the surrounding frames.

  In this patch I define a separate max Q for GFs and ARFs that is
  derived from but somewhat lower than that defined for normal frames.
  In effect there is a minimum Q delta that will always be available for
  GFs and ARFs regardless of the target rate and MAXQ setting.

  This may of course mean that the absolute lowest rate obtainable for
  a given clip is somewhat higher.

  Change-Id : I268868b28401900d0cd87e51e609cd3b784ab54a