Recherche avancée

Sur d’autres sites (8403)

• PHP shell_exec wait for script to done ? [duplicate]

  6 mars 2016, par Melih Büyükbayram

  This question already has an answer here :

  • PHP shell_exec wait for script to finish ? [duplicate]
    
    1 answer
    

  I have a PHP script that queries a database for a list of jobs to be done and fires off other PHP scripts based on what it finds in the database (basically a process queue).

  Some of the scripts that the queue runner script executes may take 30 seconds or so to finish running (convert video, resizing images, etc).

  The problem is that shell_exec() in the queue runner script calls the processing scripts, but then doesn’t wait for them to finish, resulting in the queue not being completed.

  Queue runner script :

  #!/usr/bin/php
  
  <?php
  
      // Loop through database and find jobs to be done
  
      shell_exec("nohup $command > /dev/null 2> /dev/null & echo $! &");
  
  ?>

  Running the job script directly from the command line works and the PDF is created.

  Any ideas on how to fix this ? Or a better way to run a process queue ?

• ffmpeg : videos before and after conversion aren't the same length

  16 juillet 2012, par Koyot

  I have a set of .mov videos which require conversion to .mp4 format. I'm using ffmpeg and running this command :

  ffmpeg -i Banking.mov -vsync -async -sameq -ac 1 -ab 64k -ar 44100 Banking.mp4

  There is a slight difference between input and output video in time length (00:03:35.407 and 00:03:35.582). And here's the catch - I'm storing time cue set at precise times in a file which is used by a program to point at specific scenes. The 0.1 second difference causes it to point at wrong scenes, therefore making the cue set useless. Is there any possibility to preserve exactly the same time in different format ?

     FFmpeg version CVS, Copyright (c) 2000-2004 Fabrice BellardMac OSX universal build for ffmpegX
  
    configuration:  --enable-memalign-hack --enable-mp3lame --enable-gpl --disable-vhook --disable-ffplay --disable-ffserver --enable-a52 --enable-xvid --enable-faac --enable-faad --enable-amr_nb --enable-amr_wb --enable-pthreads --enable-x264 
  
    libavutil version: 49.0.0
  
    libavcodec version: 51.9.0
  
    libavformat version: 50.4.0
  
    built on Apr 15 2006 04:58:19, gcc: 4.0.1 (Apple Computer, Inc. build 5250)
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x5597b8]negative ctts, ignoring
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Banking.mov':
  
    Duration: 00:03:35.6, start: 0.000000, bitrate: 1400 kb/s
  
    Stream #0.0(eng): Audio: pcm_s16be, 24000 Hz, stereo, 768 kb/s
  
    Stream #0.1(eng), 29.97 fps(r): Video: h264, yuv420p, 720x480
  
  Output #0, mp4, to 'Banking.mp4':
  
    Stream #0.0, 29.97 fps(c): Video: mpeg4, yuv420p, 720x480, q=2-31, 200 kb/s
  
    Stream #0.1: Audio: aac, 44100 Hz, mono, 64 kb/s
  
  Stream mapping:
  
    Stream #0.1 -> #0.0
  
    Stream #0.0 -> #0.1
  
  Press [q] to stop encoding
  
  frame= 6461 q=0.0 Lsize=   53181kB time=215.3 bitrate=2023.3kbits/s    
  
  video:51437kB audio:1618kB global headers:0kB muxing overhead 0.237816%

• Replacing the standard Android H264 software encoder with an ffmpeg based one

  10 août 2012, par rubenvb

  In Android ICS and later, a new OpenMax IL API version is in use, making old binary blobs useless/unused. This leads to older devices that otherwise run ICS just fine and dandy to have broken video playback (YouTube HQ and IMBD, for example) because Androids fallback software decoder sucks when compared to what ffmpeg can do on the same device (I tested MXPlayer+arm6vfp ffmpeg and a 720p movie played back great).

  I am trying to dig through the Android source code to see where and what exactly I could add/replace code to allow the ffmpeg library's awesomeness to be used. The problem is I don't know exactly what code is being used in for example the YouTube app to decode video, or how that's decided.

  So I have two options as far as I can tell :

  1. Figure out the current software decoder being used, and try to wrap its external interface around ffmpeg, effectively replacing the slow software decoder currently used. The end result would be a single .so I could push to the device.

  2. Figure out how to trick Android into thinking an OMX library based on ffmpeg (I have built one succesfully for Android : limoa) and add this somewhere to the list of considered libraries (or better : replace the unusable hardware codec).

  As an extension, I'd like to also make camcorder video encoding work through this, so a true integrated solution would be very much wanted. The question is : how, and where, and what ? Searching the Android source tree gives numerous counts of "H264" and related stuff in many different places. I need the lowest and simplest possible, so I can simply wrap the hypothetical decode(buffer) function call to use ffmpeg (libavcodec).