Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

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

Autres articles (44)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (7722)

  • How to upload and overlay animation.html file from system and overlay over video in HTML or ANGULAR

    23 septembre 2020, par Hiren

    Hey I am trying to build an app which has a functionality of allowing a user to upload a pre-existing .HTML file from his system which contains a simple animation init

    


    I want to get that file and overlay the animation contained in .HTML file on my video and display it to the user.

    


    is that possible please help me if it is.

    


    

    

    body {
  background: #;
}

#fullScreenBox {
  height: 500px;
  width: 50%;
  background: #;
  position: absolute;
  top: 0;
  bottom: 0;
  left: 0;
  right: 0;
  margin: auto;
}

#hiddenBox {
  width: 50%;
  height: 500px;
  background: #;
  position: absolute;
  top: 0;
  bottom: 0;
  left: 0;
  right: 0;
  margin: auto;
  overflow: hidden;
}

#title {
  width: 100%;
  height: 150px;
  background: #;
  /*U can also use #*/
  position: absolute;
  top: 200px;
  font-family: arial;
  font-size: 50px;
  color: white;
  text-align: center;
  opacity: 0;
}

#subtitle {
  width: 100%;
  height: 50px;
  background: #;
  /*U can also use #*/
  position: absolute;
  top: 300px;
  font-family: arial;
  font-size: 50px;
  color: red;
  text-align: center;
  opacity: 0;
}

#line01 {
  width: 25%;
  height: 4px;
  background: white;
  /*U can also use #*/
  position: absolute;
  top: 50px;
  bottom: 0;
  left: 0;
  right: 0;
  margin: auto;
  color: white;
  opacity: 0;
}

#overlay {
  position: absolute;
  color: #FFF;
  text-align: center;
  font-size: 20px;
  padding: 10px 0;
  width: 50%;
  height: 500px;
  background: #;
  top: 0;
  bottom: 0;
  left: 0;
  right: 0;
  margin: auto;
}

#v {
  height: 500px;
  width: 100%;
}

    


    &#xA;&#xA;  <div>&#xA;    <div class="">&#xA;      <div class="webvfx" data-animate="&#x27;{&#xA;">&#xA;        LONDON&#xA;      </div>&#xA;      <div class="webvfx" data-animate="&#x27;{&#xA;">&#xA;&#xA;      </div>&#xA;&#xA;      <div class="webvfx" data-animate="&#x27;{&#xA;">&#xA;        City of Dreams!&#xA;      </div>&#xA;    </div>&#xA;</div>

    &#xD;&#xA;

    &#xD;&#xA;

    &#xD;&#xA;&#xA;

    This is my HTML file that contains a simple animation for example which is in user system

    &#xA;

    In my application when user upload this file i want to overlay the animation contained in this file on the video as he uploads it is these any way&#xA;Thank you

    &#xA;

  • lavu/frame : Add Dolby Vision metadata side data type

    3 janvier 2022, par Niklas Haas
    lavu/frame : Add Dolby Vision metadata side data type
    

    In order to be able to extend this struct later (as the Dolby Vision RPU
    evolves), all of the 'container' structs are considered extensible, and
    the individual constituent fields must instead be accessed via offsets.
    The precedent for this style of access is set in
    <libavutil/detection_bbox.h>

    Signed-off-by : Niklas Haas <git@haasn.dev>
    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

    • [DH] doc/APIchanges
    • [DH] libavutil/dovi_meta.c
    • [DH] libavutil/dovi_meta.h
    • [DH] libavutil/frame.c
    • [DH] libavutil/frame.h
    • [DH] libavutil/version.h
  • FFmpeg Has A Native VP8 Decoder

    24 juin 2010, par Multimedia Mike — VP8

    Thanks to David Conrad and Ronald Bultje who committed their native VP8 video decoder to the FFmpeg codebase yesterday. At this point, it can decode 14/17 of the VP8 test vectors that Google released during the initial open sourcing event. Work is ongoing on those 3 non-passing samples (missing bilinear filter). Meanwhile, FFmpeg’s optimization-obsessive personalities are hard at work optimizing the native decoder. The current decoder is already profiled to be faster than Google/On2’s official libvpx.

    Testing
    So it falls to FATE to test this on the ridiculous diversity of platforms that FFmpeg supports. I staged individual test specs for each of the 17 test vectors : vp8-test-vector-001 ... vp8-test-vector-017. After the samples have propagated through to the various FATE installations, I’ll activate the 14 test specs that are currently passing.

    Initial Testing Methodology
    Inspired by Ronald Bultje’s idea, I built the latest FFmpeg-SVN with libvpx enabled. Then I selected between the reference and native decoders as such :

    $ for i in 001 002 003 004 005 006 007 008 009 \
     010 011 012 013 014 015 016 017
    do
      echo vp80-00-comprehensive-$i.ivf
      ffmpeg -vcodec libvpx -i \
        /path/to/vp8-test-vectors-r1/vp80-00-comprehensive-$i.ivf \
        -f framemd5 - 2> /dev/null
    done > refs.txt
    

    $ for i in 001 002 003 004 005 006 007 008 009 \
    010 011 012 013 014 015 016 017
    do
    echo vp80-00-comprehensive-$i.ivf
    ffmpeg -vcodec vp8 -i \
    /path/to/vp8-test-vectors-r1/vp80-00-comprehensive-$i.ivf \
    -f framemd5 - 2> /dev/null
    done > native.txt

    $ diff -u refs.txt native.txt

    That reveals precisely which files differ.