Recherche avancée

Médias (1)

Mot : - Tags -/graphisme

Autres articles (60)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

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

  • Is there any way to resume live h264 playback (client rejoin) using the h.264 codec ?

    22 février 2021, par Ice

    Currently, I'm having a bit of an issue with the MediaSource API for resuming live h264 playback.
My server-side code will keep the first packet from FFmpeg, then dispatch it to clients. However, this works well but raises an issue.

    


    When I restart the stream and it dispatches to the client(s), it goes as expected and this is the result I expect when a client disconnects then has to reconnect to the stream, is the aforementioned result

    


    However, if I were to rejoin the stream, I get this as the result

    


    Also, FFMpeg data is being sent to the client in the picture above, it's just not rendering it for some reason.

    


    Here's my function for playing audio/video frames that I get from the server.

    


    private _playFrame(type: 0 | 1) {
    const src = type === 0 ? this.audioSource : this.videoSource;
    if (!src || src.updating) return;
    const queue = type === 0 ? this.audioFrameQueue : this.videoFrameQueue;
    src.appendBuffer(queue.shift());
    if (this.video.src && this.video.paused) this.video.play().then(() => null);
}


    


  • NewTeeVee Guide to Playing WebM

    4 août 2010, par noreply@blogger.com (John Luther)

    Janko Roettgers at NewTeeVee has written a handy guide to playing WebM video on your system. Check it out.

  • NewTeeVee Guide to Playing WebM

    4 août 2010, par noreply@blogger.com (John Luther)

    Janko Roettgers at NewTeeVee has written a handy guide to playing WebM video on your system. Check it out.

Navigation