Recherche avancée

Sur d’autres sites (10221)

• 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 !!

• Ffmpeg set duration using node-fluent-ffmpeg

  23 mai 2013, par Vprnl

  I'm really new to the world of ffmpeg so please excuses me if this is a stupid queston.

  I'm using the module Node-fluent-ffmpeg to stream a movie and convert it from avi to webm.
  So far so good (it plays the video), but I'm having trouble parsing the duration to the player. My ultimate goal is to be able to skip ahead in the movie. But first the player needs to know how long the video is.

  my code is as followed :

  var stat = fs.statSync(movie);
  
  
  
  var start = 0;
  
  var end = 0;
  
  var range = req.header('Range');
  
  if (range != null) {
  
  start = parseInt(range.slice(range.indexOf('bytes=')+6,
  
    range.indexOf('-')));
  
  end = parseInt(range.slice(range.indexOf('-')+1,
  
    range.length));
  
  }
  
  if (isNaN(end) || end == 0) end = stat.size-1;
  
  if (start > end) return;
  
  
  
  res.writeHead(206, { // NOTE: a partial http response
  
      'Connection':'close',
  
      'Content-Type':'video/webm',
  
      'Content-Length':end - start,
  
      'Content-Range':'bytes '+start+'-'+end+'/'+stat.size,
  
      'Transfer-Encoding':'chunked'
  
  });
  
  
  
  var  proc = new ffmpeg({ source: movie, nolog: true, priority: 1, timeout:15000})
  
      .toFormat('webm')
  
      .withVideoBitrate('1024k')
  
      .addOptions(['-probesize 900000', '-analyzeduration 0', '-bufsize 14000'])
  
      .writeToStream(res, function(retcode, error){
  
      if (!error){
  
          console.log('file has been converted succesfully',retcode);
  
      }else{
  
          console.log('file conversion error',error);
  
      }
  
  });

  I tried to set the header with a start and a end based on this article : http://delog.wordpress.com/2011/04/25/stream-webm-file-to-chrome-using-node-js/

  I also looked in the FFmpeg documentation and found -f duration and -ss.
  But I don't quite know how to convert the byte range to seconds.

  I feel like I'm pretty close to a solution but my inexperience with the subject matter prohibits me from getting it to work. If I'm unclear in any way please let me know. (I have a tendency of explaining things fuzzy.)

  Thanks in advance !

• Anomalie #3095 : Le filtre |image_renforcement ne préserve pas la transparence des images

  18 juillet 2014, par tcharlss ಠ_ಠ

  Il s’agit d’un LAMP local installé sur Ubuntu 14.04.
  La librairie GD (libgd3 2.1.0-3) ainsi que le module GD pour PHP5 (php5-gd 5.5.9) sont bien installés.
  Testé avec des images PNG en couleur et en noir et blanc : même résultat.
  Dans « Génération de miniatures des images », j’ai essayé toutes les méthodes : GD1, GD2, Convert et Netpbm.

  S’il s’agit bien d’une librairie manquante sur le serveur, il me semble que le filtre ne devrait rien faire au lieu d’aplatir l’image.