Recherche avancée

Médias (91)

Autres articles (43)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • 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

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

Sur d’autres sites (8229)

  • 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 ?.

  • Evolution #3450 : déporter apple-touch-icon.png et autres variantes vers le plugin favicon

    5 février 2021, par RastaPopoulos ♥

    @erational j’avais des améliorations à proposer dans un ticket, et justement je posais la question à la fin, que ça devrait revenir dans la communauté maintenant, vu qu’à priori c’était parce qu’à l’époque yavait pas Git :
    https://github.com/tetue/favicon/issues/1

    M’est-avis qu’on devrait le recopier chez nous pour pouvoir l’améliorer ici.

Navigation