Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (74)

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

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

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

Sur d’autres sites (16197)

  • lavd/v4l2 : do not fail when VIDIOC_ENUMSTD returns ENODATA

    18 août 2014, par Andre Wolokita
    lavd/v4l2 : do not fail when VIDIOC_ENUMSTD returns ENODATA
    

    As of September 14 2012, v4l_enumstd() will return ENODATA
    when a device’s std field is set to 0. That is, the device
    does not have a standard format. In order to properly
    handle this case, v4l2_set_parameters should catch the
    ENODATA code and break instead of failing.

    Below is the v4l2-core commit describing this change.

    >>commit a5338190efc7cfa8c99a6856342a77d21c9a05cf
    >>Author : Hans Verkuil <hans.verkuil@cisco.com>
    >>Date : Fri Sep 14 06:45:43 2012 -0300
    >>
    >> [media] v4l2-core : tvnorms may be 0 for a given input, handle that case
    >>
    >> Currently the core code looks at tvnorms to see whether ENUMSTD
    >> or G_PARM should be enabled. This is not a good check for drivers
    >> that support the STD API on one input and the DV Timings API on another.
    >> In that case tvnorms may be 0.
    >> Instead check whether s_std is present (for ENUMSTD) or whether g_std or
    >> current_norm is present for g_parm.
    >> Also, in the enumstd core function return ENODATA if tvnorms is 0,
    >> because in that case the current input does not support the STD API
    >> and ENUMSTD should return ENODATA for that.
    >>
    >> Signed-off-by : Hans Verkuil <hans.verkuil@cisco.com>
    >> Reviewed-by : Sakari Ailus <sakari.ailus@iki.fi>
    >> Signed-off-by : Mauro Carvalho Chehab <mchehab@redhat.com>

    • [DH] libavdevice/v4l2.c
  • avcodec_decode_video2 returns positive number when got_picture_ptr is 0

    22 août 2017, par dafnahaktana

    According to the documentation : here, avcodec_decode_video2 should return 0 if no frame could be decompressed. The got_picture_ptr should also be set to zero if no frame could be decompressed.

    I ran this function on a h264 video and I got positive return value while the got_picture_ptr was set to 0. Maybe that the documentation is not updated ?

  • Libav - how to correctly free memory leaking with av_write_frame

    20 avril 2017, par golstar

    I am using LIBAV on Ubuntu to save user’s video stream(RTP VP8) on server in WebM format.
    The problem is, memory is leaking when using av_write_frame. Memory usage is constantly growing (equally with the webm file size) and is never freed after finishing the video recording. The only way to free the memory(RAM) is deleting the WebM file from the storage (HD) afterwards.

    I have 2 questions :

    1. Is it possible to free the memory consumed by av_write_frame during runtime ? I am freeing the packet.data correctly. Memory usage is not growing when av_write_frame line is commented.
    2. What is the correct way to close the file ? This is what I’m doing (it does not free the memory) :

      av_write_trailer(fctx);
      avcodec_close(vStream->codec);
      avio_close(fctx->pb);
      avformat_free_context(fctx);