Recherche avancée

Médias (1)

Mot : - Tags -/Christian Nold

Autres articles (94)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

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

  • Revision 43047 : le prefix de Zpip, c’est Z

    20 décembre 2010, par maieul@… — Log

    le prefix de Zpip, c’est Z

  • avformat/url : check url root node when rel include double dot and trim double dot

    29 avril 2020, par Steven Liu
    avformat/url : check url root node when rel include double dot and trim double dot

    fix ticket : 8625
    
and add testcase into url for double dot corner case
    

    Signed-off-by : Steven Liu <lq@chinaffmpeg.org>
    • [DH] libavformat/tests/url.c
    • [DH] libavformat/url.c
    • [DH] tests/ref/fate/url

  • HTML5 Progressive Streaming — no follow-up range requests

    20 septembre 2023, par user2333829

    I'm working on an embedded device that is recording video on the fly. I'd like to stream that to an HTML5 video element, using our own custom server. I have this almost working and would like some help.

    &#xA;&#xA;

    So far as I can tell, I've got libav / ffmpeg doing their job right. I encoded an mp4 in RAM with the moov atom at the start of the file. I've written this file to disk and it plays everywhere it should.

    &#xA;&#xA;

    The problem, I think, lies with how I'm responding to HTTP range requests. When I try to do a live stream, I get an initial range request from the browser / player (currently tried Chrome, Firefox, and VLC) for bytes:0-. I responded with some initial bytes. The browser / player actually plays this fine, but never asks again. So the live stream doesn't work, just the first 3 seconds or whatever.

    &#xA;&#xA;

    I've looked at the RFC spec of partial content, and my understanding is I'm doing what I should be... Clearly I'm not though. Here is an example of a request / response with Chrome as the requester :

    &#xA;&#xA;

    &#xA;&#xA;

    &#xA;get /live.mp4 HTTP/1.1&#xA;host: localhost:1235&#xA;connection: keep-alive&#xA;accept-encoding: identity;q=1, *;q=0&#xA;user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36&#xA;accept: */*&#xA;dnt: 1&#xA;accept-language: en-GB,en-US;q=0.9,en;q=0.8&#xA;range: bytes=0-&#xA;

    &#xA;&#xA;

    &#xA;HTTP/1.1 206 Partial Content&#xA;Accept-Ranges: bytes&#xA;Content-Type: video/mp4&#xA;Content-Length: 182400&#xA;Content-Range: bytes 0-182399/*&#xA;

    &#xA;&#xA;

    &#xA;&#xA;

    Again, with that request / response pair, Chrome plays the first 182400 bytes but never makes a second request. I thought having the '*' in Content-Range would make this happen...

    &#xA;

Navigation