Recherche avancée

Médias (3)

Mot : - Tags -/pdf

Autres articles (41)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (7263)

  • Revision 87599 : $GLOBALS[’visiteur_session’] au lieu de global $auteur_session ; et ...

    22 février 2015, par kent1@… — Log

    $GLOBALSvisiteur_session ? au lieu de global $auteur_session ; et $auteur_session
    Indentation / Formatage

  • ffmpeg rtp streaming errors : RTP : dropping old packet received too late

    2 février 2019, par Андрей_RnD

    I start video transfer by means of ffmpeg like this :

    ffmpeg -f video4linux2 -i /dev/video0 -vcodec libx264 -preset ultrafast -crf 20 -tune zerolatency -s 800x600 -r 25 -b:v 0.9M -sdp_file video.sdp -f rtp rtp://192.168.10.24:5010    

    I reproduce this way :

    ffplay -protocol_whitelist file,udp,rtp video.sdp    

    Everything works just fine. Then I interrupt transmission and after a couple of seconds I resume. ffplay does not immediately start to reproduce but errors occur :

    ....
    [sdp @ 0x6ebf80] RTP: dropping old packet received too lateB f=1/1
       Last message repeated 14 times
    [sdp @ 0x6ebf80] RTP: dropping old packet received too lateB f=1/1
       Last message repeated 33 times
    [sdp @ 0x6ebf80] RTP: dropping old packet received too lateB f=1/1
       Last message repeated 41 times
    [sdp @ 0x6ebf80] RTP: dropping old packet received too lateB f=1/1
       Last message repeated 49 times
    [sdp @ 0x6ebf80] RTP: dropping old packet received too lateB f=1/1
       Last message repeated 33 times
    [sdp @ 0x6ebf80] RTP: dropping old packet received too lateB f=1/1
       Last message repeated 27 times
    [sdp @ 0x6ebf80] RTP: dropping old packet received too lateB f=1/1
       Last message repeated 14 times
    [sdp @ 0x6ebf80] RTP: dropping old packet received too lateB f=1/1
       Last message repeated 48 times
    [sdp @ 0x6ebf80] RTP: dropping old packet received too lateB f=1/1
       Last message repeated 34 times
    ......    

    After a some time, playback is restored, but it is too long. Is there a way to eliminate or minimize the occurrence of errors of this nature when the incoming stream is suspended, can options or something else ? Read the manual ffmpeg nothing worthwhile about this did not naryl .... ((((

  • avformat/matroskaenc : Improve BlockAdditions

    20 novembre 2019, par Andreas Rheinhardt
    avformat/matroskaenc : Improve BlockAdditions
    

    8ffcc826 added support for muxing BlockAdditions with BlockAddID equal
    to one. The restriction to BlockAddID == 1 probably resulted from
    a limitation to what was needed ; yet over time this led to three
    occurences of "(side_data_size && additional_id == 1)". This commit
    changes this by setting side_data_size to 0 if additional_id != 1.

    It also stops hardcoding 1 for the value of BlockAddID to write ;
    but it still upholds the requirement that it is 1. See below.

    Despite BlockAddId actually having a default value of 1, it is still
    written, because until very recently (namely dbc50f8a) our demuxer
    used a wrong default value of 0.

    Furthermore, use put_ebml_binary() to write the BlockAdditional element.

    (The Matroska specifications have evolved and now the BlockAddID 1 is
    reserved for the codec (as described in the codec's codec mapping),
    BlockMore elements with BlockAddID > 1 are now of a more
    codec-independent nature and require a BlockAdditionalMapping in the
    track's TrackEntry. Given that this muxer does not support writing said
    BlockAdditionalMapping yet (actually, none have been defined yet), we
    have to uphold the requirement that BlockAddID == 1.)

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavformat/matroskaenc.c