Recherche avancée

Médias (91)

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

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

Sur d’autres sites (6681)

  • 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

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

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


    3. 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.
    4. 


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


    


    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. :)