Recherche avancée

Sur d’autres sites (9312)

• lavc/options : add test for avcodec_copy_context

  4 décembre 2014, par Lukasz Marek

  lavc/options : add test for avcodec_copy_context
  This test doesn’t cover every possible issue with this function.
  
  It covers options management only.
  Signed-off-by : Lukasz Marek <lukasz.m.luki2@gmail.com>
  

  • [DH] libavcodec/Makefile
  • [DH] libavcodec/options.c

• ffmpeg progess bar not giving percent

  3 décembre 2014, par Brett

  Hi im trying to create a java program that shows the percent of a ffmpeg command , Im not sure where i am going wrong.

  Its keeps giving me these results

  run :
  Total duration : 857.44 seconds.
  Progress : 0.85%
  Progress : 1.76%
  Progress : 2.79%
  Progress : 3.93%
  Progress : 5.04%
  Progress : 6.21%
  Progress : 6000.27%
  Progress : 6001.29%
  Progress : 6002.46%
  Progress : 6003.58%
  Progress : 6004.59%
  Progress : 6005.70%
  Progress : 6006.77%
  Progress : 12000.86%
  Progress : 12001.97%
  Progress : 12002.97%
  Progress : 12004.03%
  Progress : 12005.15%
  Progress : 12006.27%
  Progress : 18000.34%
  Progress : 18001.46%
  Progress : 18002.29%
  Progress : 18003.41%
  Progress : 18004.41%
  Progress : 18005.50%
  Progress : 18006.55%
  Progress : 24000.52%
  Progress : 24001.62%
  Progress : 24002.74%
  Progress : 24003.69%
  Progress : 24004.76%
  Progress : 24005.88%
  Progress : 24006.94%
  Progress : 30001.01%
  Progress : 30002.16%
  Progress : 30003.24%
  Progress : 30004.25%
  Progress : 30005.37%
  Progress : 30006.44%
  Progress : 36000.56%
  Progress : 36001.60%
  Progress : 36002.69%
  Progress : 36003.73%
  Progress : 36004.81%
  Progress : 36005.93%
  Progress : 42000.05%
  Progress : 42001.18%
  Progress : 42002.30%
  Progress : 42003.41%
  Progress : 42004.50%
  Progress : 42005.60%
  Progress : 42006.72%
  Progress : 48000.84%
  Progress : 48001.96%
  Progress : 48003.08%
  Progress : 48004.18%
  Progress : 48005.09%
  Progress : 48006.16%
  Progress : 54000.22%
  Progress : 54001.15%
  Progress : 54002.20%
  Progress : 54003.30%
  Progress : 54004.42%
  Progress : 54005.49%
  Progress : 54006.38%
  Progress : 60000.45%
  Progress : 60001.57%
  Progress : 60002.55%
  Progress : 60003.64%
  Progress : 60004.66%
  Progress : 60005.62%
  Progress : 60006.72%
  Progress : 66000.67%
  Progress : 66001.73%
  Progress : 66002.75%
  Progress : 66003.61%
  Progress : 66004.71%
  Progress : 66005.82%
  Progress : 66006.81%
  Progress : 72000.67%
  Progress : 72001.73%
  Progress : 72002.80%
  Progress : 72003.87%
  Progress : 72004.81%
  Progress : 72005.71%
  Progress : 72006.69%
  Progress : 78000.73%
  Progress : 78001.82%
  Progress : 78002.91%
  Progress : 78003.91%
  Progress : 78004.98%
  Progress : 78005.88%
  Progress : 78006.49%
  Progress : 84000.37%
  Progress : 84001.12%
  Progress : 84002.04%
  BUILD SUCCESSFUL (total time : 49 seconds)

  But the file is created , i don’t know why im getting 0.00% any help would be awsome
  ..
  It also complains some imports a not being used here are the imports.

  here is my code

  import java.io.IOException;
  
  import java.util.Scanner;
  
  import static java.util.logging.Level.parse;
  
  import java.util.regex.Pattern;
  
  import javafx.util.Duration;
  
  import static javax.management.Query.lt;
  
  /**
  
   *
  
   * @author brett
  
   */
  
  
  
  public class MashMeUp {
  
  
  
      public static void main(String[] args) throws IOException {
  
          ProcessBuilder pb = new ProcessBuilder("ffmpeg", "-i", "C:\\Users\\brett\\Documents\\Telegraph_Road.mp4", "C:\\Users\\brett\\Documents\\out.mp4");
  
  
  
          // ProcessBuilder pb = new ProcessBuilder(args);  
  
          final Process p = pb.start();
  
  
  
      // create a new thread to get progress from ffmpeg command , override  
  
          // it's run method, and start it!  
  
          new Thread() {
  
              public void run() {
  
  
  
                  Scanner sc = new Scanner(p.getErrorStream());
  
  
  
                  // Find duration  
  
                  Pattern durPattern = Pattern.compile("(?<=Duration: )[^,]*");
  
                  String dur = sc.findWithinHorizon(durPattern, 0);
  
                  if (dur == null) {
  
                      throw new RuntimeException("Could not parse duration.");
  
                  }
  
                  String[] hms = dur.split(":");
  
                  double totalSecs = Integer.parseInt(hms[0]) * 3600
  
                          + Integer.parseInt(hms[1]) * 60
  
                          + Double.parseDouble(hms[2]);
  
                  System.out.println("Total duration: " + totalSecs + " seconds.");
  
  
  
                  // Find time as long as possible.  
  
                  Pattern timePattern = Pattern.compile("(?<=time=)[\\d:.]*");
  
                  // TODO make regex that works with ffmpeg static build  
  
                  String match;
  
                  String[] matchSplit;
  
  while (null != (match = sc.findWithinHorizon(timePattern, 0))) {
  
      matchSplit = match.split(":");
  
      double progress = Double.parseDouble(matchSplit[2]) / totalSecs +  Integer.parseInt(matchSplit[0]) * 3600 + Integer.parseInt(matchSplit[1]) * 60;
  
                      System.out.printf("Progress: %.2f%%%n", progress * 100);
  
                  }
  
              }
  
          }.start();
  
      }
  
  }

