Recherche avancée

Sur d’autres sites (4027)

• Updating ffmpeg on Ubuntu 12.04 ; conflicts with old version from standard repository

  29 octobre 2016, par Frank van Wensveen

  I have never used ffmpeg on my Ubuntu Linux 12.04 (Precise Pangolin) box until now. Typing ’ffmpeg’ at the command prompt revealed that ffmpeg 0.8.17 (listed as ffmpeg 0.8.17-4:0.8.17-0ubuntu0.12.04.2) was installed. Seeing as I need to convert h.265 to h.264, an update was obviously required.

  Following posted instructions, I installed a ream of packages :

  $ sudo apt-get install faad libmp4v2-dev libfaac0 libfaac-dev
  
  libxvidcore4 libxvidcore4-dev liba52-0.7.4 liba52-0.7.4-dev libx264-dev
  
  libgsm-tools libogg-dev libtheora-bin libfaad-dev libvorbis-dev 
  
  libtheora-dev libdts-dev git-core yasm texi2html checkinstall

  followed by

  $ sudo apt-get purge ffmpeg

  in order to get rid of the old stuff from the original repo.

  Downloaded the latest ffmpeg, and a ."/configure ; make ; sudo make install" later, I should be in business.

  Except that typing ’ffmpeg’ at the prompt still fired up the old version. A quick look revealed that the old ffmpeg binary was still sitting in /usr/bin with the new one being installed in /usr/local/bin. But ffmpeg is no longer listed as an installed package, and sudo apt-get remove ffmpeg tells me that "Package ffmpeg is not installed, so not removed".

  Running /usr/local/bin/ffmpeg directly works, however then fails in an Unknown encoder ’libx264’ error. Which is puzzling because the package libx264-120 is installed and /usr/lib/i386-linux-gnu/libx264.so.120 (with the appropriate symlink to /usr/lib/i386-linux-gnu/libx264.so) does exist.

  Maybe I’ve been looking at this for too long, because I’m sure this is a simple issue but I just can’t see it.

  Can someone please hand me the stupid had and point out why I deserve to wear it ?

  Tnx !

• AWS Lambda execution time for FFMPEG transcoding

  4 janvier 2023, par FlamingMoe

  I'm using AWS Lambda for converting files from WEBM to MP4

  


  I'm using ffmpeg version 4.3.1-static https://johnvansickle.com/ffmpeg/ (I have done the following tests also with the ffmpeg in serverless AWS ffmpeg layer (that includes de 4.1.3), but results are even worse (about 25% slower)

  


  I'm using Node 10x as container.

  


  WEBM size   Time to convert.  Memory Lambda.  Memory used (as shown in log)

80Mb             ~44s              3008            410
40Mb             ~44s              3008            375

80Mb             ~70s              1024            321
40Mb             ~70s              1024            279


  


  All videos are 80s length. So as far as I can see, it does not matter the size of the WEBM, if the length of the video is the same, it takes the same to convert. So ffmpeg takes more time if the video length is higher, not if the file size is higher ... curious ;-)

  


  But in the other hand, I'm confused with Lambda memory. I know memory and CPU comes together in Lambda ... the more memory you choose, the more CPU is assigned.

  


  But...

  


  

  1. Why ffmpeg just take about 300/400Mb if it has more to run ?

  


  2. How can I tell ffmpeg to use more memory ?

  


  3. Is there any option to accelerate the process in Lambda ?

  


  


  Btw, In all tests, all ffmpeg are the same, and

  


  cpu-used paramenter)

  


  

  • I added to ffmpeg parameters cpu-used=100, and it does not matter at all if I put cpu-used=5 ... times are the same, so I guess that parameter is useless (i don't know why)

  


  


  threads parameter)

  


  

  • Also I did some tests with "threads" parameters, but it's useless also.

  


  


  I know it's not a good comparison, but same files takes about 5 seconds to be converted in a simple dedicated server (8 vCores and 8GB RAM in OVH Centos VPS).

  


  Btw, Amazon Elastic Transcoder is not an option :
a) it's extremely more expensive
b) it has just his profiles to convert, and my ffmpeg commands are very complex (watermarks, effects, etc ...)

  


• How can I use FFMpeg with PHP in a Vagrant environment ?

  31 juillet 2015, par curtisblackwell

  I’ve got this working on a DigitalOcean server, but I can’t seem to get it working locally.

  My Vagrant box is ubuntu/trusty64. When I ssh into the machine to check out the permissions of the ffmpeg binary, it’s 664. I tried running chmod 755 ffmpeg (w/ and w/o sudo), but it has no effect and outputs no response. I’m the owner, so chown wouldn’t make any difference (but also doesn’t work, w/ or w/o sudo). Outside of the Vagrant machine, the file permissions are 755 and owned by me, though that doesn’t seem to matter.

  The binaries are static builds from a site linked to on the official FFMpeg site’s download page.

  Running cat /etc/*-release on both the remote DO server and the Vagrant machine returns the same result :

  DISTRIB_ID=Ubuntu
  
  DISTRIB_RELEASE=14.04
  
  DISTRIB_CODENAME=trusty
  
  DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
  
  NAME="Ubuntu"
  
  VERSION="14.04.2 LTS, Trusty Tahr"
  
  ID=ubuntu
  
  ID_LIKE=debian
  
  PRETTY_NAME="Ubuntu 14.04.2 LTS"
  
  VERSION_ID="14.04"
  
  HOME_URL="http://www.ubuntu.com/"
  
  SUPPORT_URL="http://help.ubuntu.com/"
  
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

  When attempting to execute the binary through PHP on the Vagrant machine (with exec()), I get a 126 exit code.

  What else should I try to get this working ?