Recherche avancée

Médias (0)

Mot : - Tags -/objet éditorial

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (64)

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • Configurer la prise en compte des langues

    15 novembre 2010, par

    Accéder à la configuration et ajouter des langues prises en compte
    Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
    De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
    Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...)

  • XMP PHP

    13 mai 2011, par

    Dixit Wikipedia, XMP signifie :
    Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
    Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
    XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...)

Sur d’autres sites (6312)

  • 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