Recherche avancée

Médias (1)

Mot : - Tags -/net art

Autres articles (70)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

  • 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

Sur d’autres sites (11610)

  • If I pass this code in Windows console it works, but when I emulate windows console in node.js code doesn't work, and returns unclear error

    22 décembre 2016, par Maxim Cherevatov

    I have code :

    cmd.get(
       'trimp3  ant.mp3 ant2.mp3 00:00 00:20',
       function(data){
           console.log('the node-cmd cloned dir contains these files :\n\n',data)
       }
    );

    If pass this code in Windows console it works well !
    But, when i emulate windows console in node.js this code not work, and returns unclear mistake :

    [!!] ERROR:  "ffmpeg" �� ����� ����७��� ��� ���譥�
    ��������, �ᯮ��塞�� �ணࠬ��� ��� �������� 䠩���.

    To emulate the use node-cmd.

  • android ffmpeg halfninja av_open_input_file returns -2 (no such file or directory)

    20 janvier 2012, par cdavidyoung

    I have built ffmpeg for Android using the code and method described at

    https://github.com/halfninja/android-ffmpeg-x264

    using Ubuntu running in VirtualBox on windows. I then copied libvideokit.so into the Project\libs\armeabi folder of a Windows copy of the provided projects. From there I was able to run the ProjectTest from Eclipse on my Android device. I can see the ffmpeg code being executed but when it gets to the point of opening the input file it gives me the indicated error. I have noticed some discussion of this problem at

    FFMpeg on Android, undefined references to libavcodec functions, although it is listed on command line

    but the solutions have not helped since the file protocol is enabled in this build and I also tried putting "file :" in front of the filepath to no avail. For completeness I tried setting minimal_featureset=0 to enable all the defaults but this gives me the same error. Below is a snapshot of the logcat from Eclipse showing the output from Videokit with an extra call to LOGE to display the result from av_open_input_file. Any suggestions of things to try would be greatly appreciated.

    10-23 11:57:33.888: DEBUG/Videokit(4830): run() called
    10-23 11:57:33.888: DEBUG/Videokit(4830): run passing off to main()
    10-23 11:57:33.904: DEBUG/Videokit(4830): main(): registering all modules
    10-23 11:57:33.927: DEBUG/Videokit(4830): main(): registered everything
    10-23 11:57:33.927: DEBUG/Videokit(4830): main(): initting opts
    10-23 11:57:33.943: DEBUG/Videokit(4830): main(): initted opts.
    10-23 11:57:33.943: ERROR/Videokit(4830): ffmpeg version N-30996-gf925b24, Copyright (c) 2000-2011 the FFmpeg developers
    10-23 11:57:33.943: ERROR/Videokit(4830):   built on Oct 21 2011 13:54:03 with gcc 4.4.3
    10-23 11:57:33.943: ERROR/Videokit(4830):   configuration: --enable-cross-compile --arch=arm5te --enable-armv5te --target-os=linux --disable-stripping --prefix=../output --disable-neon --enable-version3 --disable-shared --enable-static --enable-gpl --enable-memalign-hack --cc=arm-linux-androideabi-gcc --ld=arm-linux-androideabi-ld --extra-cflags='-fPIC -DANDROID -D__thumb__ -mthumb -Wfatal-errors -Wno-deprecated' --disable-everything --enable-decoder=mjpeg --enable-demuxer=mjpeg --enable-parser=mjpeg --enable-demuxer=image2 --enable-muxer=mp4 --enable-encoder=libx264 --enable-libx264 --enable-decoder=rawvideo --enable-protocol=file --enable-hwaccels --disable-ffmpeg --disable-ffplay --disable-ffprobe --disable-ffserver --disable-network --enable-filter=buffer --enable-filter=buffersink --disable-demuxer=v4l --disable-demuxer=v4l2 --disable-indev=v4l --disable-indev=v4l2 --extra-cflags='-I../x264 -Ivideokit' --extra-ldflags=-L../x264
    10-23 11:57:33.943: DEBUG/Videokit(4830): main(): parsing options
    10-23 11:57:33.943: DEBUG/Videokit(4830): parse_options has 4 options to parse
    10-23 11:57:33.951: ERROR/Videokit(4830): opt_input_file av_open_input_file /mnt/sdcard/fun/snap0000.jpg -2
    10-23 11:57:33.951: ERROR/Videokit(4830): /mnt/sdcard/fun/snap0000.jpg: No such file or directory
    10-23 11:57:33.951: ERROR/Videokit(4830): ffmpeg_exit(1) called!
  • Overlay filter in LibAV/FFMpeg returns strange (tripled) frame in C

    28 juillet 2014, par gkuczera

    I tried to make a program, which merges two frames. I use LibAV (libav-win32-20140428) under Windows 7 64 and Visual Studio 2013.
    But the result is quite odd.

    http://oi58.tinypic.com/rcobnm.jpg

    The filter which was used is Overlay. When I change the graph, to the one, that uses only one stream and add FADE effect, everything works like a charm. But OVERLAY and eg. DRAWBOX give me strange distortion (three frames on one and black and white effect). Here is the code :

    static int init_filter_graph(AVFilterGraph **pGraph, AVFilterContext **pSrc1, AVFilterContext **pSink)
    {
       AVFilterGraph* tFilterGraph;
       AVFilterContext* tBufferContext1;
       AVFilter* tBuffer1;
       AVFilterContext* tColorContext;
       AVFilter* tColor;
       AVFilterContext* tOverlayContext;
       AVFilter* tOverlay;
       AVFilterContext* tBufferSinkContext;
       AVFilter* tBufferSink;

       int tError;

       /* Create a new filtergraph, which will contain all the filters. */
       tFilterGraph = avfilter_graph_alloc();

       if (!tFilterGraph) {
           return -1;
       }

       { // BUFFER FILTER 1
           tBuffer1 = avfilter_get_by_name("buffer");
           if (!tBuffer1) {
               return -1;
           }
           tBufferContext1 = avfilter_graph_alloc_filter(tFilterGraph, tBuffer1, "src1");
           if (!tBufferContext1) {
               return -1;
           }

           av_dict_set(&tOptionsDict, "width", "320", 0);
           av_dict_set(&tOptionsDict, "height", "240", 0);
           av_dict_set(&tOptionsDict, "pix_fmt", "bgr24", 0);
           av_dict_set(&tOptionsDict, "time_base", "1/25", 0);
           av_dict_set(&tOptionsDict, "sar", "1", 0);
           tError = avfilter_init_dict(tBufferContext1, &tOptionsDict);
           av_dict_free(&tOptionsDict);
           if (tError < 0) {
               return tError;
           }
       }

       { // COLOR FILTER
           tColor = avfilter_get_by_name("color");
           if (!tColor) {
               return -1;
           }
           tColorContext = avfilter_graph_alloc_filter(tFilterGraph, tColor, "color");
           if (!tColorContext) {
               return -1;
           }

           av_dict_set(&tOptionsDict, "color", "white", 0);
           av_dict_set(&tOptionsDict, "size", "20x120", 0);
           av_dict_set(&tOptionsDict, "framerate", "1/25", 0);
           tError = avfilter_init_dict(tColorContext, &tOptionsDict);
           av_dict_free(&tOptionsDict);
           if (tError < 0) {
               return tError;
           }
       }

       { // OVERLAY FILTER
           tOverlay = avfilter_get_by_name("overlay");
           if (!tOverlay) {
               return -1;
           }
           tOverlayContext = avfilter_graph_alloc_filter(tFilterGraph, tOverlay, "overlay");
           if (!tOverlayContext) {
               return -1;
           }

           av_dict_set(&tOptionsDict, "x", "0", 0);
           av_dict_set(&tOptionsDict, "y", "0", 0);
           av_dict_set(&tOptionsDict, "main_w", "120", 0);
           av_dict_set(&tOptionsDict, "main_h", "140", 0);
           av_dict_set(&tOptionsDict, "overlay_w", "320", 0);
           av_dict_set(&tOptionsDict, "overlay_h", "240", 0);
           tError = avfilter_init_dict(tOverlayContext, &tOptionsDict);
           av_dict_free(&tOptionsDict);
           if (tError < 0) {
               return tError;
           }
       }

       { // BUFFERSINK FILTER
           tBufferSink = avfilter_get_by_name("buffersink");
           if (!tBufferSink) {
               return -1;
           }

           tBufferSinkContext = avfilter_graph_alloc_filter(tFilterGraph, tBufferSink, "sink");
           if (!tBufferSinkContext) {
               return -1;
           }

           tError = avfilter_init_str(tBufferSinkContext, NULL);
           if (tError < 0) {
               return tError;
           }
       }

       // Linking graph
       tError = avfilter_link(tBufferContext1, 0, tOverlayContext, 0);
       if (tError >= 0) {
           tError = avfilter_link(tColorContext, 0, tOverlayContext, 1);
       }
       if (tError >= 0) {
           tError = avfilter_link(tOverlayContext, 0, tBufferSinkContext, 0);
       }
       if (tError < 0) {
           return tError;
       }

       tError = avfilter_graph_config(tFilterGraph, NULL);
       if (tError < 0) {
           return tError;
       }

       *pGraph = tFilterGraph;
       *pSrc1 = tBufferContext1;
       *pSink = tBufferSinkContext;

       return 0;
    }

    What do you think is the reason ?