Recherche avancée

Médias (0)

Mot : - Tags -/upload

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

Autres articles (9)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

Sur d’autres sites (3910)

  • Merge commit ’182cf170a544bce069c8690c90b49381150a1f10’

    1er avril 2017, par Clément Bœsch
    Merge commit ’182cf170a544bce069c8690c90b49381150a1f10’
    

    * commit ’182cf170a544bce069c8690c90b49381150a1f10’ :
    vp8 : Return stream format information from parser

    Return codes are adjusted to consume the whole packet in case of error
    as the API does not allow returning AVERROR codes (a negative return
    value is valid).

    Merged-by : Clément Bœsch <u@pkh.me>

    • [DH] libavcodec/vp8_parser.c
  • FFmpeg error message when processing

    19 avril 2013, par FlyingCat

    Hi I am using FFmpeg to get the image from several video files.

    I got my ffmpeg codes ready but I got the following error when I exec my codes.

    ffmpeg version 0.8.6-4:0.8.6-0ubuntu0.12.04.1, Copyright (c) 2000-2013 the Libav developers
    built on Apr  2 2013 17:02:36 with gcc 4.6.3

    *** THIS PROGRAM IS DEPRECATED ***
    This program is only provided for compatibility and will be removed in a future release. Please use avconv instead.

    //files info...
    //files info...

    Incompatible pixel format &#39;yuv420p&#39; for codec &#39;mjpeg&#39;, auto-selecting format &#39;yuvj420p&#39;

    //file info...

    [buffer @ 0x1513c40] Buffering several frames is not supported. Please consume all available frames before adding a new one.
    Last message repeated 75 times

    [image2 @ 0x1513460] Could not open file : /test/project
    av_interleaved_write_frame(): Input/output error

    I only show the error messages that have color highlighted.

    My codes

                  $ffmpeg ="/usr/bin/ffmpeg";

                  $image_source_path = &#39;/test/project/test.mp4&#39;;
                  $ALL_PLACE_WIDTH = 300;
                  $ALL_PLACE_HEIGHT = 300;

                  $image_cmd = " -r 1 -ss 00:00:10 -t 00:00:01 -s ".$ALL_PLACE_WIDTH."x".$ALL_PLACE_HEIGHT."   -f image2 " ;

                  $dest_image_path = &#39;/test/project&#39;;

                  $str_command= $ffmpeg  ." -i " . $image_source_path . $image_cmd .$dest_image_path;
                  shell_exec($str_command);

    It seems my linux want to me switch avconv. I am not sure how to fix these errors. Can someone give me a hint about it ? Thanks so much !

  • avcodec/libdav1d : print libdav1d version in verbose level

    4 février 2024, par James Almer
    avcodec/libdav1d : print libdav1d version in verbose level
    

    info level will be too noisy if several instances of the decoder are fired
    at the same time, as will be the case with tiled AVIF.

    Signed-off-by : James Almer <jamrial@gmail.com>

    • [DH] libavcodec/libdav1d.c