Recherche avancée

Médias (2)

Mot : - Tags -/documentation

Autres articles (97)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (10231)

  • Correctly Allocate And Fill Frame In FFmpeg

    14 avril 2022, par Michel Feinstein

    I am filling a Frame with a BGR image for encoding, and I am getting a memory leak. I think I got to the source of the problem but it appears to be a library issue instead. Since FFmpeg is such a mature library, I think I am misusing it and I would like to be instructed on how to do it correctly.

    



    I am allocating a Frame using :

    



    AVFrame *bgrFrame = av_frame_alloc();


    



    And later I allocate the image in the Frame using :

    



    av_image_alloc(bgrFrame->data, bgrFrame->linesize, bgrFrame->width, bgrFrame->height, AV_PIX_FMT_BGR24, 32);


    



    Then I fill the image allocated using :

    



    av_image_fill_pointers(bgrFrame->data, AV_PIX_FMT_BGR24, bgrFrame->height, originalBGRImage.data, bgrFrame->linesize);


    



    Where originalBGRImage is an OpenCV Mat.

    



    And this has a memory leak, apparently, av_image_alloc() allocates memory, and av_image_fill_pointers() also allocates memory, on the same pointers (I can see bgrFrame->data[0] changing between calls).

    



    If I call

    



    av_freep(&bgrFrame->data[0]);


    



    After av_image_alloc(), it's fine, but if I call it after av_image_fill_pointers(), the program crashes, even though bgrFrame->data[0] is not NULL, which I find very curious.

    



    Looking FFmpeg's av_image_alloc() source code, I see it calls av_image_fill_pointers() twice inside it, once allocating a buffer buff....and later in av_image_fill_pointers() source code, data[0] is substituted by the image pointer, which is (I think) the source of the memory leak, since data[0] was holding buf from the previous av_image_alloc() call.

    



    So this brings the final question : What's the correct way of filling a frame with an image ?.

    


  • Correctly Allocate And Fill Frame In FFmpeg

    24 février 2016, par mFeinstein

    I am filling a Frame with a BGR image for encoding, and I am getting a memory leak. I think I got to the source of the problem but it appears to be a library issue instead. Since FFmpeg is such a mature library, I think I am misusing it and I would like to be instructed on how to do it correctly.

    I am allocating a Frame using :

    AVFrame *bgrFrame = av_frame_alloc();

    And later I allocate the image in the Frame using :

    av_image_alloc(bgrFrame->data, bgrFrame->linesize, bgrFrame->width, bgrFrame->height, AV_PIX_FMT_BGR24, 32);

    Then I fill the image allocated using :

    av_image_fill_pointers(bgrFrame->data, AV_PIX_FMT_BGR24, bgrFrame->height, originalBGRImage.data, bgrFrame->linesize);

    Where originalBGRImage is an OpenCV Mat.

    And this has a memory leak, apparently, av_image_alloc() allocates memory, and av_image_fill_pointers() also allocates memory, on the same pointers (I can see bgrFrame->data[0] changing between calls).

    If I call

    av_freep(&bgrFrame->data[0]);

    After av_image_alloc(), it’s fine, but if I call it after av_image_fill_pointers(), the program crashes, even though bgrFrame->data[0] is not NULL, which I find very curious.

    Looking FFmpeg’s av_image_alloc() source code, I see it calls av_image_fill_pointers() twice inside it, once allocating a buffer buff....and later in av_image_fill_pointers() source code, data[0] is substituted by the image pointer, which is (I think) the source of the memory leak, since data[0] was holding buf from the previous av_image_alloc() call.

    So this brings the final question : What’s the correct way of filling a frame with an image ?.

  • avcodec/nvenc : include nvEncodeAPI v7 SDK header

    27 août 2016, par Timo Rothenpieler
    avcodec/nvenc : include nvEncodeAPI v7 SDK header

    As Nvidia has put the most recent Video Codec SDK behind a double
    
registration wall, of which one needs manual approval of a lenghty
    
application, bundling this header saves everyone trying to use NVENC
    
from that headache.
    

    The header is still MIT licensed and thus fine to bundle with ffmpeg.
    

    Not bundling this header would get ffmpeg stuck at SDK v6, which is
    
still freely available, holding back future development of the NVENC
    
encoder.
    • [DH] compat/nvenc/nvEncodeAPI.h
    • [DH] configure
    • [DH] libavcodec/nvenc.h
    • [DH] tests/ref/fate/source

Navigation