Recherche avancée

Médias (1)

Mot : - Tags -/Rennes

Autres articles (65)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

  • D’autres logiciels intéressants

    12 avril 2011, par

    On ne revendique pas d’être les seuls à faire ce que l’on fait ... et on ne revendique surtout pas d’être les meilleurs non plus ... Ce que l’on fait, on essaie juste de le faire bien, et de mieux en mieux...
    La liste suivante correspond à des logiciels qui tendent peu ou prou à faire comme MediaSPIP ou que MediaSPIP tente peu ou prou à faire pareil, peu importe ...
    On ne les connais pas, on ne les a pas essayé, mais vous pouvez peut être y jeter un coup d’oeil.
    Videopress
    Site Internet : (...)

  • Possibilité de déploiement en ferme

    12 avril 2011, par

    MediaSPIP peut être installé comme une ferme, avec un seul "noyau" hébergé sur un serveur dédié et utilisé par une multitude de sites différents.
    Cela permet, par exemple : de pouvoir partager les frais de mise en œuvre entre plusieurs projets / individus ; de pouvoir déployer rapidement une multitude de sites uniques ; d’éviter d’avoir à mettre l’ensemble des créations dans un fourre-tout numérique comme c’est le cas pour les grandes plate-formes tout public disséminées sur le (...)

Sur d’autres sites (6671)

  • How to calculate byte/index ranges for mpeg-dash MPD file ?

    7 avril 2016, par TheSHEEEP

    I basically know how an .mpd file would have to be structured to support streaming from separate .mp4 (or webm) files.

    However, I would like to implement the "static" (aka "on-demand") method, thus only having one file per quality that I want to offer in the stream.

    In all samples, this is done by supplying the indexRange & range values within a Representation like this :

    <representation bandwidth="2073921" codecs="avc1.4d401f" height="720" mimetype="video/mp4" width="1280">
    
        <baseurl>car-20120827-88.mp4</baseurl>
    
        <segmentbase indexrange="708-1183">
    
          <initialization range="0-707"></initialization>
    
        </segmentbase>
    
</representation>

    What I could not find out anywhere is how one would calculate the indexRange/range values here, using only ffmpeg (or ffprobe).
    What exactly would one have to do to get those numbers right for arbitrary (yet supported, of course) video files to create the .mpd file for them ?

    Or am I trying to figure out something in vain here and those values are just arbitrary ?

  • Extract motion vectors from x265 (HVEC) encoded video with ffmepg/libavcodec ?

    16 novembre 2017, par John Allard

    I know that one can extract the motion vectors from an h264 encoded via by first setting the flag

    av_dict_set(&amp;opts, "flags2", "+export_mvs", 0);

    then you can query the side-data for the motion vectors by doing this

    sd = av_frame_get_side_data(frame, AV_FRAME_DATA_MOTION_VECTORS);

    When I looked online to see if you can do something similar with HVEC encoded videos, I wasn’t able to find any information. All I found was this by the definition of "AV_FRAME_DATA_MOTION_VECTORS"

    Motion vectors exported by some codecs (on demand through the
    export_mvs flag set in the libavcodec AVCodecContext flags2 option).

    The data is the AVMotionVector struct defined in
    libavutil/motion_vector.h.

    but there was no information on exactly which codecs export this motion vector information. How would I go about finding this out ?

  • Extract motion vectors from x265 (HEVC) encoded video with ffmpeg/libavcodec ?

    28 mars 2018, par John Allard

    I know that one can extract the motion vectors from an h264 encoded via by first setting the flag

    av_dict_set(&amp;opts, "flags2", "+export_mvs", 0);

    then you can query the side-data for the motion vectors by doing this

    sd = av_frame_get_side_data(frame, AV_FRAME_DATA_MOTION_VECTORS);

    When I looked online to see if you can do something similar with HEVC encoded videos, I wasn’t able to find any information. All I found was this by the definition of "AV_FRAME_DATA_MOTION_VECTORS"

    Motion vectors exported by some codecs (on demand through the
    export_mvs flag set in the libavcodec AVCodecContext flags2 option).

    The data is the AVMotionVector struct defined in
    libavutil/motion_vector.h.

    but there was no information on exactly which codecs export this motion vector information. How would I go about finding this out ?

Navigation