Recherche avancée

Médias (29)

Mot : - Tags -/Musique

Autres articles (59)

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

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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (7923)

  • how to make omxh264enc output filler data ?

    8 septembre 2020, par BlueWaterCrystal

    I require filler data from the encoder to artificially raise the bitrate to sustain constant bitrate.

    


    normally x264enc does this but omx264enc doesn't seem to. even though there seems be a value within its code PROP_FILLER_DATA

    


  • Decode h264 packet stream to an ES data file with FFMpeg C API

    27 juillet 2017, par user8335183

    I want to convert the decoded h264 packet data to an elementary stream data file(dump) with FFMpeg’s C API, but I do not know what to do.

    What steps should I take ?

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

    


Navigation