Recherche avancée

Médias (91)

Autres articles (105)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs

    12 avril 2011, par

    La manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
    Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.

  • Gestion de la ferme

    2 mars 2010, par

    La ferme est gérée dans son ensemble par des "super admins".
    Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
    Dans un premier temps il utilise le plugin "Gestion de mutualisation"

Sur d’autres sites (12572)

  • WebM Decoding Improvements in Google Chrome 6

    10 septembre 2010, par noreply@blogger.com (John Luther)

    Google Chrome 6 for Windows, Mac and Linux was released last week. We want to congratulate the Chrome team and thank them for their contributions to the WebM project.

    Making the web faster is a core goal of Chrome, and we are happy to report that across a set of test clips Chrome 6 decodes VP8 video significantly faster than the developer version that was released at our launch in May. On single-core Intel machines the average improvement is about 20% ; on multicore processors it ranges from 15% (two cores) to 50% (four cores). If you want to try it for yourself, get Chrome 6 and then follow our instructions for playing WebM videos on Youtube.

    We’ve made further decoding speed gains in Chrome 7 dev channel, and are working on better video rendering to further improve the WebM user experience.

  • WebM Decoding Improvements in Google Chrome 6

    10 septembre 2010, par noreply@blogger.com (John Luther)

    Google Chrome 6 for Windows, Mac and Linux was released last week. We want to congratulate the Chrome team and thank them for their contributions to the WebM project.

    Making the web faster is a core goal of Chrome, and we are happy to report that across a set of test clips Chrome 6 decodes VP8 video significantly faster than the developer version that was released at our launch in May. On single-core Intel machines the average improvement is about 20% ; on multicore processors it ranges from 15% (two cores) to 50% (four cores). If you want to try it for yourself, get Chrome 6 and then follow our instructions for playing WebM videos on Youtube.

    We’ve made further decoding speed gains in Chrome 7 dev channel, and are working on better video rendering to further improve the WebM user experience.

  • FATE Under New Management

    2 août 2010, par Multimedia Mike — FATE Server

    At any given time, I have between 20-30 blog posts in some phase of development. Half of them seem to be contemplations regarding the design and future of my original FATE system and are thus ready for the recycle bin at this point. Mans is a man of considerably fewer words, so I thought I would use a few words to describe the new FATE system that he put together.

    Overview
    Here are the distinguishing features that Mans mentioned in his announcement message :

    • Test specs are part of the ffmpeg repo. They are thus properly versioned, and any developer can update them as needed.
    • Support for inexact tests.
    • Parallel testing on multi-core systems.
    • Anyone registered with FATE can add systems.
    • Client side entirely in POSIX shell script and GNU make.
    • Open source backend and web interface.
    • Client and backend entirely decoupled.
    • Anyone can contribute patches.

    Client
    The FATE build/test client source code is contained in tests/fate.sh in the FFmpeg source tree. The script — as the extension implies — is a shell script. It takes a text file full of shell variables, updates source code, configures, builds, and tests. It’s a considerably minor amount of code, especially compared to my original Python code. Part of this is because most of the testing logic has shifted into FFmpeg itself. The build system knows about all the FATE tests and all of the specs are now maintained in the codebase (thanks to all who spearheaded that effort— I think it was Vitor and Mans).

    The client creates a report file which contains a series of lines to be transported to the server. The first line has some information about the configuration and compiler, plus the overall status of the build/test iteration. The second line contains ’./configure’ information. Each of the remaining lines contain information about an individual FATE test, mostly in Base64 format.

    Server
    The server source code lives at http://git.mansr.com/?p=fateweb. It is written in Perl and plugs into a CGI-capable HTTP server. Authentication between the client and the server operates via SSH/SSL. In stark contrast to the original FATE server, there is no database component on the backend. The new system maintains information in a series of flat files.

Navigation