Recherche avancée

Médias (3)

Mot : - Tags -/image

Autres articles (99)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

Sur d’autres sites (10906)

  • "opaque" pointer in ffmpeg AVFrame

    4 octobre 2016, par R2-D2

    In ffmpeg there is a structure AVFrame describing decoded video or audio data.

    It has a void pointer opaque. The documentation claims it is "for some private data of the user".

    What does this mean ?
    Can it be used to transport any additional data as per-frame metadata ?

  • doc : Mention -dn in the "Stream selection" paragraph.

    27 septembre 2016, par Carl Eugen Hoyos
    doc : Mention -dn in the "Stream selection" paragraph.
    

    There is no "Data options" paragraph.
    Requested-by : ilker tezcan

    • [DH] doc/ffmpeg.texi
  • Chrome "stalling" when streaming mp3 file from nodejs windows only

    8 octobre 2015, par Alan Hollis

    We’ve got a really annoying bug when trying to send mp3 data. We’ve got the following set up.

    Web cam producing aac -> ffmpeg convert to adts -> send to nodejs server -> ffmpeg on server converts adts to mp3 -> mp3 then streamed to browser.

    This works *perfectly" on Linux ( chrome with HTML5 and flash, firefox flash only )

    However on windows the sound just "stalls", no matter what combination we use ( browser/html5/flash ). If however we shutdown the server the sound then immediately starts to play as we expect.

    For some reason on windows based machines it’s as if the sound is being buffered "waiting" for something but we don’t know what that is.

    Any help would be greatly appreciated.

    Relevant code in node

       res.setHeader('Connection', 'Transfer-Encoding');
       res.setHeader('Content-Type', 'audio/mpeg');
       res.setHeader('Transfer-Encoding', 'chunked');
       res.writeHeader('206');

       that.eventEmitter.on('soundData', function (data) {
           debug("Got sound data" + data.cameraId + " " + req.params.camera_id);
           if (req.params.camera_id == data.cameraId) {
               debug("Sending data direct to browser");
               res.write(data.sound);
           }
       });

    Code on browser

          soundManager.setup({
                               url: 'http://dashboard.agricamera.co.uk/themes/agricamv2/swf/soundmanager2.swf',
                               useHTML5Audio: false,
                               onready: function () {
                                   that.log("Sound manager is now ready")
                                   var mySound = soundManager.createSound({
                                       url: src,
                                       autoLoad: true,
                                       autoPlay: true,
                                       stream: true,
                                   });
                               }
                           });