Recherche avancée

Médias (1)

Mot : - Tags -/biographie

Autres articles (56)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (5170)

  • CANNOT LINK EXECUTABLE error with required libs loaded. How to link them properly ? [duplicate]

    11 septembre 2019, par dentex

    edit : I’m aware of the possible duplicate, but the answer it’s not directly applicable. I’m using ProcessBuilder and not Runtime.getRuntime().exec :

    public int execProcess(List<string> cmds, ShellUtils.ShellCallback sc) {    
       StringBuilder cmdlog = new StringBuilder();
       for (String cmd : cmds) {
            cmdlog.append(' ');
       }
       Utils.logger("v", cmdlog.toString(), DEBUG_TAG);

       ProcessBuilder pb = new ProcessBuilder();
       pb.directory(mBinFileDir);
       pb.command(cmds);

       Process process = null;
       int exitVal = 1; // Default error
       try {
           process = pb.start();

           StreamGobbler errorGobbler = new
           StreamGobbler(process.getErrorStream(), "ERROR", sc);

           StreamGobbler outputGobbler = new
           StreamGobbler(process.getInputStream(), "OUTPUT", sc);

           errorGobbler.start();
           outputGobbler.start();

           exitVal = process.waitFor();

           sc.processComplete(exitVal);

        } catch (Exception e) {
            Log.e(DEBUG_TAG, "Error executing ffmpeg command!", e);
        } finally {
            if (process != null) {
                Utils.logger("w", "destroyng process", DEBUG_TAG);
                process.destroy();
            }
       }
       return exitVal;
    }
    </string>

    I have two versions on FFmpeg compiled for android : with and without liblame enabled.

    When I load in /data/data/&lt;>/app_bin/ the FFmpeg binary compiled with NO lame support, it extracts audio from video without an issue. But when I use the one with lame support enabled, I get the error below into the log.

    Required libs, also compiled for android, are correctly loaded when shipped into the libs project folder with System.loadLibrary("lame").

    I was wondering if there is something else to do in order to properly make the FFmpeg binary find the libs.
    Those are the same libs given to the NDK to build the FFmpeg binary.

    D/dalvikvm(13741): Trying to load lib /data/app-lib/&lt;>/liblame.so 0x40ffed08
    D/dalvikvm(13741): Added shared lib /data/app-lib/&lt;>/liblame.so 0x40ffed08
    D/dalvikvm(13741): No JNI_OnLoad found in /data/app-lib/&lt;>/liblame.so 0x40ffed08, skipping init
    D/FfmpegController(13741): Trying to chmod '/data/data/&lt;>/app_bin/ffmpeg' to: 755
    V/FfmpegController(13741): /data/data/&lt;>/app_bin/ffmpeg -y -i /storage/sdcard0/Download/video.webm -vn -acodec copy /storage/sdcard0/Download/audio.ogg
    >>>>>> ---------- &lt;&lt;&lt;&lt;&lt;&lt;
    D/DownloadsService(13741): soinfo_link_image(linker.cpp:1673): could not load library "liblame.so" needed by "/data/data/&lt;>/app_bin/ffmpeg"; caused by load_library(linker.cpp:771): library "liblame.so" not foundCANNOT LINK EXECUTABLE
    >>>>>> ---------- &lt;&lt;&lt;&lt;&lt;&lt;
    I/DownloadsService(13741): FFmpeg process exit value: 255

    I’m not attaching code because it’s fairly straightforward :

    • download the FFmpeg binary (it’s not shipped with the app) ;
    • copy the binary from the download folder to /data/data/&lt;>/app_bin/ ;
    • chmod 755 ;
    • execute from there and read the output.

    Please comment if something else is required.

  • CANNOT LINK EXECUTABLE error with required libs loaded. How to link them properly ? [duplicate]

    4 avril 2013, par dentex

    edit : I'm aware of the possible duplicate, but the answer it's not directly applicable. I'm using ProcessBuilder and not Runtime.getRuntime().exec :

    public int execProcess(List<string> cmds, ShellUtils.ShellCallback sc) {    
       StringBuilder cmdlog = new StringBuilder();
       for (String cmd : cmds) {
            cmdlog.append(&#39; &#39;);
       }
       Utils.logger("v", cmdlog.toString(), DEBUG_TAG);

       ProcessBuilder pb = new ProcessBuilder();
       pb.directory(mBinFileDir);
       pb.command(cmds);

       Process process = null;
       int exitVal = 1; // Default error
       try {
           process = pb.start();

           StreamGobbler errorGobbler = new
           StreamGobbler(process.getErrorStream(), "ERROR", sc);

           StreamGobbler outputGobbler = new
           StreamGobbler(process.getInputStream(), "OUTPUT", sc);

           errorGobbler.start();
           outputGobbler.start();

           exitVal = process.waitFor();

           sc.processComplete(exitVal);

        } catch (Exception e) {
            Log.e(DEBUG_TAG, "Error executing ffmpeg command!", e);
        } finally {
            if (process != null) {
                Utils.logger("w", "destroyng process", DEBUG_TAG);
                process.destroy();
            }
       }
       return exitVal;
    }
    </string>

    I have two versions on FFmpeg compiled for android : with and without liblame enabled.

    When I load in /data/data/&lt;>/app_bin/ the FFmpeg binary compiled with NO lame support, it extracts audio from video without an issue. But when I use the one with lame support enabled, I get the error below into the log.

    Required libs, also compiled for android, are correctly loaded when shipped into the libs project folder with System.loadLibrary("lame").

    I was wondering if there is something else to do in order to properly make the FFmpeg binary find the libs.
    Those are the same libs given to the NDK to build the FFmpeg binary.

    D/dalvikvm(13741): Trying to load lib /data/app-lib/&lt;>/liblame.so 0x40ffed08
    D/dalvikvm(13741): Added shared lib /data/app-lib/&lt;>/liblame.so 0x40ffed08
    D/dalvikvm(13741): No JNI_OnLoad found in /data/app-lib/&lt;>/liblame.so 0x40ffed08, skipping init
    D/FfmpegController(13741): Trying to chmod &#39;/data/data/&lt;>/app_bin/ffmpeg&#39; to: 755
    V/FfmpegController(13741): /data/data/&lt;>/app_bin/ffmpeg -y -i /storage/sdcard0/Download/video.webm -vn -acodec copy /storage/sdcard0/Download/audio.ogg
    >>>>>> ---------- &lt;&lt;&lt;&lt;&lt;&lt;
    D/DownloadsService(13741): soinfo_link_image(linker.cpp:1673): could not load library "liblame.so" needed by "/data/data/&lt;>/app_bin/ffmpeg"; caused by load_library(linker.cpp:771): library "liblame.so" not foundCANNOT LINK EXECUTABLE
    >>>>>> ---------- &lt;&lt;&lt;&lt;&lt;&lt;
    I/DownloadsService(13741): FFmpeg process exit value: 255

    I'm not attaching code because it's fairly straightforward :

    • download the FFmpeg binary (it's not shipped with the app) ;
    • copy the binary from the download folder to /data/data/&lt;>/app_bin/ ;
    • chmod 755 ;
    • execute from there and read the output.

    Please comment if something else is required.

  • ffmpeg segments are not working as expected [closed]

    14 août 2023, par Sumit Dey

    Trying to record rstp stream from an IP camera into 10 mins chunks.

    &#xA;

    FFREPORT=file=$log_DIR/ffmpeg_recording.log \&#xA;ffmpeg -i "rtsp://$CAMERA_USERNAME:$CAMERA_PASSWORD@$IP:$PORT/stream1" \&#xA;-acodec aac -vcodec copy \&#xA;-f segment -segment_time 600 -min_seg_duration 300 -segment_atclocktime 1 -reset_timestamps 1 -segment_format mp4 \&#xA;-strftime 1 "$cap_DIR/record_%Y-%m-%d-%H.%M.%S.mp4" \&#xA;-report -y&#xA;

    &#xA;

    However, the video segments saved by ffmpeg are only 1 min long, instead of 10mins.

    &#xA;

    Even the parameter for min_seg_duration of 5min is not respected.

    &#xA;

    Log file : https://pastebin.com/xNLYh5Vq

    &#xA;


    &#xA;

    Reference : https://ffmpeg.org/ffmpeg-formats.html#segment_002c-stream_005fsegment_002c-ssegment

    &#xA;