Recherche avancée

Médias (91)

Autres articles (35)

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

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

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

Sur d’autres sites (4241)

  • swscale/cms,graph,lut3d : Use ff_-prefix, don't export internal functions

    8 janvier, par Andreas Rheinhardt
    swscale/cms,graph,lut3d : Use ff_-prefix, don't export internal functions

    Symbols with the sws_* prefix are exported.
    

    Reviewed-by : Alexander Strasser <eclipse7@gmx.net>
    
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
    • [DH] libswscale/cms.c
    • [DH] libswscale/cms.h
    • [DH] libswscale/graph.c
    • [DH] libswscale/graph.h
    • [DH] libswscale/lut3d.c
    • [DH] libswscale/lut3d.h
    • [DH] libswscale/swscale.c
    • [DH] libswscale/utils.c

  • avcodec/alsdec : Set channels from data after data is set

    18 mars 2022, par Michael Niedermayer
    avcodec/alsdec : Set channels from data after data is set

    Fixes : out of array write
    
Fixes : 45624/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_ALS_fuzzer-6473487382872064
    
Fixes : 45626/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_ALS_fuzzer-4874997192065024
    

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

  • How to get raw frame data from AVFrame.data[] and AVFrame.linesize[] without specifying the pixel format ?

    25 janvier 2016, par vivienlwt

    I get the general idea that the frame.data[] is interpreted depending on which pixel format is the video (RGB or YUV). But is there any general way to get all the pixel data from the frame ? I just want to compute the hash of the frame data, without interpret it to display the image.

    According to AVFrame.h :

    uint8_t* AVFrame::data[AV_NUM_DATA_POINTERS]

    pointer to the picture/channel planes.

    int AVFrame::linesize[AV_NUM_DATA_POINTERS]

    For video, size in bytes of each picture line.

    Does this mean that if I just extract from data[i] for linesize[i] bytes then I get the full pixel information about the frame ?

Navigation