Recherche avancée

Médias (2)

Mot : - Tags -/map

Autres articles (57)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • 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 (...)

Sur d’autres sites (11113)

  • ffmpeg add sound to output video

    5 janvier 2023, par Peter Czask

    I'll like to add a sound from a mp3 file to the output video when inserting an overlay image, my current command is (I'll like to add a sound on the output video at second 11) :

    


    ffmpeg.exe -y -i input.mp4 -i image1.png -filter_complex "[0:v][1:v] overlay=2250:250:enable='between(t,11,17)'" -pix_fmt yuv420p -c:a copy output.mp4


    


    How do I add the sound on that command ? It's possible to do it ?

    


    Thanks

    


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

  • Revision 5171 : La notification des forums pointe vers la page de management

    7 mars 2011, par kent1 — Log

    La notification des forums pointe vers la page de management

Navigation