Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP

Autres articles (83)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (13727)

  • 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