Recherche avancée

Médias (91)

Autres articles (42)

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

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

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (7743)

  • avfilter/avf_abitscope : Correct range for framerate

    23 mars 2017, par Gyan Doshi
    avfilter/avf_abitscope : Correct range for framerate

    Signed-off-by : Gyan Doshi <gyandoshi@gmail.com>
    
Signed-off-by : Paul B Mahol <onemda@gmail.com> (via IRC)
    • [DH] libavfilter/avf_abitscope.c

  • ffmpeg output file size grows faster than linearly with movie length

    14 janvier 2021, par Jakob Filser

    I'm using ffmpeg to string together some .bmp images into a movie. In total, there are 1001 frames, amounting to 0:40 length. The command I'm using is

    &#xA;

    ffmpeg -f image2 -i render.%05d.bmp -c:v libx264 -s 512:268 render.mp4&#xA;

    &#xA;

    The output file is 33,2 MB large, which is about twice the size of a full HD (about 16 times the pixels !) video of the same length. Apart from the file size being unreasonably large, I realized it grows faster than linearly (can't tell exactly if it is quadratic, exponential etc.) with the number of frames. After 100 frames it is about 1536 KB large (which is already too large), after 500 frames it is already 15104 KB, and after 1001 it finally arrives at 34085 KB.

    &#xA;

    My educated guess would be that for each frame it stores some information about all of the previous frames again, which makes absolutely no sense.

    &#xA;

    What am I doing wrong ? Before you recommend libx265 to me : It turns the entire video green.

    &#xA;

  • lavc/lpc : do not explode when windowing a 1-length array

    21 septembre 2022, par Lynne
    lavc/lpc : do not explode when windowing a 1-length array

    Divided by 0.
    • [DH] libavcodec/lpc.c

Navigation