Recherche avancée

Médias (91)

Autres articles (69)

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

  • Organiser par catégorie

    17 mai 2013, par

    Dans MédiaSPIP, une rubrique a 2 noms : catégorie et rubrique.
    Les différents documents stockés dans MédiaSPIP peuvent être rangés dans différentes catégories. On peut créer une catégorie en cliquant sur "publier une catégorie" dans le menu publier en haut à droite ( après authentification ). Une catégorie peut être rangée dans une autre catégorie aussi ce qui fait qu’on peut construire une arborescence de catégories.
    Lors de la publication prochaine d’un document, la nouvelle catégorie créée sera proposée (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

Sur d’autres sites (9702)

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

    11 septembre 2019, par dentex

    This question already has an answer here :

    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

    This question already has an answer here :

    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.

  • Fixed handling of multiple class names for errorClass option. Test by Max Lynch. Fixes #280

    29 mars 2012, par Başar Aykut

    m jquery.validate.js m test/test.js Fixed handling of multiple class names for errorClass option. Test by Max Lynch. Fixes #280

Navigation