Recherche avancée

Médias (2)

Mot : - Tags -/documentation

Autres articles (49)

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

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

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

Sur d’autres sites (4604)

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

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

  • Core : Required rule take precedence over number & digits rules

    11 janvier 2016, par Arkni
    Core : Required rule take precedence over number & digits rules

    Ref #1611
    
Ref #1663
    
Fixes #1514

Navigation