Recherche avancée

Médias (1)

Mot : - Tags -/portrait

Autres articles (40)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

  • Submit enhancements and plugins

    13 avril 2011

    If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
    You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.

Sur d’autres sites (9477)

  • Edit audio files on the server with Meteor

    28 décembre 2015, par Mohammed Hussein

    I am building a Meteor application to split uploaded audio files.

    I upload the audio files and store them using GridFS :

    child = Npm.require('child_process');

    var fs = Npm.require('fs');

    storagePath= fs.realpathSync(process.env.PWD+'/audio');

    StaticServer.add('/audio', clipsPath);

    and then using a method I split the audio file using :

    child.exec(command);

    the command is the ffmpeg command used to cut the source audio file and store it on the storagePath.

    The application worked fine locally but when I tried to deploy it to digital ocean I got errors, stating that the file /audio does not exist.
    I use mupx to deploy and the error appears after "verifying deployment".

    Here is the error :

       -----------------------------------STDERR-----------------------------------
       eteor-dev-bundle@0.0.0 No README data
       => Starting meteor app on port:80

       /bundle/bundle/programs/server/node_modules/fibers/future.js:245
                                                       throw(ex);
                                                             ^
       Error: ENOENT, no such file or directory '/bundle/bundle/audio'
           at Object.fs.lstatSync (fs.js:691:18)
           at Object.realpathSync (fs.js:1279:21)
           at server/startup.js:10:20
           at /bundle/bundle/programs/server/boot.js:249:5
       npm WARN package.json meteor-dev-bundle@0.0.0 No description
       npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
       npm WARN package.json meteor-dev-bundle@0.0.0 No README data
       => Starting meteor app on port:80

       /bundle/bundle/programs/server/node_modules/fibers/future.js:245
                                                       throw(ex);
                                                             ^
       Error: ENOENT, no such file or directory '/bundle/bundle/audio'
           at Object.fs.lstatSync (fs.js:691:18)
           at Object.realpathSync (fs.js:1279:21)
           at server/startup.js:10:20
           at /bundle/bundle/programs/server/boot.js:249:5

       => Redeploying previous version of the app

       -----------------------------------STDOUT-----------------------------------

       To see more logs type 'mup logs --tail=50'

       ----------------------------------------------------------------------------

    The main question is how to generate an output file using ffmpeg and store it in a place where I can access it and display it in the browser.

  • doc/examples/muxing : Remove outdated comment

    21 mars 2022, par Andreas Rheinhardt
    doc/examples/muxing : Remove outdated comment
    

    This comment only applies to the scenario in which one uses
    the AVCodecContexts embedded in AVStreams. Yet this code sample
    stopped doing so in 9897d9f4e074cdc6c7f2409885ddefe300f18dc7 ;
    and the last major version bump even removed the public
    AVCodecContexts in AVStreams. So just remove this comment.

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

    • [DH] doc/examples/muxing.c
  • pixfmt : remove misleading and broken documentation

    28 mai 2015, par wm4
    pixfmt : remove misleading and broken documentation
    

    This was probably broken some time ago. The breakage is now part of the
    ABI. For example, we have :

    AV_PIX_FMT_XYZ12BE
    AV_PIX_FMT_NV16
    AV_PIX_FMT_NV20LE

    AV_PIX_FMT_NV20LE is wrong. It has the value 113, but as little-endian
    format it should be even. This must have been quite obvious when these
    formats were added (because of the AV_PIX_FMT_XYZ12BE entry), but
    nobody cared or knew about this.

    The future libavutil major bump will also break this additionally,
    because disabling FF_API_VDPAU will remove an odd number of entries from
    the middle of the enum.

    Signed-off-by : Luca Barbato <lu_zero@gentoo.org>

    • [DH] libavutil/pixfmt.h