Recherche avancée

Médias (1)

Mot : - Tags -/publicité

Autres articles (31)

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

Sur d’autres sites (7556)

  • What's the relationship between AVPacket in FFMpeg and H.264 NAL Uint ?

    10 octobre 2017, par Ello

    I use FFMpeg’s api to encode images to H.264 stream, the code is like this encode code. When I called the function avcodec_encode_video2 I got one AVPacket’s data, then I saved it to file. I use several images to get several files for test.
    Based on the startcode 00 00 00 01 or 00 00 01, I found that the 1st and 2nd files’ data both contain several H.264 NAL Uints. But start from the third file, I can’t found the startcode. Like followed image.
    Picture

    I feel confused. Base on the FFMpeg’s code I think one AVPacket’s data should contain at least one NAL Uint, but the result is unexpected. Is that means one NAL Uint may be divided to two AVPackets’ data ? What’s the relationship between AVPacket and H.264 NAL Uint ?

  • What's the relationship between AVPacket in FFMpeg and H.264 NAL Uint ?

    10 octobre 2017, par Ello

    I use FFMpeg’s api to encode images to H.264 stream, the code is like this encode code. When I called the function avcodec_encode_video2 I got one AVPacket’s data, then I saved it to file. I use several images to get several files for test.
    Based on the startcode 00 00 00 01 or 00 00 01, I found that the 1st and 2nd files’ data both contain several H.264 NAL Uints. But start from the third file, I can’t found the startcode. Like followed image.
    Picture

    I feel confused. Base on the FFMpeg’s code I think one AVPacket’s data should contain at least one NAL Uint, but the result is unexpected. Is that means one NAL Uint may be divided to two AVPackets’ data ? What’s the relationship between AVPacket and H.264 NAL Uint ?

  • What's the relationship between AVPacket in FFMpeg and H.264 NAL Uint ?

    8 juin 2016, par Ello

    I use FFMpeg’s api to encode images to H.264 stream, the code is like this encode code. When I called the function avcodec_encode_video2 I got one AVPacket’s data, then I saved it to file. I use several images to get several files for test.
    Based on the startcode 00 00 00 01 or 00 00 01, I found that the 1st and 2nd files’ data both contain several H.264 NAL Uints. But start from the third file, I can’t found the startcode. Like followed image.
    Picture

    I feel confused. Base on the FFMpeg’s code I think one AVPacket’s data should contain at least one NAL Uint, but the result is unexpected. Is that means one NAL Uint may be divided to two AVPackets’ data ? What’s the relationship between AVPacket and H.264 NAL Uint ?

Navigation