Recherche avancée

Médias (91)

Autres articles (21)

  • MediaSPIP Core : La Configuration

    9 novembre 2010, par

    MediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
    Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...)

  • Ajouter notes et légendes aux images

    7 février 2011, par

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

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

  • FFmpeg 5 C api codec : how many times will EOF be returned by the receiving end ?

    3 février 2024, par Guanyuming He

    Edit : I may have written my questions unclearly at first, so I rewrote them. Sorry if you had found my questions confusing.

    


    I'm new to FFmpeg api programming (I'm using version 5.1) and am learning from the documentation and official examples.

    


    In the documentation page about send/receive encoding and decoding API overview, end of stream situation is discussed briefly :

    


    


    End of stream situations. These require "flushing" (aka draining) the codec, as the codec might buffer multiple frames or packets internally for performance or out of necessity (consider B-frames). This is handled as follows :

    


    


    


    Instead of valid input, send NULL to the avcodec_send_packet() (decoding) or avcodec_send_frame() (encoding) functions. This will enter draining mode.
Call avcodec_receive_frame() (decoding)
or avcodec_receive_packet() (encoding) in a loop until AVERROR_EOF is returned. The functions will not return AVERROR(EAGAIN), unless you forgot to enter draining mode.
Before decoding can be resumed again, the codec has to be reset with avcodec_flush_buffers().

    


    


    As I understand it, when I get AVERROR_EOF, I have reached a special point where I need to drain buffered data from the codec and finally reset the codec with avcodec_flush_buffers(). Without doing it, I cannot continue decoding/encoding.

    


    Is my understanding correct ?

    


    If so, then I have some questions :

    


      

    1. How many times at most can EOF be returned by the receiving end during one complete process, for example, decoding ?

      2. 


    2. If the answer to the first question is infinity, then : If I received an EOF from the receiving end when I already finished sending data (e.g. when after EOF is returned by av_read_frame()), how should I tell if it's really finished ? Here there is no return code only for indicating if the receiving is finished.

      3. 


    3. The data returned from the receive_... functions during draining, should I take them as valid ?

      4. 


    


    I might have found answers to those in the official examples, but I'm not sure if the answer is universally true. I noticed that in some official examples, like in transcode_aac.c, draining is only done for the first EOF reached, and then after the second one is received, it is regarded that there are really nothing left. Any data received during draining is also written to the final output.

    


    Am I correct on interpreting the example ? If so, can I say that the answer to question 1 is once, and the answer to question 3 is yes ?

    


    I appreciate your response and time in advance. :)

    


  • mp4 video file with gps location

    4 mars 2017, par Charles Chay

    I had a understanding that there is no official support to insert gps location metadata into .mp4 files. However, I see a gps location metadata inserted into the video file while I was using my Sony Z2 with geotagging on. ffmpeg was able to detect the metadata after exporting the same file to my laptop. Anyone knows if there a new interface method or api declared for such purpose in andriod ndk ?

  • How to transcode video in android in multiple formats [on hold]

    25 novembre 2016, par adilyousuf

    I am new to android development. I am working on Video Converter(Transcoder), I applied different api (MediaCodec,FFMPEG) But I didn’t understand what to do.
    I didn’t get any special help from android official website and also i didn’t get complete help from google. I also used projects from github but they are very difficult(error) or out of understanding, If someone has work on project like this please tell me what should I learn and do

Navigation