Recherche avancée

Médias (91)

Autres articles (10)

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

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

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

Sur d’autres sites (3864)

  • avcodec/h264_refs : Fix and add back trace code removed in e1c5170c638e39a8017827339ac...

    4 janvier 2016, par Michael Niedermayer
    avcodec/h264_refs : Fix and add back trace code removed in e1c5170c638e39a8017827339ac687c5f6ff9b35
    • [DH] libavcodec/h264_refs.c

  • Android FFmpeg ComplexCommand to remove frames from the back of a video

    17 août 2017, par Tix

    Compiled using

    compile ’com.writingminds:FFmpegAndroid:0.3.2’

    Currently i have only managed to come up with a complexcommand that removes duplicate frames, and only start to capture frames from frame 25 onwards of a video like so :

    String[] complexCommand = {"-y", "-i", yourRealPath, "-an", "-framerate", "60", "-vf", "select='gte(n,25)'", "-vsync", "0",  dest.getAbsolutePath()};

    select='gte(n,25)' will return me all frames from frame 25 onwards.

    "-vsync", "0" will remove duplicate frames.

    Now i want to ALSO remove certain number of frames from the back of the video, for e.g. i want to remove the last 20 frames. How do I go about doing that ?

  • How to implement multiple video resolutions on front and back-end

    25 février 2021, par LanGuu

    I need a solution or hint on how should I handle multiple resolutions on front-end and back-end. I have been reading about hls, dash, and mse for last few days but the more information I read, the more lost I am.

    


    Right now I have only a microservice for downscaling video using FFmpeg. The FFmpeg returns mp4 with no hls or dash, 4 video resolutions with no sound, and 2 different audio quality.
On front-end, I use react-player. The hardest part is that I need to merge audio and video, synchronize and handle change quality events.
I have found Media source extensions but it won't work I am not sure, but probably because I am using raw mp4 files.

    


    I would like to ask you a few questions

    


      

    1. It is possible to combine video and audio sources without MSE and still keep video and audio separate

      2. 


    2. Do I need HLS or Dash to use MSE ?

      3. 


    3. What is a difference between progressive download and progressive streaming ?

      4. 


    4. If I have to choose what is better right now hls or dash ? what is much easier to implement ?

      5. 


    


Navigation