Recherche avancée

Médias (16)

Mot : - Tags -/mp3

Autres articles (110)

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

  • Automated installation script of MediaSPIP

    25 avril 2011, par

    To overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
    You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
    The documentation of the use of this installation script is available here.
    The code of this (...)

  • Soumettre bugs et patchs

    10 avril 2011

    Un logiciel n’est malheureusement jamais parfait...
    Si vous pensez avoir mis la main sur un bug, reportez le dans notre système de tickets en prenant bien soin de nous remonter certaines informations pertinentes : le type de navigateur et sa version exacte avec lequel vous avez l’anomalie ; une explication la plus précise possible du problème rencontré ; si possibles les étapes pour reproduire le problème ; un lien vers le site / la page en question ;
    Si vous pensez avoir résolu vous même le bug (...)

Sur d’autres sites (11375)

  • avformat/dashdec : fix pointer being freed was not allocated

    16 septembre 2019, par vectronic
    avformat/dashdec : fix pointer being freed was not allocated
    

    prevent attempt to call xmlFree if val was not allocated
    fixes : 8135

    Reviewed-by : Steven Liu <lq@onvideo.cn>
    Signed-off-by : vectronic <hello.vectronic@gmail.com>

    • [DH] libavformat/dashdec.c
  • FFMPEG HTTP protocol closing after first packet

    27 août 2019, par rusty

    I’m trying to send a live video stream from my webcam to FFMPEG via the HTTP protocol. However after the first packet is sent FFMPEG closes, but does indeed output a fully playable video. As my intention.

    After going over the documentation for the protocol I thought mulitiple_requests would stop this behavior which it did not. After searching online for a few hours I can not find an example specific to my scenario. i.e. receiving a network stream over HTTP.

    Code running on the client-side :

    var xhttp=new XMLHttpRequest;

    if (navigator.mediaDevices) {

       var constraints = { audio: true, video: true };

       navigator.mediaDevices.getUserMedia(constraints)
         .then(function(stream) {
           var mediaRecorder = new MediaRecorder(stream);
           m = mediaRecorder;
           m.start();
           m.ondataavailable=e=>{
             xhttp.open("POST","http://localhost:8080");
             xhttp.send(e.data);
           }
           setInterval(function(){
             m.requestData();
           },2000);
         }).catch(function(error) {
           console.log(error.message);
         });
    }

    The FFMPEG command I have tried thus far :

    ffmpeg -listen 1 -multiple_requests -i http://localhost:8080 file.webm

    Maybe this is not possible with FFMPEG ? If this is the case then it appears the only solution would be to put this command in a loop and keep appending to the output.

  • .travis.yml : Generate and validate html documentation.

    30 juillet 2019, par Ralph Giles
    .travis.yml : Generate and validate html documentation.
    

    Install Doxygen when running on the linux environment to test
    generation of the API documentation.

    Run the included static html documentation as well as the
    generated API documentation through xmllint to verify
    it conforms to the declared DTD. Since this this will be very
    slow or fail relying on network resources, also install
    the w3c-sgml library so the xhtml1 DTDs are available locally.

    We're checking the source files, not build results in the
    particular environment, so it's fine to run this check
    on only a subset of builds.

    Don't validate on CMake builds since they're not currently
    generating API documentation even when Doxygen is available.

    • [DH] .travis.yml