Recherche avancée

Médias (9)

Mot : - Tags -/soundtrack

Autres articles (48)

  • Librairies et logiciels spécifiques aux médias

    10 décembre 2010, par

    Pour un fonctionnement correct et optimal, plusieurs choses sont à prendre en considération.
    Il est important, après avoir installé apache2, mysql et php5, d’installer d’autres logiciels nécessaires dont les installations sont décrites dans les liens afférants. Un ensemble de librairies multimedias (x264, libtheora, libvpx) utilisées pour l’encodage et le décodage des vidéos et sons afin de supporter le plus grand nombre de fichiers possibles. Cf. : ce tutoriel ; FFMpeg avec le maximum de décodeurs et (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (8610)

  • avformat/matroskadec : Accept more unknown-length elements

    17 mai 2019, par Andreas Rheinhardt
    avformat/matroskadec : Accept more unknown-length elements
    

    The current Matroska specifications mandate that only two elements may
    use an unknown-length length : Segments and clusters. But this was not
    always so : For the greater part of Matroska's existence, all master
    elements were allowed to make use of the unknown-length feature.

    And there were muxers creating such files : For several years
    libavformat's Matroska muxer used unknown-length for all master
    elements when the output wasn't seekable. This only stopped in March
    2010 with 2529bb30. And even afterwards it was possible (albeit
    unlikely) for libavformat to create unknown-length master elements
    that are in violation of today's specifications, namely if the master
    element was so big that the seek backwards to update the size could
    no longer be performed inside the AVIOContext's write buffer. This
    has only been fixed in October 2016 (with the patches that introduced
    support for writing CRC-32 elements).

    Libavformat's Matroska demuxer meanwhile has never really supported
    unknown-length elements besides segments and clusters. Support for the
    latter was hardcoded. This commit changes this : Now all master elements
    for which a syntax to parse them is available are supported. This
    includes the files produced by old versions of libavformat's muxer.

    More precisely, master elements that have unknown length and are about
    to be parsed (not skipped) are supported ; only a warning is emitted for
    them. For normal files, this means that level 1 elements after the
    clusters that are encountered after the clusters have been parsed (i.e.
    not because they are referenced by the seekhead at the beginning of the
    file) are still unsupported (they would be skipped at this point if
    their length were known).

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

    • [DH] libavformat/matroskadec.c
  • avcodec/mips/cabac : replace addi with addiu

    2 juillet 2019, par YunQiang Su
    avcodec/mips/cabac : replace addi with addiu
    

    addi/daddi are deprecated by MIPS for years, and MIPS r6 remove
    them.

    They should be replace with addiu :
    ADDIU performs the same arithmetic operation but
    does not trap on overflow.

    Reviewed-by : Shiyou Yin <yinshiyou-hf@loongson.cn>
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavcodec/mips/cabac.h
  • ffmpeg - Invalid report file level (windows)

    24 octobre 2019, par Pedro Lobito

    ffmpeg is giving me an error and I couldn’t get much help googling it, besides a thread on ffmpeg mailing list dated 5 years ago which doesn’t address the exact same problem.

    No matter which ffmpeg version or build for windows I use, the error is always :

    c:\>ffmpeg.exe
    Invalid report file level

    I’ve been using ffmpeg on the same computer for years and I’ve no idea where the problem started and how to debug it. Any help is welcome.


    Notes :

    1. No antivirus is running
    2. ffmpeg.exe is on windows path
    3. I’ve tried installing ffmpeg with
      choco install
      ffmpeg

      but it reports the same error.