Recherche avancée

Sur d’autres sites (6014)

• Video upload size

  16 mai 2014, par Jonas m

  I’m having a hard time figuring this one out, so hopefully, some of you who has tried this before, will take the time to reply and share your knowledge.

  I’m working on a site, which after release, will be feeded in the television and other commercial places. The site asks the user to upload a video with a story, and we expect alot of people to do so.

  My problem is the whole storage/space talk. A normal, unencoded iPhone recording easily fills around 100-120 MB for a minute or two.

  I’ve tried setting up and using FFMPEG to re-encode the movies, but the problem is, that one encoding sucks up 100% of the CPU, leaving the site inaccisible for anybody else.

  Is there anything you could suggest, which would be sufficient for such a site ? The client is on a budget, so price is a consideration aswell. Best of all would be a free alternative to etc. FFMPEG, but with less CPU usage.

  My specs are as follows
  CentOs 6 on a
  1GB ram DigitalOcean cloud service with nginx + php-fpm and mysql.

  Im hoping for some cleaver folks to answer this !
  Thanks in advance.
  Jonas

• an error happened : spawn ENOENT, node.js & FFmpeg

  20 juin 2014, par user2757842

  I am having a nightmare of a time trying figure this out. I asked a question about this yesterday but only got so far, long story short, I cannot for the life of me figure this out.

  All i want to do, is transcode a .avi file to a .flv file using FFmpeg in a node.js app, this works just using the command line for FFmpeg but not in the app, here’s the code :

  var ffmpeg = require('fluent-ffmpeg');
  
  
  
  //make sure you set the correct path to your video file
  
  var proc = new ffmpeg({ source: 'C:/Users/Jay/Documents/movie/drop.avi', nolog: true });
  
  
  
  //Set the path to where FFmpeg is installed
  
  proc.setFfmpegPath("C:\\Users\\Jay\\Documents\\FFMPEG\\bin");
  
  
  
  proc
  
  //set the size
  
  //.withSize('50%') <-- error appears after this line
  
  
  
  // set fps
  
  //.withFps(24)
  
  
  
  // set output format to force
  
  //.toFormat('flv')
  
  
  
  // setup event handlers
  
  .on('end', function() {
  
      console.log('file has been converted successfully');
  
  })
  
  .on('error', function(err) {
  
      console.log('an error happened: ' + err.message);
  
  })
  
  // save to file <-- the new file I want -->
  
  .saveToFile('C:/Users/Jay/Documents/movie/drop.flv');

  The error appears on the line specified above, it’s not an error with red writing, but it simply says :

  an error happened: spawn ENOENT

  Has anyone come across this ?

• libFLAC/cpu.c : Simplify OS SSE support detection.

  28 juillet 2014, par Erik de Castro Lopo

  libFLAC/cpu.c : Simplify OS SSE support detection.
  Simplify the code that tries to detect whether OS supports SSE instructions.
  a) Linux : "old" vs "new" sigaction
  OBSOLETE_SIGCONTEXT_FLAVOR was disabled in Mar 2007 in commit 1ca3a445f.
  
  According to <http://unixhelp.ed.ac.uk/CGI/man-cgi?sigaction>: "Support for
  
  SA_SIGINFO was added in Linux 2.2" (released in Jan 1999). If noone wants to
  
  use FLAC with Linux kernel 2.0 then it’s safe to delete this code.
  b) MSVC : try/catch vs. sigill_handler
  TRY_CATCH_FLAVOR was enabled in Jan 2009 in commit a832ef32. According to the
  
  comment in cpu.c, "sigill_handler flavor resulted in several crash reports on
  
  win32". Also this sigill_handler flavor is not thread-safe.
  c) MinGW : fxsave/fxrestore vs. sigill_handler
  The code was added Mar 2014 in commit 99d5154f. It’s better to use FXSR flavor
  
  instead of sigill_handler flavor. The reasons are the same as for MSVC.
  Patch-from : lvqcl <lvqcl.mail@gmail.com>
  

  • [DH] src/libFLAC/cpu.c