Recherche avancée

Médias (0)

Mot : - Tags -/performance

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (21)

  • 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

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (4608)

  • Need help on handling MPEG4V1 data

    31 janvier 2021, par Gediminas

    I'm in situation where I need to get a chunk of MPEG4V1 (Microsoft MPEG-4 VKI
Codec V1) data located in the beginning of a packet (that was sent by some DVR unit).

    



    Packet structure looks something like this :

    



      

    • Compressed MPEG4 data.
    • 


    • Long integer - Number of events and tripwires.
    • 


    • Long integer - Number of events.
    • 


    • Event - Event's sequence.
    • 


    • Long integer - Number of tripwires.
    • 


    • Tripwire - Tripwires sequence.
    • 


    • Long integer - Cyclical redundant code (CRC).
    • 


    



    So there is no indication of how to know where does the MPEG4 data ends (Or is there ?),
and from where should I start reading this additional data like "Number of events and tripwires" and etc...

    



    I uploaded two packet's so you could see how the actual data looks like :
recvData1.txt,
recvData2.txt.

    



    I've tried to decode those packets using FFmpeg library with avcodec_decode_video function and by removing byte by byte from the end of my recvData buffer in a hope for any results,
    
but FFmpeg just allways returned with an error messages like this :

    



    


    "[msmpeg4v1 @ 038865a0] invalid startcode",
 "[msmpeg4v1 @ 038865a0] header damaged".

    


    



    I'm not that good specialist on knowing of how does the MPEG4 works from the inside,
but judging by the error messages it's clearly seen that I'm missing some data for decoding at the start of the buffer.

    



    So I'm not sure of what part / kind of MPEG data I'm getting here..
    
Maybe it's some kind of MPEG's "frame" data with it's "end" indication or something ?

    



    I've even compared the start of my recvData buffer to some of MPEG4V1 encoded video files I found on the net "http://www.trekmania.net/clips/video_clips4.htm" to check if the start of my buffer really contains the MPEG data ..and not some kind of DVR vendor specific stuff..

    



    And I noticed that there are about 20bytes of data 
(at the start of my packet data, and in .avi files right after about 180bytes..) 
that looks like some kind of header or something..

    



    Please check this image : "http://ggodis.gamedev.lt/stackOverflow/recvData.jpg"

    



    Maybe someone knows what this part of MPEG4V1 data represents ?

    



    P.S. ..I've checked the CRC values for my received packets and they were correct..

    


  • Need help on handling MPEG4V1 data

    14 septembre 2011, par Gediminas

    I'm in situation where I need to get a chunk of MPEG4V1 (Microsoft MPEG-4 VKI
    Codec V1
    ) data located in the beginning of a packet (that was sent by some DVR unit).

    Packet structure looks something like this :

    • Compressed MPEG4 data.
    • Long integer - Number of events and tripwires.
    • Long integer - Number of events.
    • Event - Event's sequence.
    • Long integer - Number of tripwires.
    • Tripwire - Tripwires sequence.
    • Long integer - Cyclical redundant code (CRC).

    So there is no indication of how to know where does the MPEG4 data ends (Or is there ?),
    and from where should I start reading this additional data like "Number of events and tripwires" and etc...

    I uploaded two packet's so you could see how the actual data looks like :
    recvData1.txt,
    recvData2.txt.

    I've tried to decode those packets using FFmpeg library with avcodec_decode_video function and by removing byte by byte from the end of my recvData buffer in a hope for any results,
    but FFmpeg just allways returned with an error messages like this :

    "[msmpeg4v1 @ 038865a0] invalid startcode",
    "[msmpeg4v1 @ 038865a0] header damaged".

    I'm not that good specialist on knowing of how does the MPEG4 works from the inside,
    but judging by the error messages it's clearly seen that I'm missing some data for decoding at the start of the buffer.

    So I'm not sure of what part / kind of MPEG data I'm getting here..
    Maybe it's some kind of MPEG's "frame" data with it's "end" indication or something ?

    I've even compared the start of my recvData buffer to some of MPEG4V1 encoded video files I found on the net "http://www.trekmania.net/clips/video_clips4.htm" to check if the start of my buffer really contains the MPEG data ..and not some kind of DVR vendor specific stuff..

    And I noticed that there are about 20bytes of data
    (at the start of my packet data, and in .avi files right after about 180bytes..)
    that looks like some kind of header or something..

    Please check this image : "http://ggodis.gamedev.lt/stackOverflow/recvData.jpg"

    Maybe someone knows what this part of MPEG4V1 data represents ?

    P.S. ..I've checked the CRC values for my received packets and they were correct..

  • aacdec : don’t return frames without data

    12 mai 2015, par Andreas Cadhalpun
    aacdec : don’t return frames without data
    

    Since commit 676a395a aac->frame->data is not necessarily allocated at
    the end of aac_decode_frame_int if avctx->channels is 0.

    In this case a bogus frame without any data, but non-zero nb_samples is
    returned.

    Signed-off-by : Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>
    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavcodec/aacdec.c