Recherche avancée

Sur d’autres sites (5310)

• Executing process on cmd, does not process

  2 août 2012, par Z Jackobovski

  I am running ffmpeg from Java. Using it to convert flv files to mp3.

  When I run the code below, ffmpeg starts, creates a new file (the .mp3 one) but runs at 0% of CPU. When I stop the JAVA app (from netbeans) ffmpeg remains open and goes from 0% to 99% per Windows task manager (CTRL-ALT-DEL). Another weird thing is going on. The output from ffmpeg is not being printed.

  The thread is starting but for some reason java is not giving it any time to do its processing.

  Any suggestions on how to fix this ? Thanks.

  public class ConverterThread extends Thread {
  
  
  
   String fileToConvert;
  
   String fileToCreate;
  
   GetSong getSong;
  
  
  
  
  
  
  
  public ConverterThread(String downloadLocationOnDisk, GetSong getSong) {
  
     this.fileToConvert = downloadLocationOnDisk;
  
     this.getSong = getSong;
  
  }
  
  
  
  
  
  public void run(){
  
      try {
  
          Thread cur=Thread.currentThread();
  
          cur.setPriority(Thread.MAX_PRIORITY);
  
  
  
             String downloadLocationOnDisk = fileToConvert;
  
  
  
              if(downloadLocationOnDisk.contains(".flv"))
  
                  fileToCreate = downloadLocationOnDisk.replace(".flv", ".mp3");
  
  
  
              if(downloadLocationOnDisk.contains(".m4a"))
  
                  fileToCreate = downloadLocationOnDisk.replace(".m4a", ".mp3");
  
  
  
  
  
  
  
              String cmdLine =  "ffmpeg/bin/ffmpeg -i \"" + fileToConvert + "\" \"" + fileToCreate +"\""; 
  
  
  
              System.err.println(cmdLine);
  
  
  
               // run the Unix "ps -ef" command
  
               // using the Runtime exec method:
  
               Process p = Runtime.getRuntime().exec(cmdLine);
  
  
  
  
  
               BufferedReader stdInput = new BufferedReader(new 
  
                    InputStreamReader(p.getInputStream()));
  
  
  
               BufferedReader stdError = new BufferedReader(new 
  
                    InputStreamReader(p.getErrorStream()));
  
  
  
               String s;
  
  
  
               // read the output from the command
  
               while ((s = stdInput.readLine()) != null) {
  
                   System.out.println(s);
  
               }
  
  
  
               // read any errors from the attempted command
  
               System.out.println("Here is the standard error of the command (if any):\n");
  
               while ((s = stdError.readLine()) != null) {
  
                   System.out.println(s);
  
               }
  
  
  
      } catch (IOException ex) {
  
          Logger.getLogger(ConverterThread.class.getName()).log(Level.SEVERE, null, ex);
  
      }

• ffmpeg crashing on my ec2 linux

  19 décembre 2016, par Alex Bollbach

  I have a node script that has the line :

  execSync('ffmpeg -loglevel panic -i ${path} -acodec copy -f segment -segment_time 10 -vcodec copy -reset_timestamps 1 -map 0 ./tmp/%d.ts');

  Basically, I’m splitting a given video into 10 second segments. This works on my development machine where I have ffmpeg installed :

  However, when I push the code to my ec2 instance (running the linux AMI), I get this crash :

  Error: Command failed: ffmpeg -loglevel panic -i ../test11.mp4 -acodec copy -f segment -segment_time 10 -vcodec copy -reset_timestamps 1 -map 0 ./tmp/%d.ts

  I have checked that all the files and directories exist and are organized correctly in both cases. The only thing I’ve deduced is that the ffmpeg versions vary between machines, so :

  (developement-Machine)$ ffmpeg -version

  (developement-Machine)$ ffmpeg version 3.0.2 Copyright (c) 2000-2016 the FFmpeg developers

  (ec2)$ ffmpeg -version

  (ec2)$ ffmpeg version N-61041-g52a2138

  Is it the case that the ffmpeg version issues are the culprit here and if so how can I get them in sync ? Locally I simply used Homebrew to install ffmpeg. On the ec2, I’ve used YUM as a package manager to install node and npm before but it isn’t trivial to install ffmpeg. I’ve tried to wget the static builds on ffmpeg sites but after un-taring them I get a directory of directories and I’m not sure how to proceed. The original ffmpeg I installed on my ec2 was here (http://ffmpeg.gusari.org/static/64bit/ffmpeg.static.64bit.2014-02-16.tar.gz)

  Either way I am making no progress and I could spend the next 6 hours figuring out what is going on in my linux shell. So I realize this question is a bit unfocused but is the crash likely an ffmpeg version ? and if so, how can I install the local version I have of ffmpeg on my production ec2 server ?

• "Automatic" switchable graphics on desktop, is there a way to disable them ?

  14 août 2021, par Hab-Land0

  Recently, I've updated my graphic drivers for a new system I built, a mix between an amd apu and an nvidia quadro. But I stumbled upon a rare problem, every time I tried to use OpenCL acceleration on ffmpeg for libx264 encoding, ffmpeg notifies me with the next line :

  


  [libx264 @ 0000028149222780] OpenCL acceleration disabled, switchable graphics detected


  


  When searching this line on ffmpeg's code, apparently occurs when the "main OpenCL driver" (if you can call it that) is redirected in such a way that tries to use both devices (Code).

  


  My obvious next step was to search everything I could around this "switchable graphics", but almost all the tutorials on websites told me that I should search around the driver's settings, but literally either Radeon Software or Nvidia's control panel don't display any option about it (It is worth to say that almost all of the tutorials refer to laptops with dedicated graphics and were very outdated).

  


  Another way I use OpenCL is for vapoursynth's filters, such as KNLMeansCL. And, when I make use of this filter, task manager detects that both AMD's APU and Nvidia's gpu are being used simultaneously (I guess that's how the switchable graphics actually works, and partially complementing why x264 OpenCL doesn't work).

  


  My main complain with this is that I attempt to use AMD as a display driver and let Nvidia do the hard work, and I actually was able to do that before updating my drivers. And, talking about the "updates" more in-depth, I updated nvidia's from "462.59" to "471.11" and, unfortunately, I can't remember what versions were my AMD drivers.

  


  Edit : the only way I can make full use of NVIDIA's card is by using it as my main display, but that also apparently disables AMD's igpu, I am not sure if its even able to be used on small tasks (like those that were previously mentioned)