Recherche avancée

Médias (1)

Mot : - Tags -/école

Autres articles (66)

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

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (7538)

  • cook : check subbands more completely, fix out of array read.

    17 novembre 2012, par Michael Niedermayer

    cook : check subbands more completely, fix out of array read.

  • Cloaked Archive Wiki

    16 mai 2011, par Multimedia Mike — General

    Google’s Chrome browser has made me phenomenally lazy. I don’t even attempt to type proper, complete URLs into the address bar anymore. I just type something vaguely related to the address and let the search engine take over. I saw something weird when I used this method to visit Archive Team’s site :



    There’s greater detail when you elect to view more results from the site :



    As the administrator of a MediaWiki installation like the one that archiveteam.org runs on, I was a little worried that they might have a spam problem. However, clicking through to any of those out-of-place pages does not indicate anything related to pharmaceuticals. Viewing source also reveals nothing amiss.

    I quickly deduced that this is a textbook example of website cloaking. This is when a website reports different content to a search engine than it reports to normal web browsers (humans, presumably). General pseudocode :

    C :
    1. if (web_request.user_agent_string == CRAWLER_USER_AGENT)
    2.  return cloaked_data ;
    3. else
    4.  return real_data ;

    You can verify this for yourself using the wget command line utility :

    <br />
    $ wget --quiet --user-agent="<strong>Mozilla/5.0</strong>" \<br />
     http://www.archiveteam.org/index.php?title=Geocities -O - | grep \&lt;title\&gt;<br />
    &lt;title&gt;GeoCities - Archiveteam&lt;/title&gt;

    $ wget —quiet —user-agent="Googlebot/2.1"
    http://www.archiveteam.org/index.php?title=Geocities -O - | grep \<title\>
    <title>Cheap xanax | Online Drug Store, Big Discounts</title>

    I guess the little web prank worked because the phaux-pharma stuff got indexed. It makes we wonder if there’s a MediaWiki plugin that does this automatically.

    For extra fun, here’s a site called the CloakingDetector which purports to be able to detect whether a page employs cloaking. This is just one humble observer’s opinion, but I don’t think the site works too well :



  • ffmpeg av_read_frame is blocked long time

    10 avril 2018, par geeeek
    while (av_read_frame(pFormatCtx, packet) >= 0) {
       if (packet->stream_index == videoindex) {
           ret = avcodec_decode_video2(pCodecCtx, pFrame, &amp;got_picture, packet);
           if (ret &lt; 0) {
               printf("Decode Error.\n");
               return -1;
           }
           printf("Succeed to decode 1 frame! %d\n", tt++);
       }
       av_packet_unref(packet);
    }

    I am using ffmpeg to provide live audio/video RTSP streaming in android.

    But I have a trouble from blocking av_read_frame function forever.
    Android Log :

    I/libnav: Succeed to decode 1 frame! 70
    I/libnav: Succeed to decode 1 frame! 71
    I/libnav: Succeed to decode 1 frame! 72
    I/libnav: Succeed to decode 1 frame! 73
    I/libnav: Succeed to decode 1 frame! 74
    I/libnav: Succeed to decode 1 frame! 75
    blocking forever...

    Thus I
    have experimented some code stuffs. I have copied Android jni code about ffmpeg to pc(ubuntu). Above my code is worked without any blocking.

    Succeed to decode 21122 frame!
    Succeed to decode 21123 frame!
    Succeed to decode 21124 frame!
    ...
    without blocking ...

    I guess that this problem is about delay. I have removed avcodec_decode_video2 call in android jni. my code is executed without any blocking.

    I have found ffmpeg av_read_frame() need very long time to stop threads. But it can’t help me.

    If you have a similiar problem, please help me.