Recherche avancée

Médias (91)

Autres articles (92)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

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

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

Sur d’autres sites (13090)

  • Tools/Techniques for investigating video corruption — ffmpeg / libavcodec

    17 juillet 2013, par Gopherkhan

    In my current work I'm trying to encode some images to h264 video using the FFMPEG's C library. The resulting video plays fine in VLC, but has no preview image. The video can play in VLC and Mplayer on ubuntu, but won't play on Mac or PC (in fact, it causes a "VTDecoderXPCService quit unexpectedly" error on Mac).

    If I run the resulting file through FFMPEG using the command line, the resulting file has a preview image, and plays correctly everywhere.

    Apparently the file that I get out of the program is corrupt in some weird place, but I don't have any output during my compilation or run to indicate where. I can't share my code at the moment (work code isn't open source yet :-( ), but I have tried a number of things :

    1. Writing only header and trailer data (av_write_trailer) and no frames
    2. writing frames only minus the trailer (using avcodec_encode_video2 and av_write_frame)
    3. Adjusting our time_base and frame pts values to encode only one frame per second
    4. Removing all variable frame rate code
    5. Numerous other variants that I won't bother you with here

    In creating my project, I've also followed the following tutorials :

    And consulted the deprecated ffmpeg functions list

    And compiled FFMPEG on ubuntu according to the official doc

    And consulted numerous StackOverflow questions :

    But every run of the program runs into the exact same problem.

    My question is, is there anything obvious that causes a programmatic run of FFMpeg to differ from a console run (e.g., an incomplete finalization, some threading issues, etc.) ? Like some obvious reason that a console run could repair a corrupted file ? Or is there a decent tool/method for inspecting a video file and finding the point of corruption ?

  • add libaribb24 ARIB STD-B24 caption decoder

    14 janvier 2019, par Jan Ekström
    add libaribb24 ARIB STD-B24 caption decoder
    

    * Outputs ASS lines with basic coloring and font scaling for each
    given region.
    * Sets the default style to the resolution of the subtitle plane
    (for example, 960x540 / 36pt font for profile A).
    * Has options to :
    * Disable ruby text (which is coded as regions which have
    half-height text in libaribb24).
    Enabled by default as without positioning ruby text only
    confuses as it is usually coded in the beginning of the decoded
    subtitle line.
    * Set the working directory, in which libaribb24 will read
    configuration as well as into which it may save broadcast extra
    symbols as PNG.
    Unset by default.

    The unconventional library check can be explained by the library's
    current master branch being licensed as LGPLv3, but at the time of
    writing the latest official release is still licensed under GPLv3.

    Thus, one either has to wait for the following release, or enable
    GPLv3.

    • [DH] Changelog
    • [DH] configure
    • [DH] doc/decoders.texi
    • [DH] libavcodec/Makefile
    • [DH] libavcodec/allcodecs.c
    • [DH] libavcodec/avcodec.h
    • [DH] libavcodec/codec_desc.c
    • [DH] libavcodec/libaribb24.c
    • [DH] libavcodec/profiles.c
    • [DH] libavcodec/profiles.h
    • [DH] libavcodec/version.h
  • Merge commit ’b70d7a4ac72d23f3448f3b08b770fdf5f57de222’

    15 mai 2014, par Michael Niedermayer
    Merge commit ’b70d7a4ac72d23f3448f3b08b770fdf5f57de222’
    

    * commit ’b70d7a4ac72d23f3448f3b08b770fdf5f57de222’ :
    lavc : add a native Opus decoder.

    Conflicts :
    Changelog
    configure
    libavcodec/version.h

    Fate tests pass with both avresample as well as swresample based opus decoder, but
    are disabled (reference files are very large so i want to think a day or 2 about
    if theres an alternative or if they could be avoided, they also dont match the
    official samples)

    Merged-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] Changelog
    • [DH] configure
    • [DH] libavcodec/Makefile
    • [DH] libavcodec/allcodecs.c
    • [DH] libavcodec/opus.c
    • [DH] libavcodec/opus.h
    • [DH] libavcodec/opus_celt.c
    • [DH] libavcodec/opus_imdct.c
    • [DH] libavcodec/opus_parser.c
    • [DH] libavcodec/opus_silk.c
    • [DH] libavcodec/opusdec.c
    • [DH] libavcodec/version.h
    • [DH] tests/Makefile
    • [DH] tests/fate/opus.mak