Recherche avancée

Médias (1)

Mot : - Tags -/book

Autres articles (103)

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

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

  • Formulaire personnalisable

    21 juin 2013, par

    Cette page présente les champs disponibles dans le formulaire de publication d’un média et il indique les différents champs qu’on peut ajouter. Formulaire de création d’un Media
    Dans le cas d’un document de type média, les champs proposés par défaut sont : Texte Activer/Désactiver le forum ( on peut désactiver l’invite au commentaire pour chaque article ) Licence Ajout/suppression d’auteurs Tags
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire. (...)

Sur d’autres sites (3590)

  • How to make a video file from H264 encoded data [on hold]

    4 décembre 2014, par vominhtien961476

    I received H264 encoded data from Camera (frame by frame). Then I want to make a video File (AVI, MP4,...). So Is there any simple way to put directly these data to container whithout decode the h264 data -> convert to Bitmap -> encode again to make a video file as I did.

  • FFmpeg API : parse raw movie packet data into AVPacket

    7 novembre 2011, par Andrea3000

    If you have a movie file and you need to extract frame (packet) from it, it's simply a matter of writing :

    avformat_open_input(AVFormatContext **ps, const char *filename, AVInputFormat *fmt, AVDictionary **options);
    

    
...
    

    
AVPacket packet;
    
av_read_frame(formatContext, &packet);

    But what if I don't have the movie file but only unparsed, raw packet data ? These raw packet data are the same as the raw data contained into the movie file but I don't access them throught avformat_open_input and therefore I can't use av_read_frame so FFmpeg doesn't parse them.

    How can I parse this raw data in order to build the corresponding AVPacket ?
    I need to obtain an AVPacket identical to the ones provided by av_read_frame.

  • How do I pre-allocate the memory for libavcodec to write decoded frame data ?

    18 décembre 2018, par codemonkey

    I am trying to decode a video with libav by following the demo code : here

    I need to be able to control where the frame data in pFrame->data[0] is stored. I have tried setting pFrame->data to my own buffer as follows :

    // Determine required buffer size and allocate buffer 
    
int numBytes = av_image_get_buffer_size(pixFmt, width, height, 1); 
    
(uint8_t*) dataBuff = (uint8_t*) malloc (numBytes * sizeof(uint8_t)); 
    

    
// Assign buffer to image planes in pFrame
    
av_image_fill_arrays(frame->data, frame->linesize, dataBuff, pixFmt, width,
    
height, 1);

    While this does set pFrame->data to be dataBuff (if I print their addresses, they are the same), this call ret = avcodec_receive_frame(pCodecContext, pFrame) to receive the decoded data always writes the data to a different address. It seems to manage its own memory somewhere in the underlying API and ignores the dataBuff that I assigned to pFrame right before.

    So I’m stuck—how can I tell libav to write decoded frame data to memory that I pre-allocate ? I’ve seen people ask similar questions online and in the libav forum but haven’t been able to find an answer.

    Many thanks 

Navigation