Recherche avancée

Médias (91)

Autres articles (88)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • MediaSPIP Player : problèmes potentiels

    22 février 2011, par

    Le lecteur ne fonctionne pas sur Internet Explorer
    Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
    Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

Sur d’autres sites (10993)

  • ffmpeg for Android build shows error

    2 avril 2015, par Jamal

    I would like to build ffmpeg for Android so I am following a steps from this tutorial http://www.roman10.net/how-to-build-ffmpeg-with-ndk-r9/

    What I tried

    1. downloaded android-ndk-r10d-darwin-x86_64.bin for Mac 64 bit OS
    2. decompressed/extract the NDK archieve file
    3. downloaded ffmpeg 2.6.1
    4. decompressed/extract the `ffmpeg 2.6.1 file
    5. copied the ffmpeg 2.6.1 extracted folder and pasted into android-ndk-r10d/sources/ location
    6. Opened the ffmpeg-2.6.1/configure file and replaced this code

      SLIBNAME_WITH_MAJOR=’$(SLIBNAME).$(LIBMAJOR)’
      LIB_INSTALL_EXTRA_CMD=’$$(RANLIB) "$(LIBDIR)/$(LIBNAME)"’
      SLIB_INSTALL_NAME=’$(SLIBNAME_WITH_VERSION)’
      SLIB_INSTALL_LINKS=’$(SLIBNAME_WITH_MAJOR) $(SLIBNAME)’

    with

    SLIBNAME_WITH_MAJOR='$(SLIBPREF)$(FULLNAME)-$(LIBMAJOR)$(SLIBSUF)'
    LIB_INSTALL_EXTRA_CMD='$$(RANLIB) "$(LIBDIR)/$(LIBNAME)"'
    SLIB_INSTALL_NAME='$(SLIBNAME_WITH_MAJOR)'
    SLIB_INSTALL_LINKS='$(SLIBNAME)'

    7.Created the build_android.shfile inside ffmpeg-2.6.1 folder so now it be like this ffmpeg-2.6.1/build_android.sh.
    instead of this NDK=$HOME/Desktop/adt/android-ndk-r9 line I set current NDK location
    8. executed this sudo chmod +x build_android.sh command

    1. while executing this command ./build_android.sh got below error

    Hubs-Mac-mini:ffmpeg-2.6.1 hubmaci7$ ./build_android.sh
    Configured with : —prefix=/Applications/Xcode.app/Contents/Developer/usr —with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/c++/4.2.1
    Configured with : —prefix=/Applications/Xcode.app/Contents/Developer/usr —with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/c++/4.2.1
    /hubmaci7/Pictures/Hubino/Jamal/android-ndk-r10d/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/bin/arm-linux-androideabi-gcc is unable to create an executable file.
    C compiler test failed.

    If you think configure made a mistake, make sure you are using the latest
    version from Git.  If the latest version fails, report the problem to the
    ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
    Include the log file "config.log" produced by configure as this will help
    solve the problem.
    Makefile:2: config.mak: No such file or directory
    Makefile:59: /common.mak: No such file or directory
    Makefile:100: /libavutil/Makefile: No such file or directory
    Makefile:100: /library.mak: No such file or directory
    Makefile:102: /doc/Makefile: No such file or directory
    Makefile:185: /tests/Makefile: No such file or directory
    make: *** No rule to make target `/tests/Makefile'.  Stop.
    Makefile:2: config.mak: No such file or directory
    Makefile:59: /common.mak: No such file or directory
    Makefile:100: /libavutil/Makefile: No such file or directory
    Makefile:100: /library.mak: No such file or directory
    Makefile:102: /doc/Makefile: No such file or directory
    Makefile:185: /tests/Makefile: No such file or directory
    make: *** No rule to make target `/tests/Makefile'.  Stop.
    Makefile:2: config.mak: No such file or directory
    Makefile:59: /common.mak: No such file or directory
    Makefile:100: /libavutil/Makefile: No such file or directory
    Makefile:100: /library.mak: No such file or directory
    Makefile:102: /doc/Makefile: No such file or directory
    Makefile:185: /tests/Makefile: No such file or directory
    make: *** No rule to make target `/tests/Makefile'.  Stop.
    Hubs-Mac-mini:ffmpeg-2.6.1 hubmaci7$

    please provide a needed solution for me to solve this errors

  • How to decode h264 video encoded from yuv444p frames ?

    22 octobre 2015, par Bing Liu

    I had an h264 video stream encoded from yuv444p frames, it was played well using vlc or mpv player.

    But when I tried to decode it using libavcodec, it just looked like this.

    wrong result ;

    The source frame is an upsize down vlc-player logo.

    Here is the intialization of the decoder :

    AVCodec *codec = avcodec_find_decoder(AV_CODEC_ID_H264);
    AVCodecContext *codecCtx = avcodec_alloc_context3(codec);
    avcodec_open2(codecCtx, codec, NULL);

    The decoder worked well when decoding packets encoded from yuv420p.
    Did I miss anything when decoding those packets encoded from yuv444p frames ?

    Update:I converted the yuv444p output into BGRA with sws_scale(), then I make a transforment with the follow codes ;

    int offset_out = 0, offset_tmp = 0;
    uint32_t *tmp = (uint32_t *)malloc(width * height * 4);
    for (int i = 0; i < width * height; i++) {
       if ((i + width + 9) % (width + 9) > width) {
           out[offset_out++] = in[i];
       } else {
           tmp[offset_tmp++] = in[i];
       }
    }
    memcpy(out + offset_out, tmp, offset_tmp);
    free(tmp);

    Then the picture looked all right.

    There is a number 9 in i + width + 9. I guessed that cause I knew the width and height of the source picture. But what if the width or height was changed to some value else, 9 didn’t work.

    I want to know what’s wrong with the decoder.

  • How does Rust work with process arguments ?

    1er octobre 2022, par SoptikHa

    I'm really confused about Rust processes. I'm trying to call something like this :

    



    ffmpeg -i path/to/test-video.webm -ab 160k -ac 2 -vn -f mp3 -


    



    This should extract sound out of video and send it to stdout. So I've done this :

    



    let sound: std::process::Output = Command::new("ffmpeg")
    .arg(format!("-i {}", args.input.to_str().unwrap()))
    .arg("-ab 160k")
    .arg("-ac 2")
    .arg("-vn")
    .arg("-f mp3")
    .arg("-")
    .stdout(Stdio::piped())
    .stdin(Stdio::inherit())
    .stderr(Stdio::inherit())
    .output()
    .unwrap();


    



    But for some reason, this doesn't work. It prints this to stderr :

    



    Unrecognized option 'i path/to/test-video.webm'.
Error splitting the argument list: Option not found


    



    When I remove the slashes from args (so it looks like .arg(format!("i {}", ...)).arg("ab 160k")..., I get this :

    



    Output file #0 does not contain any stream


    



    I think I misunderstood how this works, but I tested it on other applications and it seemed to work the way I'm doing it now. What did I miss, how does Rust work with these arguments ?

    



    And just to be clear, I know about the ffmpeg crates, but they don't work for me for some reason, I can't even compile them.