Recherche avancée

Médias (1)

Mot : - Tags -/portrait

Autres articles (71)

  • Les vidéos

    21 avril 2011, par

    Comme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
    Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
    Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

Sur d’autres sites (13058)

  • Can you "stream" images to ffmpeg to construct a video, instead of saving them to disk ?

    8 juillet 2016, par Brandon

    My work recently involves programmatically making videos. In python, the typical workflow looks something like this :

    import subprocess, Image, ImageDraw

    for i in range(frames_per_second * video_duration_seconds):
       img = createFrame(i)
       img.save("%07d.png" % i)

    subprocess.call(["ffmpeg","-y","-r",str(frames_per_second),"-i", "%07d.png","-vcodec","mpeg4", "-qscale","5", "-r", str(frames_per_second), "video.avi"])

    This workflow creates an image for each frame in the video and saves it to disk. After all images have been saved, ffmpeg is called to construct a video from all of the images.

    Saving the images to disk (not the creation of the images in memory) consumes the majority of the cycles here, and does not appear to be necessary. Is there some way to perform the same function, but without saving the images to disk ? So, ffmpeg would be called and the images would be constructed and fed to ffmpeg immediately after being constructed.

  • Android FFmpeg reports "file protocol not found"

    27 avril 2017, par Abdul Mateen

    I am trying to convert sequence images to video using ffmpeg command in android.
    I have build ffmpeg for android and put ffmpeg binary file in /data/local folder.
    I am running ffmpeg command using Runtime.getruntime.execute("mycommand") in Android.

    Stucture of mycommand is like this

    "/data/local/ffmpeg -r 40 qscale 2 -i /mnt/sdcard/images/img%d.jpg /mnt/sdcard/images/finalvideo.mp4"

    mycommand contains the path of a folder where I placed all my sequence images. Running this command gives me error "protocol not found".

    Also I read that file protocol is default in ffmpeg documentation.

    How can I run such commands ?

    The Error I am getting after running simple command like ffmpeg -i /mnt/sdcard/vid.mp4

    ffmpeg version 0.11.1.git Copyright (c) 2000-2012 the FFmpeg developers
    built on Sep 26 2012 11:58:35 with gcc 4.4.3 (GCC)
    configuration: --target-os=linux --prefix=/home/esteves/android-ffmpeg --enable-cross-compile --enable-runtime-cpudetect --disable-asm --arch=arm --cc=/home/esteves/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --cross-prefix=/home/esteves/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi- --disable-stripping --nm=/home/esteves/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-nm --sysroot=/home/esteves/android-ndk/platforms/android-8/arch-arm --enable-nonfree --enable-version3 --disable-everything --enable-gpl --disable-doc --enable-avresample --enable-demuxer=amr --enable-demuxer=aac --enable-demuxer=rawvideo --enable-demuxer=rtsp --enable-muxer=rtsp --enable-muxer=flv --enable-muxer=mpegts --enable-muxer=mp4 --enable-demuxer=rtp --enable-demuxer=rtp --disable-ffplay --disable-ffserver --enable-ffmpeg --disable-ffprobe --enable-libx264 --enable-encoder=libx264   libavutil      51. 72.100 / 51. 72.100
    libavcodec     54. 55.100 / 54. 55.100
    libavformat    54. 25.105 / 54. 25.105
    libswscale      2.  1.101 /  2.  1.101
    error of main   libswresample   0. 15.100 /  0. 15.100
    error of main   libpostproc    52.  0.100 / 52.  0.100
    /mnt/sdcard/vid.mp4: Protocol not found
  • Revision 72b146690a : Merge "Refactor vp9_dequant_idct_add function" into experimental

    28 février 2013, par Yunqing Wang

    Changed Paths : Modify /vp9/common/vp9_rtcd_defs.sh Modify /vp9/decoder/vp9_dequantize.c Merge "Refactor vp9_dequant_idct_add function" into experimental