Recherche avancée

Médias (0)

Mot : - Tags -/masques

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

Autres articles (61)

  • Soumettre améliorations et plugins supplémentaires

    10 avril 2011

    Si vous avez développé une nouvelle extension permettant d’ajouter une ou plusieurs fonctionnalités utiles à MediaSPIP, faites le nous savoir et son intégration dans la distribution officielle sera envisagée.
    Vous pouvez utiliser la liste de discussion de développement afin de le faire savoir ou demander de l’aide quant à la réalisation de ce plugin. MediaSPIP étant basé sur SPIP, il est également possible d’utiliser le liste de discussion SPIP-zone de SPIP pour (...)

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

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

  • H264 keyframe issue with RTP

    3 septembre 2015, par Mat DePasquale

    I’m building an RTP encoder for H264 video. The video data provider doesn’t periodically stream the keyframe in the data, instead they have provided me with a binary file representation of the keyframe. This includes the SPS-PPS-SEI and then 8 slices of the i-frame.

    Since I am encoding RTP, I need to rebroadcast this keyframe at 2 second intervals. I am doing that in my code, along with the rest of the data as it comes in. I am using ffmpeg to connect to the RTP data via a UDP socket for display testing.

    I am noticing that every 2 seconds, the video seems to blank and resync itself, pixelate, etc. Obviously, this is highly undesirable in the video product. I’ve been trying to debug this for quite some time and the only thing I can determine is that it has to do with the keyframe. If I just send the keyframe once, and then the rest of the data, ffmpeg displays the video fine. But in a network environment, I need to send the keyframe at periodic intervals.

    Does anyone have an idea as to why this resyncing of the video happens and most importantly, how to stop it from happening ?

    Thanks !

  • lavc : allow asynchronous decoders to return correct pkt_dts values

    11 septembre 2015, par wm4
    lavc : allow asynchronous decoders to return correct pkt_dts values

    The generic code in utils.c sets the AVFrame.pkt_dts field from the
    
packet it was supposedly decoded. This does not have to be true for a
    
fully asynchronous decoder like mmaldec. It could be overwritten with an
    
incorrect value. Even if the decoder doesn’t determine the DTS (but sets
    
it to AV_NOPTS_VALUE), it’s impossible to determine a correct value in
    
utils.c.
    

    Decoders can now be marked with FF_CODEC_CAP_SETS_PKT_DTS, in which case
    
utils.c won’t overwrite the field. The decoders are expected to set this
    
field (even if they only set it to AV_NOPTS_VALUE).
    

    Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
    • [DBH] libavcodec/internal.h
    • [DBH] libavcodec/mmaldec.c
    • [DBH] libavcodec/utils.c

  • dnxhddec : better support for 4:4:4

    4 octobre 2015, par Christophe Gisquet
    dnxhddec : better support for 4:4:4

    Profiles 1256 & 1270 (currently) signal at the frame header and MB
    
levels the colorspace used, either RGB or YUV. While a MB-level
    
varying colorspace is not supported, whether it is constant can be
    
tracked so as to determine the exact colorspace.
    

    This requires having bitdepth and the ACT and 4:4:4 flags, in turn
    
needing the CID. Because setting those before having validated
    
enough things may result in invalid/unset DSP fucntions, setting
    
the bitdepth in the context is delayed.
    

    It is not tested against a true RGB sequence, though.
    

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavcodec/dnxhddec.c

Navigation