Recherche avancée

Médias (91)

Autres articles (74)

  • Qu’est ce qu’un masque de formulaire

    13 juin 2013, par

    Un masque de formulaire consiste en la personnalisation du formulaire de mise en ligne des médias, rubriques, actualités, éditoriaux et liens vers des sites.
    Chaque formulaire de publication d’objet peut donc être personnalisé.
    Pour accéder à la personnalisation des champs de formulaires, il est nécessaire d’aller dans l’administration de votre MediaSPIP puis de sélectionner "Configuration des masques de formulaires".
    Sélectionnez ensuite le formulaire à modifier en cliquant sur sont type d’objet. (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

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

  • Revision 6a6c427710 : vp9/encoder/vp9_onyx_if : Fix compute_qdelta_by_rate() warnings - Rename and mak

    13 février 2014, par Tom Finegan

    Changed Paths :
     Modify /vp9/encoder/vp9_onyx_if.c



    vp9/encoder/vp9_onyx_if : Fix compute_qdelta_by_rate() warnings

    - Rename and make static
    s/vp9_compute_qdelta_by_rate/compute_qdelta_by_rate/
    - Make base_q_index an integer.
    - Add a cast.

    Change-Id : Iea8d1397fd2717e7373b182ec51f5db960ef2cca

  • Revision 235b77e54b : decode_test_driver : Use size_t for size arg to DecodeFrame(). Use size_t for De

    13 février 2014, par Tom Finegan

    Changed Paths :
     Modify /test/decode_test_driver.cc


     Modify /test/decode_test_driver.h



    decode_test_driver : Use size_t for size arg to DecodeFrame().

    Use size_t for DecodeFrame()'s size arg, and cast only
    at the vpx_codec_decode() call site. This silences warnings that
    appear in svc_test.cc when building with vs2013.

    Change-Id : I2cf39f02a45732c752097f07b0c7ad414b1517d8

  • NodeJS piping with ffmpeg

    8 février 2014, par Gnap

    I wanted to do a HTTP live stream on a screen cast with using ffmpeg, nodejs and html5 . I wanted it to be as real time as possible. However, I find that my video received by the client was behind by 1 2 seconds (On Chrome/Chromium). I am using vp8/webm as my codec.

    I have eliminated the following factors as such :
    1) Network : I have tried serving and receiving the video file locally by stating the video source to be 127.0.0.1:PORT or localhost:PORT
    2) ffmpeg encoding speed:I have tried outputting the file locally, it the "delay" seems to be negligible.
    3) Chrome internal buffer. The buffer was accounted to be 0.07s 0.08s.

    On the nodeJS side, I have a child process that runs the ffmpeg command, and did a ffmpeg.stdout.pipe(res) ; <— ffmpeg is child_process.spawn(...)

    So it seems that the ffmpeg.std.pipe(res) of nodejs seems to be the one delaying the video stream. Am I correct in assuming so ? Is there anyway that I may reduce the delay ?

Navigation