Recherche avancée

Médias (39)

Mot : - Tags -/audio

Autres articles (58)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • 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

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

  • How to filter motion vectors ?

    2 août 2019, par vdletg

    My video is very noisy temporally. The video was taken under low light conditions at a high frame rate.

    Currently I’ve tried

    ffplay -flags2 +export_mvs -i test.mp4 -vf edgedetect=low=0.05:high=0.17,hqdn3d=4.0:3.0:6.0:4.5,codecview=mv=pf+bf+bb,"lutyuv=y='if(lt(val,19),0,val)'

    The motion vectors are tracking noise as in the near dark areas the vectors varying greatly in magnitude and angle.

    How do I decimate or filter the display motion vectors based on magnitude and/or location ?

  • fate : use current syntax for the scale filter

    10 juillet 2013, par Sean McGovern
    fate : use current syntax for the scale filter

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] tests/fate/filter-video.mak
    • [DH] tests/fate/h264.mak

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

    19 juin, 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).

    &#xA;

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

    &#xA;

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

    &#xA;

    However, I'm confused as to why is this necessary in the first place. The concat filter works similarly in that it 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 ?

    &#xA;

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

    &#xA;

Navigation