Recherche avancée

Médias (91)

Autres articles (65)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Le plugin : Podcasts.

    14 juillet 2010, par

    Le problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
    Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
    Types de fichiers supportés dans les flux
    Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...)

  • MediaSPIP Player : les contrôles

    26 mai 2010, par

    Les contrôles à la souris du lecteur
    En plus des actions au click sur les boutons visibles de l’interface du lecteur, il est également possible d’effectuer d’autres actions grâce à la souris : Click : en cliquant sur la vidéo ou sur le logo du son, celui ci se mettra en lecture ou en pause en fonction de son état actuel ; Molette (roulement) : en plaçant la souris sur l’espace utilisé par le média (hover), la molette de la souris n’exerce plus l’effet habituel de scroll de la page, mais diminue ou (...)

Sur d’autres sites (4773)

  • AWS Lambda. Error=20 (Not a directory) when moving FFmpeg to /tmp

    18 novembre 2017, par Omar Riaz

    I am using the ffmpeg-cli-wrapper to run FFmpeg from an application I upload onto AWS lambda. I was initially getting the

    error=13 Permission Denied

    when trying to call it via the wrappers ProcessBuilder. My inital solution was to chmod 755 ffmpeg before uploading, but it didn’t help.

    For information, my FFmpeg and ffprobe files are located in the following classpath : static/ffmpeg/ffmpeg and static/ffmpeg/ffprobe. They are also statically linked.

    AWS Lambda permission denied when trying to use ffmpeg

    I’ve tried to follow the instructions given in the example above, but when I try to perform either mv or cp command :Runtime.exec("mv " + pathToFFmpeg + " /tmp"), I get the

    error=20, Not a directory

    error.

    I know that I have the correct path for FFmpeg because the following command mv *pathToFFmpeg* *an arbitrary name* runs without error, meaning that the file is there and so the mv command just renames it as it’s supposed to do.

  • Couldn't run a ffmpeg process by using supervisor [on hold]

    11 août 2019, par Ahmad

    This issue seems to be weird, at least for me.

    I’m trying to run a ffmpeg process using the supervisor as follows :

    [program:myprocessname]
    command="/usr/bin/ffmpeg -loglevel quiet -i ..."
    process_name=%(program_name)s
    numprocs=1
    umask=022
    priority=999
    autostart=true
    autorestart=unexpected
    startretries=3
    exitcodes=0
    stopsignal=TERM
    stopwaitsecs=10
    user=vagrant

    This program never gets run, in spite of changing the command to the absolute path where the FFmpeg is located.

    This is what I get (from log) when I try to run it :

    {
       "description": "can't find command '/usr/bin/ffmpeg -loglevel quiet -i
    ...'",
       "exitstatus": 0,
       "group": "myprocessname",
       "logfile": "/var/log/supervisor/myprocessname-stdout---supervisor-oxWFk5.log",
       "name": "myprocessname",
       "now": 1554747933,
       "pid": 0,
       "spawnerr": "can't find command '/usr/bin/ffmpeg -loglevel quiet -i ...'",
       "start": 1554747575,
       "state": 200,
       "statename": "FATAL",
       "stderr_logfile": "/var/log/supervisor/myprocessname-stderr---supervisor-WNmJv6.log",
       "stdout_logfile": "/var/log/supervisor/myprocessname-stdout---supervisor-oxWFk5.log",
       "stop": 0
    }

    It might be that FFmpeg spawns processes where the supervisor couldn’t handle ?

    Any idea, please ?

  • While working with ffmpeg : Created function in C file and after compilation with NDK accessing from android activity, getting signal 11 error

    30 mai 2016, par Dayanand Lande

    After successfully fire command ndk-build I got .so file in my libs folder, then after some changes in gradle file I got native_libs.xml .idea/libraries folder.

    Now I am accessing c function from my java code/ android activity. I am getting signal 11 error

    My code is

    C file

    #include
    #include <android></android>log.h>
    #include

    #include "libavcodec/avcodec.h"
    #include "libavformat/avformat.h"

    #define LOG_TAG "mylib"
    #define LOGI(...)  __android_log_print(ANDROID_LOG_INFO, LOG_TAG, __VA_ARGS__)
    #define LOGE(...)  __android_log_print(ANDROID_LOG_ERROR, LOG_TAG, __VA_ARGS__)


    //JNIEXPORT jint JNICALL Java_com_xxx_xxx_activities_SplashActivity_logFileInfo(JNIEnv * env, jobject this, jstring filename);

    jint Java_com_xxx_xxx_activities_TutorialsActivity_logFileInfo(JNIEnv * env, jobject this, jstring filename)
    {
       av_register_all();

       AVFormatContext *pFormatCtx;
       const jbyte *str;
       str = (*env)->GetStringUTFChars(env, filename, NULL);

       if(avformat_open_input(&amp;pFormatCtx, str, NULL, NULL)!=0)
       {
           LOGE("Can't open file '%s'\n", str);
           return 1;
       }
       else
       {
           LOGI("File was opened\n");
           LOGI("File '%s', Codec %s",
               pFormatCtx->filename,
               pFormatCtx->iformat->name
           );
       }
       return 0;
    }

    Loading and try to access method in java code is

    private static native int logFileInfo(String filename);


       static {
           System.loadLibrary("framegrabber");
       }

    In OnCreate of activity

    logFileInfo(file.getAbsolutePath());

    Finally error at point logFileInfo(file.getAbsolutePath()); is

    A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x106e in tid 8905 (Thread-20972)

    Please replay if you have any solution, Thanking in advance.