Recherche avancée

Médias (91)

Autres articles (96)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

  • on2avc : change a comment at #endif to match actual define

    23 avril 2014, par Kostya Shishkov
    on2avc : change a comment at #endif to match actual define
    • [DBH] libavcodec/on2avcdata.h

  • Why does FFmpeg's xfade filter need the timebase and frame rate to match ?

    17 novembre 2022, par Hashim Aziz

    As I discovered not long ago, and recently had to rediscover after trying to use it again, xfade - the crossfade filter that FFmpeg introduced in 2019 - requires that both inputs have a matching timebase (TBN) and frame rate (FPS).

    


    This is "resolved" by explicitly making them the same, by adding SETTB and a hardcoded FPS to both streams (there doesn't seem to be a constant equivalent to AVTB for FPS) prior to using xfade :

    


    -filter_complex \
[0:v]settb=AVTB,fps=29[v0];
[1:v]settb=AVTB,fps=29[v1];
[v0][v1]xfade=transition=fade:duration=$fadeduration:offset=$fadetime,format=yuv420p[faded]; 


    


    However, I'm confused as to why is this necessary in the first place. The concat filter works similarly in that requires all its inputs to have matching parameters, but this makes sense because the whole point of concat is to avoid re-encoding. If the xfade filter is (presumably) re-encoding anyway, why do the timebase and frame rate still need to match ?

    


    Is there a reason the devs decided to enforce these limitations for the filter when they don't seem to be technically necessary ?

    


  • nvenc : Make sure that enum and array index match

    24 septembre 2016, par Luca Barbato
    nvenc : Make sure that enum and array index match

    And use a macro to reduce the boilerplate.
    

    Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
    
Signed-off-by : Diego Biurrun <diego@biurrun.de>
    
Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
    • [DBH] libavcodec/nvenc.c

Navigation