Recherche avancée

Sur d’autres sites (7714)

• Revision 4517 : On permet de donner un logo à une instance : - Dans le privé en utilisant ...

  26 novembre 2010, par kent1 — Log

  On permet de donner un logo à une instance : - Dans le privé en utilisant inc/iconifier - Dans le public avec le plugin Ajaxforms L’autorisation d’iconifier est la même que de modifier Amélioration de la page d’édition de mutualisation dans le privé On donne accès à toutes les infos de l’admin d’une (...)

• A Better Process Runner

  1er janvier 2011, par Multimedia Mike — Python

  I was recently processing a huge corpus of data. It went like this : For each file in a large set, run 'cmdline-tool <file>', capture the output and log results to a database, including whether the tool crashed. I wrote it in Python. I have done this exact type of the thing enough times in Python that I’m starting to notice a pattern.

  Every time I start writing such a program, I always begin with using Python’s commands module because it’s the easiest thing to do. Then I always have to abandon the module when I remember the hard way that whatever ’cmdline-tool’ is, it might run errant and try to execute forever. That’s when I import (rather, copy over) my process runner from FATE, the one that is able to kill a process after it has been running too long. I have used this module enough times that I wonder if I should spin it off into a new Python module.

  Or maybe I’m going about this the wrong way. Perhaps when the data set reaches a certain size, I’m really supposed to throw it on some kind of distributed cluster rather than task it to a Python script (a multithreaded one, to be sure, but one that runs on a single machine). Running the job on a distributed architecture wouldn’t obviate the need for such early termination. But hopefully, such architectures already have that functionality built in. It’s something to research in the new year.

  I guess there are also process limits, enforced by the shell. I don’t think I have ever gotten those to work correctly, though.

• VeriSilicon and WebM Support

  24 janvier 2011, par noreply@blogger.com (John Luther)

  Guest blogger Tomi Jalonen is Director of Product Marketing for Hantro video IP at VeriSilicon

  2011 is shaping up to be an exciting year at VeriSilicon Holdings in terms of WebM support. With the new year upon us, I want to share some updates about the work we are doing at VeriSilicon to move the WebM platform forward.

  VeriSilicon has been a longtime partner of On2/Hantro (Hantro is the video IP brand that Google acquired with On2 Technologies) and we were among the first hardware partners to commit to WebM video when the codec was open-sourced last year. After promoting WebM to the semiconductor industry during 2010, we’re excited that at CES 2011 the first tablet supporting WebM with full 1080p resolution was demonstrated. VeriSilicon licensed the WebM IP to this tablet manufacturer and provided engineering support to bring the technology to the showroom floor.

  In addition to licensing IPs, this year we’ll be taking the WebM experience a step further by taping out several application processor chips—including the WebM video IP for Android phones, xPad, and Google TV—to accelerate the deployment of WebM and HTML5 video playback into the market.

  The entire VeriSilicon team is very excited about the future of WebM. We believe that the availability of high-quality, optimized WebM hardware video IP, combined with other VeriSilicon audio and multimedia IP, will be a key ingredient for semiconductor companies to create competitive consumer products. After the launch of WebM, the interest in hardware-accelerated WebM video has been immense and we will continue working with the WebM Project to enable WebM and VP8 in many more chips in 2011.