Recherche avancée

Médias (0)

Mot : - Tags -/objet éditorial

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (111)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

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

Sur d’autres sites (14321)

  • ffmpeg won't execute properly in google app engine standard nodejs

    3 septembre 2019, par tommyc38

    I have tried for three full days to get GAE (standard - nodejs) to run a simple video transcoder from MOV to MP4 using ffmpeg. I have tried using ffluent-ffmpeg, kicking off a child process (e.g. spawn), and nothing works. As soon as it hits the call to the executable it always errors. I have confirmed ffmpeg is installed and even tried using ffmpeg-static. Moreover, I have it working on my local machine with no problems (using all of the aforementioned ways).

    I have also tried logging the errors and nothing is really all that helpful. I can see its working through any installed package including ffmpeg (system package).

    Below is the pseudo code...step three is where the problem occurs.

    1. Send file name to GAE endpoint
    2. Download the file from google cloud storage to a temp file
    3. Transcode using ffmpeg
    4. Upload temp file to google cloud storage
    5. Remove old google cloud storage file
    6. Remove temp file

    The file I am using to test is 6MB...a 5 second video I took on my iPhone. Thank you in advance.

    UPDATE : I successfully deployed the exact same code to Node Flex environment and everything works great. I wasn’t able to get any errors in the standard environment that directed me where to look but my guess is it has something to do with how it stores the file I pipe into FFMPEG on GAE Node Standard. The docs say its a virtual file system that uses RAM. I’d love to hear if anybody managed to get it working in the standard environment.

  • Revision 93a0189936 : Use 8 threads by default for VP9 encodes BUG=https://code.google.com/p/webm/iss

    4 mars 2015, par Frank Galligan

    Changed Paths :
     Modify /vp9/vp9_cx_iface.c



    Use 8 threads by default for VP9 encodes

    BUG=https://code.google.com/p/webm/issues/detail?id=964

    Change-Id : I70679d0f139b8e0962f7e19eb56b34060953e9b0

  • How convert video to mp4 before upload to Google Storage ?

    6 février 2018, par Sofiia Vynnytska

    Currently, I have an API which uploads files to Google Storage. If user uploads video it should be converted to mp4. I took a look at FFMEPG and Java wrapper around the FFmpeg , but I need to convert video directly from InputStream without writing into a disk. Is there any solution to convert InputStream into mp4 ?

Navigation