Recherche avancée

Médias (1)

Mot : - Tags -/illustrator

Autres articles (33)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (4482)

  • Revision bb214efcb9 : Update PATENTS to reflect s/VP8/WebM/g Sync with http://www.webmproject.org/lic

    11 août 2014, par Lou Quillio

    Changed Paths :
     Modify /PATENTS


     Modify /third_party/libwebm/PATENTS.TXT



    Update PATENTS to reflect s/VP8/WebM/g

    Sync with http://www.webmproject.org/license/additional/

    modified : PATENTS
    modified : third_party/libwebm/PATENTS.TXT

    Change-Id : I97fc588589654c83c6cb7e2e2b909f23a370db8a

  • Added : Support for Chapter sub levels.

    5 octobre 2013, par Grandt
    Added : Support for Chapter sub levels.
    

    Rev. 2.53 - 2013-10-05
    * Added : Support for Chapter levels.
    * Added functions :
    * ->subLevel() to indent one level under the current, additional
    chapters are added under that.
    * ->backLevel() to step one level back to the parent of the current
    level.
    * ->rootLevel() to step back to the root of the navMap.
    * ->getCurrentLevel() to get the current level indentation (root = 1).
    * ->setCurrentLevel(int) to set the current level indentation (1 or
    less returns to the root, same as ->rootLevel()).
    * ->buildTOC now reflects this level indentation if present.
    * ePub250 is otherwise compatible to the previous version, and no
    modifications are needed if you don't need this feature.

  • ffmpeg command and args execute successfully with child_process.exec() but not child_process.spawn()

    15 octobre 2013, par Zugwalt

    I am trying to use ffmpeg to add text to a video via the drawtext filter from within node.js in a windows environment.

    I have a command and arguments that work in the command line and when executed using the child_process module's exec function, but it encounters an error when the same arguments are used with the spawn function.

    The below code illustrates the problem :

    var child_process = require('child_process');

    var cmd = 'ffmpeg';

    var args = [ '-i',
                'c:\\path\\to\\my\\inputfile.mp4',
                '-vf',
                'drawtext="fontfile=/Windows/Fonts/arial.ttf:text=\'Hello World\':fontcolor=white@0.6:fontsize=70:x=0:y=40"',
                '-y',
                'c:\\path\\to\\my\\outputfile.mp4' ];

    // Above creates the command line equivalent of:
    // ffmpeg -i c:\path\to\my\inputfile.mp4 -vf drawtext="fontfile=/Windows/Fonts/arial.ttf:text='Hello fluent text':fontcolor=white@0.7:fontsize=70:x=0:y=40" -y c:\path\to\my\outputfile.mp4
    // this works when run from the command line

    var execCmd = cmd+' '+args.join(' ');

    child_process.exec(execCmd, function (error, stdout, stderr) {
           /* ffmpeg runs fine, adding the text to the video */

           var spawn = child_process.spawn(cmd,args);

           spawn.on('close', function (code) {
               /* ffmpeg fails, with standard error (obtained via spawn.stderr) reading:
                  Could not load font ""fontfile=/Windows/Fonts/arial.ttf": impossible to find a matching font
                  Error initializing filter 'drawtext' with args '"fontfile=/Windows/Fonts/arial.ttf:text=Hello fluent text:fontcolor=white@0.6:fontsize=70:x=0:y=40"'
               */
           });
       });

    Based on the error message :

    Could not load font ""fontfile=/Windows/Fonts/arial.ttf" : impossible
    to find a matching font

    And comparing it to giving ffmpeg a bogus font on the command line :

    Could not load font "/Windows/Fonts/bogus.ttf" : impossible to find a
    matching font

    It seems the problem is that when executed from spawn the drawtext argument is incorrectly parsed and "fontfile= is incorrectly making its way into the font's path. This does not happen when the same argument is executed with exec or from the command line. Is there any additional escaping that needs to be done when executing using spawn ?