• Progress with rtc.io

  12 août 2014, par silvia

  At the end of July, I gave a presentation about WebRTC and rtc.io at the WDCNZ Web Dev Conference in beautiful Wellington, NZ.

  

  Putting that talk together reminded me about how far we have come in the last year both with the progress of WebRTC, its standards and browser implementations, as well as with our own small team at NICTA and our rtc.io WebRTC toolbox.

  

  One of the most exciting opportunities is still under-exploited : the data channel. When I talked about the above slide and pointed out Bananabread, PeerCDN, Copay, PubNub and also later WebTorrent, that’s where I really started to get Web Developers excited about WebRTC. They can totally see the shift in paradigm to peer-to-peer applications away from the Server-based architecture of the current Web.

  Many were also excited to learn more about rtc.io, our own npm nodules based approach to a JavaScript API for WebRTC.

  

  We believe that the World of JavaScript has reached a critical stage where we can no longer code by copy-and-paste of JavaScript snippets from all over the Web universe. We need a more structured module reuse approach to JavaScript. Node with JavaScript on the back end really only motivated this development. However, we’ve needed it for a long time on the front end, too. One big library (jquery anyone ?) that does everything that anyone could ever need on the front-end isn’t going to work any longer with the amount of functionality that we now expect Web applications to support. Just look at the insane growth of npm compared to other module collections :

  

  For those that – like myself – found it difficult to understand how to tap into the sheer power of npm modules as a font end developer, simply use browserify. npm modules are prepared following the CommonJS module definition spec. Browserify works natively with that and “compiles” all the dependencies of a npm modules into a single bundle.js file that you can use on the front end through a script tag as you would in plain HTML. You can learn more about browserify and module definitions and how to use browserify.

  For those of you not quite ready to dive in with browserify we have prepared prepared the rtc module, which exposes the most commonly used packages of rtc.io through an “RTC” object from a browserified JavaScript file. You can also directly download the JavaScript file from GitHub.

  

  So, I hope you enjoy rtc.io and I hope you enjoy my slides and large collection of interesting links inside the deck, and of course : enjoy WebRTC ! Thanks to Damon, JEeff, Cathy, Pete and Nathan – you’re an awesome team !

  On a side note, I was really excited to meet the author of browserify, James Halliday (@substack) at WDCNZ, whose talk on “building your own tools” seemed to take me back to the times where everything was done on the command-line. I think James is using Node and the Web in a way that would appeal to a Linux Kernel developer. Fascinating !!