Recherche avancée

Médias (0)

Mot : - Tags -/alertes

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

Autres articles (38)

  • 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

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

Sur d’autres sites (5332)

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

  • 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
  • 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