Recherche avancée

Médias (1)

Mot : - Tags -/berlin

Autres articles (36)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

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

  • Use ffmpeg from an electron app

    8 février 2017, par Sharath Huddar

    I intend to build a basic video editor desktop app. I have built a working prototype in python ( using kivy ). In this prototype I directly call the command line ffmpeg tool.

    How can I incorporate ffmpeg into my electron app ?

  • How can I bundle a precompiled binary with electron

    13 avril 2017, par UltrasoundJelly

    I am trying to include a precompiled binary with an electron app. I began with electron quick start app and modified my renderer.js file to include this code that is triggered when a file is dropped on the body :

    spawn = require( 'child_process' ).spawn,
           ffmpeg = spawn( 'node_modules/.bin/ffmpeg', ['-i',clips[0],'-an','-q:v','1','-vcodec','libx264','-y','-pix_fmt','yuv420p','-vf','setsar=1,scale=trunc(iw/2)*2:trunc(ih/2)*2,crop=in_w:in_h-50:0:50', '/tmp/out21321.mp4']);

      ffmpeg.stdout.on( 'data', data => {
            console.log( `stdout: ${data}` );
           });
      ffmpeg.stderr.on( 'data', data => {
       console.log( `stderr: ${data}` );
           });

    I have placed my precompiled ffmpeg binary in node_modules/.bin/. Everything works great in the dev panel, but when I use electron-packager to set up the app, it throws a spawn error ENOENT to the console when triggered. I did find a very similar question on SO, but the question doesn’t seem to be definitively answered. The npm page on electron-packager does show that they can be bundled, but I cannot find any documentation on how to do so.

  • Supporting HEVC/H.265 videos in Electron

    1er mars 2021, par Elmo

    Chrome/Electron don't normally support H.265 videos. I want the user to be able to play .mov files recorded by Apple devices in my app. How can I do this ?

    


    Possible approaches :

    


      

    1. Use ffmpeg to transcode to H.264 in real-time, which will be resource intensive (not ideal)
    2. 


    3. Use WebAssembly to render the video in a <canvas></canvas> tag (not ideal)
    4. &#xA;

    5. Fork and manually add H.265 codec support to Chrome/Electron (overkill)
    6. &#xA;

    7. Use a native module that renders the video in a <canvas></canvas> or BrowserView
    8. &#xA;

    &#xA;