Recherche avancée

Sur d’autres sites (7392)

• Concert MP4 Version - FFmpeg

  25 avril 2017, par Luzwitz

  I have two mp4 File :

  1. out.mp4 : ISO Media, MP4 Base Media v1 [IS0 14496-12:2003]
  2. video/rio2016/finale/brasse/200.mp4 : ISO Media, MP4 v2 [ISO 14496-14]

  How can I convert 1 to 2 (mp41 to mp42) ?

  Thanks !

• How to configure proc_open "pipes" for ffmpeg stdin/stderr on Windows ?

  10 septembre 2018, par GDP

  Firstly, I’ve spent the week googling and trying variations of dozens and dozens of answers for Unix, but it’s been a complete bust, I need an answer for Windows, so this is not a duplicate question of the Unix equivalents.

  We’re trying to create a scheduled task that will process a queue of tasks in PHP, and maintain an array of up to 10 ffmpeg instances at a time. I’ve tried exec, shell_exec and proc_open , coupled with/without start /B without any "complete" luck.
  I’m also quite certain that it has to do with setting up the descriptorspec and pipes (which I’m completely unfamiliar with), and here’s why :

  Per https://trac.ffmpeg.org/wiki/PHP,

  The part that says ">/dev/null" will redirect the standard OUTPUT
  (stdout) of the ffmpeg instance to /dev/null (effectively ignoring the
  output) and "2>/dev/null" will redirect the standard ERROR (stderr) to
  /dev/null (effectively ignoring any error log messages). These two can
  be combined into a shorter representation : ">/dev/null 2>&1". If you
  like, you can ?read more about I/O Redirection.

  An important note should be mentioned here. The ffmpeg command-line
  tool uses stderr for output of error log messages and stdout is
  reserved for possible use of pipes (to redirect the output media
  stream generated from ffmpeg to some other command line tool). That
  being said, if you run your ffmpeg in the background, you’ll most
  probably want to redirect the stderr to a log file, to be able to
  check it later.

  One more thing to take care about is the standard INPUT (stdin).
  Command-line ffmpeg tool is designed as an interactive utility that
  accepts user’s input (usually from keyboard) and reports the error log
  on the user’s current screen/terminal. When we run ffmpeg in the
  background, we want to tell ffmpeg that no input should be accepted
  (nor waited for) from the stdin. We can tell this to ffmpeg, using I/O
  redirection again "

  echo "Starting ffmpeg...\n\n";
  
  echo shell_exec("ffmpeg -y -i input.avi output.avi null >/dev/null 2>/var/log/ffmpeg.log &");
  
  echo "Done.\n";

  This example actually uses shell_exec, though we want to use proc_open so that we can use a loop to check if the process has completed or not.

  Here’s a basic sample loop of what I’ve tried. The problem in executing this is that the actual ffmpeg processing completes, but the process is hung "waiting for something". When I use debugging, and step out of the loop and terminate the process after a few minutes, the ffmpeg output is written and the script carries on. (From the command line, ffmpeg takes less than a minute to complete)

  $descriptorspec = array(
  
      array('pipe', 'r'),
  
      array('pipe', 'w'),
  
      array('pipe', 'w'),
  
  );
  
  $pipes = null;
  
  $cwd = null;
  
  $env = null;
  
  $process = proc_open('start /B ffmpeg.exe -i input.mov output.mp4 -nostdin', $descriptorspec, $pipes, $cwd, $env);
  
  $status = proc_get_status($process);
  
  while($status['running']) {
  
      sleep (60);
  
      $status = proc_get_status($process);
  
  }
  
  proc_terminate($process);

  Also, as documented at ffmpeg Main-options :

  Enable interaction on standard input. On by default unless standard
  input is used as an input. To explicitly disable interaction you need
  to specify -nostdin.

  The -nostdin option seems to indicate that it addresses my problem, but it has no apparent affect. In all solutions for Unix that I’ve found, it appears to still require some form of this this unix added : null or 2>&1.

  So, with that somewhat exhaustive prologue, can someone explain how to properly configure the proc_open function to satisfy how ffmpeg.exe interacts with I/O ? If there is a better or more appropriate approach, I’m happy to do that, but the important thing is to be able to loop thru an array of processes to check if they’re complete, so that other faster processes can complete in the meantime.

  UPDATE
  After exhaustive R&D, it seems that the I/O is not the issue in making this happen (the -nostdin option seems to work as advertised). The premise of my design was to use proc_get_status() to determine when ffmpeg was finished. The flaw in that approach is that apparently that does NOT return the actual PID of the ffmpeg process...it returns the parent PID. So, when proc_get_status() returned that the video conversion was complete, it was in fact still running, not hung. This was further complicated by testing on larger video files. The larger the video, the longer the "residual" time was that it took to actually finish — the I/O wasn’t the issue - watching the Parent PID instead of the child PID was the problem. So, without getting into much lower level system internals with Windows, this doesn’t appear to be possible with PHP directly. I’ve decided to abandon this approach, but hopefully this discovery will save someone else some time and trouble.

