Recherche avancée

Médias (2)

Mot : - Tags -/plugins

Autres articles (96)

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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (8878)

  • win_utf8_io.c : Comment only.

    22 septembre 2014, par Erik de Castro Lopo
    win_utf8_io.c : Comment only.
    

    Explains why flac is currently incompatible with extended-length paths.

    Patch-from : lvqcl <lvqcl.mail@gmail.com>

    • [DH] src/share/win_utf8_io/win_utf8_io.c
  • avutil/log : added av_log_format_line2 which returns buffer length

    27 avril 2016, par Andreas Weis
    avutil/log : added av_log_format_line2 which returns buffer length
    

    The new function behaves the same as av_log_format_line, but also forwards
    the return value from the underlying snprintf call. This will allow
    callers to accurately determine the size requirements for the line buffer.

    Signed-off-by : Andreas Weis <github@ghulbus-inc.de>
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] doc/APIchanges
    • [DH] libavutil/log.c
    • [DH] libavutil/log.h
    • [DH] libavutil/version.h
  • Reading file metadata in nodejs with ffmetadata and fs returns undefined

    10 novembre 2020, par Citanaf

    I cant seem to get this right. I am attempting to read a file's metadata (title) with ffmetadata via a loop on the folder using fs. I would then like to push those properties into an object array called files. If I place the push method inside the ffmetadata, it throws a "push is not a function" error. If I place the push method outside ffmetadata, but inside readdirSync, the object gets created, but the titles are undefined.

    &#xA;

    I think I'm running into a asynchronous issue or a variable scope issue ? I've place several Console.logs over this and the return from the metadata returns after code that comes well after this section.

    &#xA;

    Any help is appreciated.

    &#xA;

    var path = &#x27;./AudioFiles/&#x27;&#xA;var files = [];&#xA;var fTitle&#xA;&#xA;//Read list of files&#xA;fs.readdirSync(path).forEach((file) => {&#xA;    ffmetadata.read(path &#x2B; file, function(err, data){&#xA;        if (err) console.error("Error reading metadata", err);&#xA;        else {&#xA;            fTitle = data.title&#xA;        }&#xA;    })&#xA;    files.push({name:file.replace(&#x27;.mp3&#x27;,&#x27;&#x27;),title:fTitle})&#xA;})&#xA;

    &#xA;

    This is what I am receiving :

    &#xA;

    files = [{name:"myFile1",title:undefined},{name:"myFile2",title:undefined}...]&#xA;

    &#xA;

    I am expecting the below results :

    &#xA;

    files = [{name:"myFile1",title:"myFile1Title"},{name:"myFile2",title:"myFile2Title"}...]&#xA;

    &#xA;