Recherche avancée

Médias (91)

Autres articles (39)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (6086)

  • avformat/rtpdec : explicit timestamp wraparound handling

    8 juin, par Clément Péron
    avformat/rtpdec : explicit timestamp wraparound handling

    Change delta_timestamp to int32_t and add explicit cast to handle
    
RTP timestamp wraparound correctly. This fixes implementation-defined
    
behavior when computing negative timestamp differences due to 32-bit
    
wraparound.
    

    Signed-off-by : Clément Péron <peron.clem@gmail.com>
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavformat/rtpdec.c

  • avcodec/osq : Fix signed integer overflow in update_stats()

    16 juin, par Michael Niedermayer
    avcodec/osq : Fix signed integer overflow in update_stats()

    Fixes : negation of -2147483648 cannot be represented in type 'int' ; cast to an unsigned type to negate this value to itself
    
Fixes : 410109093/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_OSQ_fuzzer-6550900028276736
    

    Note, none of the available osq files uses update_stats(), this change may fix or break
    
files using coding_mode == 2. The code prior looks wrong though
    

    Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavcodec/osq.c

  • ffmpeg : Considers AVPixelFormat as Int ?

    16 mars 2014, par jamie_y

    I would like to use a function ff_load_image.

    program.c

    #include "../ffmpeg/libavfilter/lavfutils.h"
    

    
int main ()
    
{
    
  uint8_t* data;
    

    
  int linesize, width, height, log_ctx;
    

    
  int i = ff_load_image(&amp;data, &amp;linesize, &amp;width, &amp;height, AV_PIX_FMT_RGB24, "blue.jpg", &amp;log_ctx);
    
}

    This compiles, but gives a warning.

    program.c: In function &#39;main&#39;:
    
program.c:11: warning: passing argument 5 of &#39;ff_load_image&#39; makes pointer from integer without a cast
    
../ffmpeg/libavfilter/lavfutils.h:39: note: expected &#39;enum AVPixelFormat *&#39; but argument is of type &#39;int&#39;

    When I run the program, it segment faults. I can't think of any other way to specify a pixel format. Why would ffmpeg think AV_PIX_FMT_RGB8 is an integer ? It's obviously an AVPixelFormat.

Navigation