Recherche avancée

Médias (91)

Autres articles (43)

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

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

Sur d’autres sites (7386)

  • Revert "avcodec/mediacodecdec : wait on first frame after input buffers are full"

    18 juin 2018, par Aman Gupta
    Revert "avcodec/mediacodecdec : wait on first frame after input buffers are full"

    @xyz reported a regression on his Sony Xperia Z3 Tablet Compact where
    
playback would intermittently fail to start, essentially deadlocking in
    
the decoder. Bisecting narrowed down the issue to this commit, which was
    
meant as an optimization but is not necessary.
    

    This reverts commit a75bb5496ac6e7e194f1c6fd3b87f02a52e74adb.
    

    Signed-off-by : Aman Gupta <aman@tmm1.net>
    • [DH] libavcodec/mediacodecdec_common.c
    • [DH] libavcodec/mediacodecdec_common.h

  • parseutils : accept only full "ms" suffix

    3 mars 2018, par Rostislav Pehlivanov
    parseutils : accept only full "ms" suffix

    The commit which added those was pushed prematurely before anyone could object
    
to illogical suffixes like just m for milliseconds. Without this, we'd be locked
    
into never being able to implement the "m" suffix for minutes.
    

    Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>
    • [DH] libavutil/parseutils.c

  • How to get rid of errors "jitter buffer full" in ffmpeg ?

    31 janvier 2021, par jidckii

    How to get rid of errors jitter buffer full ?
    &#xA;I use ffmpeg from one of the latest snapshots.
    &#xA;ffmpeg version N-90078-gf611fef Copyright (c) 2000-2018 the FFmpeg developers

    &#xA;&#xA;

    The problem is that from the camera on rtsp there is such a stream :
    &#xA;http://ibb.co/fmckCc
    &#xA;It is not possible to fix this from the camera side.

    &#xA;&#xA;

    I accept it like this :

    &#xA;&#xA;

    ffmpeg \&#xA;-strict experimental \&#xA;-fflags &#x2B; genpts \&#xA;-fflags &#x2B; latm \&#xA;-seek2any 1 \&#xA;-avoid_negative_ts &#x2B; make_zero \&#xA;-max_delay 5000000 \&#xA;-rtsp_transport udp \&#xA;-i rtsp: // admin: @ 192.168.87.21: 554/0? .sdp \&#xA;-map 0 \&#xA;-r 15 \&#xA;-c: v copy \&#xA;-an \&#xA;-f mpegts udp: //239.0.0.1: 1234? ttl = 1? pkt_size = 1316&#xA;

    &#xA;&#xA;

    I later start to get errors from time to time

    &#xA;&#xA;

    [rtsp @ 0x154d180] jitter buffer full&#xA;[rtsp @ 0x154d180] RTP: missed 1 packets&#xA;[rtsp @ 0x154d180] jitter buffer full&#xA;[rtsp @ 0x154d180] RTP: missed 1 packets&#xA;[rtsp @ 0x154d180] jitter buffer full&#xA;[rtsp @ 0x154d180] RTP: missed 2 packets&#xA;[rtsp @ 0x154d180] jitter buffer full&#xA;[rtsp @ 0x154d180] RTP: missed 4 packets&#xA;

    &#xA;&#xA;

    because of this the picture crumbles.

    &#xA;&#xA;

    I increased the udp buffer in the linux kernel settings :

    &#xA;&#xA;

    net.core.rmem_max = 16777216&#xA;net.core.wmem_max = 16777216&#xA;net.ipv4.udp_mem = 8388608 12582912 16777216&#xA;net.ipv4.tcp_rmem = 4096 87380 8388608&#xA;net.ipv4.tcp_wmem = 4096 65536 8388608&#xA;

    &#xA;&#xA;

    It did not solve my problem.
    &#xA;Tell me, how can you deal with such errors ?

    &#xA;

Navigation