Recherche avancée

Médias (91)

Autres articles (30)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

Sur d’autres sites (4150)

  • Still can't install pygame on ubuntu

    1er octobre 2016, par brotheroflogan

    I’ve tried three different ways. The most recent was following instructions here : http://www.pygame.org/wiki/CompileUbuntu

    But when I type in the first line

    sudo apt-get install mercurial python-dev python-numpy ffmpeg \

    I am told that

    E: Package 'ffmpeg' has no installation candidate.

    I continue on with the instructions and I am later told that some of the dependencies are missing (even though those are the ones I had attempted to install moments ago).

    Then when I put in

    sudo python3 setup.py install

    it tells me

    src/_pygame.h:80:20: fatal error: Python.h: No such file or directory
    #include
                       ^
    compilation terminated.
    error: command 'i686-linux-gnu-gcc' failed with exit status 1
  • ffmpeg Error : Pattern type 'glob' was selected but globbing is not support ed by this libavformat build

    14 septembre 2017, par Aryan Naim

    I’m trying to convert group of ".jpg" files acting as individual frames into 1 single mpeg video ".mp4"

    Example parameters i used :

    frame duration  = 2 secs
    frame rate      = 30  fps
    encoder         = libx264 (mpeg)
    input pattern   = "*.jpg"
    output pattern  = video.mp4

    Based on ffmpeg wiki instructions at (https://trac.ffmpeg.org/wiki/Create%20a%20video%20slideshow%20from%20images), I issued this command :

    ffmpeg -framerate 1/2 -pattern_type glob -i "*.jpg" -c:v libx264 -r 30 -pix_fmt yuv420p video.mp4

    But I’m getting this error :

    [image2 @ 049ab120] Pattern type 'glob' was selected but globbing is not
    supported by this libavformat build *.jpg: Function not implemented

    Which probably means the API pattern matching commands for my build/version have changed. By the way this my windows 32bit ffmpeg download build (ffmpeg-20150702-git-03b2b40-win32-static).

    How can I choose a group of files using pattern matching using ffmpeg ?

  • vaapi_h264 : Fix bit offset of slice data.

    2 avril 2016, par Mark Thompson
    vaapi_h264 : Fix bit offset of slice data.
    

    Commit ca2f19b9cc37be509d85f05c8f902860475905f8 modified the meaning of
    H264SliceContext.gb : it is now initialised at the start of the NAL unit
    header, rather than at the start of the slice header. The VAAPI slice
    decoder uses the offset after parsing to determine the offset of the
    slice data in the bitstream, so with the changed meaning we no longer
    need to add the extra byte to account for the NAL unit header because
    it is now included directly.

    Signed-off-by : Derek Buitenhuis <derek.buitenhuis@gmail.com>

    • [DH] libavcodec/vaapi_h264.c