Recherche avancée

Médias (1)

Mot : - Tags -/belgique

Autres articles (94)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

Sur d’autres sites (8601)

  • avformat/matroskaenc : Rename functions to better reflect what they do

    15 avril 2020, par Andreas Rheinhardt
    avformat/matroskaenc : Rename functions to better reflect what they do
    

    EBML uses variable length integers both for the EBML IDs as well as for
    the EBML lengths ; Matroska also uses them for the TrackNumber in
    (Simple)Blocks and for the lengths of laces when EBML lacing is used.

    When encoding EBML lengths, certain encodings have a special meaning,
    namely that the element has an unknown length. This is not so when
    encoding general EBML variable length integers.

    Yet the functions called ebml_num_size() and put_ebml_num() had this
    special meaning hardcoded, i.e. they are there to write EBML lengths and
    not general EBML numbers. So rename them.

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavformat/matroskaenc.c
  • Go2Webinar decoder

    25 février 2013, par Kostya Shishkov
    Go2Webinar decoder
    
    • [DH] Changelog
    • [DH] configure
    • [DH] doc/general.texi
    • [DH] libavcodec/Makefile
    • [DH] libavcodec/allcodecs.c
    • [DH] libavcodec/avcodec.h
    • [DH] libavcodec/codec_desc.c
    • [DH] libavcodec/g2meet.c
    • [DH] libavcodec/version.h
    • [DH] libavformat/riff.c
  • Sharing FFMPEG video stream data between processes

    21 juin 2016, par lgaravaglia

    I’m trying to find a method for sharing FFMPEG library datatypes between two processes.

    The project that I’m working on requires one process to buffer the FFMPEG stream that is being received and another process needs to read from the buffer and perform some actions on the video stream. Unfortunately, I can’t use a multi-threaded approach for this project. Due to some limitations in my system I have to use separate processes.

    The data that I would like to share I have placed in a general struct as follows :

    struct FFMPEGData {
    AVFormatContext *pFormatCtx;
    AVCodecContext  *pCodecCtx;
    AVCodec         *pCodec;
    AVFrame         *pFrame, dst;
    AVPacket        *packet;
    AVPacket* pack = new AVPacket[packetNum];
    };

    The buffering process uses the format context and codec context to read the video stream and then it places packets in the AVPacket array pack. The other process should grab packets from the array and decode them, also using the format and codec contexts.

    I looked into the Boost Interprocess library, but that does not seem to be setup to handle this type of situation easily.

    Would anyone know a method for sharing my general struct between multiple processes ?