• More Cinepak Madness

  20 octobre 2011, par Multimedia Mike — Codec Technology

  Fellow digital archaeologist Clone2727 found a possible fifth variant of the Cinepak video codec. He asked me if I cared to investigate the sample. I assured him I wouldn’t be able to die a happy multimedia nerd unless I have cataloged all possible Cinepak variants known to exist in the wild. I’m sure there are chemistry nerds out there who are ecstatic when another element is added to the periodic table. Well, that’s me, except with weird multimedia formats.

  Background
  Cinepak is a video codec that saw widespread use in the early days of digital multimedia. To date, we have cataloged 4 variants of Cinepak in the wild. This distinction is useful when trying to write and maintain an all-in-one decoder. The variants are :

  1. The standard type : Most Cinepak data falls into this category. It decodes to a modified/simplified YUV 4:2:0 planar colorspace and is often seen in AVI and QuickTime/MOV files.
  2. 8-bit greyscale : Essentially the same as the standard type but with only a Y plane. This has only been identified in AVI files and is distinguished by the file header’s video bits/pixel field being set to 8 instead of 24.
  3. 8-bit paletted : Again, this is identified by the video header specifying 8 bits/pixel for a Cinepak stream. There is essentially only a Y plane in the data, however, each 8-bit value is a palette index. The palette is transported along with the video header. To date, only one known sample of this format has even been spotted in the wild, and it’s classified as NSFW. It is also a QuickTime/MOV file.
  4. Sega/FILM CPK data : Sega Saturn games often used CPK files which stored a variant of Cinepak that, while very close the standard Cinepak, couldn’t be decoded with standard decoder components.

  So, a flexible Cinepak decoder has to identify if the file’s video header specified 8 bits/pixel. How does it distinguish between greyscale and paletted ? If a file is paletted, a custom palette should have been included with the video header. Thus, if video bits/pixel is 8 and a palette is present, use paletted ; else, use greyscale. Beyond that, the Cinepak decoder has a heuristic to determine how to handle the standard type of data, which might deviate slightly if it comes from a Sega CPK file.

  The Fifth Variant ?
  Now, regarding this fifth variant– the reason this issue came up is because of that aforementioned heuristic. Basically, a Cinepak chunk is supposed to store the length of the entire chunk in its header. The data from a Sega CPK file plays fast and loose with this chunk size and the discrepancy makes it easy to determine if the data requires special handling. However, a handful of files discovered on a Macintosh game called “The Journeyman Project : Pegasus Prime” have chunk lengths which are sometimes in disagreement with the lengths reported in the containing QuickTime file’s stsz atom. This trips the heuristic and tries to apply the CPK rules against Cinepak data which, aside from the weird chunk length, is perfectly compliant.

  Here are the first few chunk sizes, as reported by the file header (stsz atom) and the chunk :

  size from stsz = 7880 (0x1EC8) ; from header = 3940 (0xF64)
  size from stsz = 3940 (0xF64) ; from header = 3940 (0xF64)
  size from stsz = 15792 (0x3DB0) ; from header = 3948 (0xF6C)
  size from stsz = 11844 (0x2E44) ; from header = 3948 (0xF6C)
  

  Hey, there’s a pattern here. If they don’t match, then the stsz size is an even multiple of the chunk size (2x, 3x, or 4x in my observation). I suppose I could revise the heuristic to state that if the stsz size is 2x, 3x, 4x, or equal to the chunk header, qualify it as compliant Cinepak data.

  Of course it feels impure, but software engineering is rarely about programmatic purity. A decade of special cases in the FFmpeg / Libav codebases are a testament to that.

  What’s A Variant ?
  Suddenly, I find myself contemplating what truly constitutes a variant. Maybe this was just a broken encoder program making these files ? And for that, I assign it the designation of distinct variation, like some sort of special, unique showflake ?

  Then again, I documented Magic Carpet FLIC as being a distinct variant of the broader FLIC format (which has an enormous number of variants as well).