Recherche avancée

Sur d’autres sites (3240)

• Pause/resume ffmpeg transcoding process

  27 janvier 2014, par XXX

  In my Android application I use Ffmpeg library written in C++. I use ffmpeg command ffmpeg -y -i in.mp4 -s 320x240 -c:a copy out.mp4 to reduce the size of media files on Android. Everything works well. But if the file is too large, then the smartphone's battery heats up. And I have a question : is it possible to stop a ffmpeg process, and then continue it later on ? When I am converting a large file, I would like to be able to start from where I left off. Or is there any way to avoid heating the battery. May be this way : cut the file into pieces, reduce each separately and paste together ?

  UPDATE

  I found this Pause any process you want in Linux. So I decided to try to apply it on Android.

  public static void pause()
  
  {
  
      try
  
      {
  
          Process      sh = Runtime.getRuntime().exec("su", null,null);
  
          OutputStream os = sh.getOutputStream();
  
          os.write(("sudo -kill -STOP (pidof Thread-10)").getBytes("ASCII"));
  
          Log.e("!!", "process stopped!");
  
          os.flush();
  
          os.close();
  
          sh.waitFor();
  
      }
  
      catch(Throwable t){t.printStackTrace();}
  
  }

  But the process doesn't stop. Thread-10 it's the name of ffmpeg transcoding process. Whats wrong ?

• x264 configure linking and building problems

  16 janvier 2014, par Pie

  I am trying to build x264 from source on Ubuntu 32bit in order to convert a sequence of jpg or png images into mp4 video : x264 site, sample images

  The downloaded binaries is able to convert the sequence into an mkv video (or few other formats) when I run this command :

  ./x264dist ~/Dev/x264emp/img/FLYOVER%4d.JPG -o abc.mkv

  x264dist is the renamed name of the binary I download from the site.

  However, when I grab the source and compile with simple configure :

  $ ./configure --enable-shared --enable-static --enable-pic

  platform:      X86
  
  system:        LINUX
  
  cli:           yes
  
  libx264:       internal
  
  shared:        yes
  
  static:        yes
  
  asm:           yes
  
  interlaced:    yes
  
  avs:           avxsynth
  
  lavf:          no
  
  ffms:          no
  
  mp4:           no
  
  gpl:           yes
  
  thread:        posix
  
  opencl:        yes
  
  filters:       crop select_every 
  
  debug:         no
  
  gprof:         no
  
  strip:         no
  
  PIC:           yes
  
  bit depth:     8
  
  chroma format: all

  then $ make. Then I use the binaries to run the exactly same command as above but there is this error :

  ./x264 ~/Dev/x264emp/img/FLYOVER%4d.JPG -o abc.mkv
  
  raw [error]: raw input requires a resolution.
  
  x264 [error]: could not open input file `/home/tmd/Dev/x264emp/img/FLYOVER%4d.JPG' via any method!

  It seems like it can’t read any input at all. But at least I am still able to run --help on that binaries.

  Then I realized that the downloaded binaries is 3.5Mb while my custom compilation results in 1.5Mb binaries.

  So I just want to know what are the build configurations used by the official build, and/or is there any dependency I am missing that leads to this problem.

  The reason I am trying to build myself because I want to port the x264 lib into Javascript using Emscripten. There has been a solution using FFmpeg but it seems like I don’t need the whole video processing library but only a simple H264 codec. So I need to solve the configure/compile/linking problem to port it rightly.

  Possibly similar How to configure X264 build before running make on OS X

• configure : disable direct stripping in OpenBSD

  7 avril 2018, par James Almer

  configure : disable direct stripping in OpenBSD
  It appears strip -o creates new files without preserving permissions
  
  from the source binary, resulting in non executable files.
  Signed-off-by : James Almer <jamrial@gmail.com>
  

  • [DH] configure