Recherche avancée

Sur d’autres sites (12583)

• Revision 11e3ac62a5 : Fixing display size setting problem. Fix of https://code.google.com/p/webm/issu

  23 août 2013, par Dmitry Kovalev

  Changed Paths :
   Modify /vp9/decoder/vp9_decodframe.c

  
  
  Fixing display size setting problem.

  Fix of https://code.google.com/p/webm/issues/detail?id=608. We could have
  used invalid display size equal to the previous frame size (not to the
  current frame size).

  Change-Id : I91b576be5032e47084214052a1990dc51213e2f0

• Added paste functionality to simplify uploading screenshots or images copied from the web (only supported by Google Chrome so far).

  24 octobre 2011, par Sebastian Tschan

  m example/index.html m jquery.fileupload.js Added paste functionality to simplify uploading screenshots or images copied from the web (only supported by Google Chrome so far).

• Piping stdout from child process directly to google cloud storage. Node.js

  2 octobre 2018, par glenn

  anyone here with expertise on piping to google cloud storage ?

  i am using FFmpeg on a server, and want to pipe to my storage bucket.

  I can get it working when I save FFmpeg output to a file, then createReadableStream from the file, and then pipe that to createWriteStream()

  however, I dont want to generate a static file, and then go through that process every time

  Why can I not just simply pipe FFmpeg.stdout.pipe(file.createWriteStream()) ?

  FYI : I am running FFmpeg as a child process

        spawnFFMPEG = () => {
  
  this.ffmpeg = child_process.spawn('ffmpeg',
  
    [
  
      '-f', 'lavfi', '-i', 'anullsrc',
  
      '-thread_queue_size', '512',
  
      '-i', '-',
  
      '-shortest', '-vcodec', 'copy',
  
      '-f', 'avi',
  
      'pipe:1'
  
    ]
  
  )
  
  
  
   this.ffmpeg.stdout.pipe(myWritableStream)