Recherche avancée

Médias (3)

Mot : - Tags -/pdf

Autres articles (105)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

Sur d’autres sites (8595)

  • x86 : h264_idct : Update comments to match 8/10-bit depth optimization split

    6 octobre 2013, par Diego Biurrun
    x86 : h264_idct : Update comments to match 8/10-bit depth optimization split
    • [DBH] libavcodec/x86/h264_idct.asm

  • 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 ?

    


Navigation