Recherche avancée

Médias (1)

Mot : - Tags -/ticket

Autres articles (25)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

Sur d’autres sites (5011)

  • Is there a way to store packet header information from an incoming h.264 stream ?

    13 septembre 2021, par SOSparachuter1

    The issue : I need to convert an h.264 stream streamed over RTP into MJPEG, but for very convoluted reasons I am required to use the libjpeg-turbo library, not the mjpeg encoder that comes with ffmpeg. So the only thing FFMPEG needs to do is convert the h.264 RTP stream to rawvideo in RGBA and output to a socket where I then manually do the transcoding.

    


    However, libjpeg-turbo only expects complete frames, meaning I need to collect rawvideo packet fragments and somehow synchronize them. Putting incoming raw video fragments into a buffer as they come results in heavily broken images.

    


    Is there some way of saving the header information of the initial h.264 RTP packets ? The command I'm currently using is very straightforward :

    


    -i rtsp :// : -vcodec rawvideo -f rawvideo udp :// :

    


  • doc/filters/histogram : copyedit for grammar

    10 février 2014, par Werner Robitza
    doc/filters/histogram : copyedit for grammar
    

    There were a few grammar and spelling mistakes in this filter
    description. I went through it and corrected them without changing
    the meaning.

    • [DH] doc/filters.texi
  • Syncronize RTSP with computer time

    17 décembre 2012, par Dídac Pérez

    I am successfully using libav to receive the video stream from an RTSP network source. The point is that I need to syncronize my computer's time with the video capturing, meaning that I need to know which datetime of my computer corresponds to the first frame (pts = 0). My API calls are the following ones :

    av_register_all()
    avcodec_register_all()
    avformat_network_init()
    avformat_open_input()
    avformat_find_stream_info()
    av_read_play()
    loop
     av_init_packet()
     av_read_frame()
     [...]
     av_free_packet
    end loop

    With the calls above, I successfully read frames, but I do need to know how can I know the exact absolute datetime that corresponds to the first frame, since it has a pts of 0. Maybe I can use a time() function or GetSystemTime (I am using Windows) between two calls of the above, but do not really know how libav works. I will appreciate your help,

    Kind regards,

    Dídac Pérez