Recherche avancée

Médias (91)

Autres articles (51)

  • Les vidéos

    21 avril 2011, par

    Comme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
    Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
    Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Mise à disposition des fichiers

    14 avril 2011, par

    Par défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
    Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
    Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...)

Sur d’autres sites (4433)

  • muxing streamable segmented mp4 with libav

    24 juillet 2020, par Elias Wagnerberger

    currently i have an application that is supposed to send fragmented mp4 data over a websocket to a client for it to be played there.

    


    i have a working implementation that pipes the raw frames to a spawned ffmpeg process and then reads fragmented mp4 segments from the output pipe before it sends those on to the client where the client then displays the video correctly.

    


    my problem is that when i try to make an implementation using libav it doesnt seem to work. my libav config uses libx264 to encode the frames before muxing them to a mp4, but when i try to play the provided segments in a browser using MSE it spits out an error. after having checked chrome ://media-internals i have figured out that chrome complains when i provide the moov box that is one of the two initialization boxes of a fmp4 stream.

    


    chrome apparently has a problem with parsing that box when its sent from libav, but not when its sent from ffmpeg.

    


    my question is :
What is the correct muxer configuration of libav so that it creates a fragmented mp4 stream where the client can recieve media boxes from the middle, after having been provided the init boxes ?

    


  • Problems with muxing fmp4 stream with libav

    20 juillet 2020, par Elias Wagnerberger

    currently i have an application that is supposed to send fragmented mp4 data over a websocket to a client for it to be played there.

    


    i have a working implementation that pipes the raw frames to a spawned ffmpeg process and then reads fragmented mp4 segments from the output pipe before it sends those on to the client where the client then displays the video correctly.

    


    my problem is that when i try to make an implementation using libav it doesnt seem to work. my libav config uses libx264rgb to encode the frames before muxing them to a mp4, but when i try to play the provided segments in a browser using MSE it spits out an error. after having checked chrome ://media-internals i have figured out that the problem lies in the moov box that is one of the two initialization boxes of a fmp4 stream.

    


    chrome apparently has a problem with parsing that box when its sent from libav, but not when its sent from ffmpeg.

    


    my question is :
What is the correct muxer configuration of libav so that it creates a fragmented mp4 stream where the client can recieve media boxes from the middle, after having been provided the init boxes ?

    


  • Problems with muxing fmp4 stream with libav

    20 juillet 2020, par Elias Wagnerberger

    currently i have an application that is supposed to send fragmented mp4 data over a websocket to a client for it to be played there.

    


    i have a working implementation that pipes the raw frames to a spawned ffmpeg process and then reads fragmented mp4 segments from the output pipe before it sends those on to the client where the client then displays the video correctly.

    


    my problem is that when i try to make an implementation using libav it doesnt seem to work. my libav config uses libx264rgb to encode the frames before muxing them to a mp4, but when i try to play the provided segments in a browser using MSE it spits out an error. after having checked chrome ://media-internals i have figured out that the problem lies in the moov box that is one of the two initialization boxes of a fmp4 stream.

    


    chrome apparently has a problem with parsing that box when its sent from libav, but not when its sent from ffmpeg.

    


    my question is :
What is the correct muxer configuration of libav so that it creates a fragmented mp4 stream where the client can recieve media boxes from the middle, after having been provided the init boxes ?

    


Navigation